diff tests/test-check-interfaces.py @ 37611:ae8730877371

httppeer: basic implementation of capabilities interface

This is a bit crude. The capabilities mechanism for version 2 of
the wire protocol is a bit different from version 1. And code
in core is relying on strings passed to capable() matching strings
advertised by the "capabilities" wire protocol command. I may
refactor the internal checking mechanism to be a bit more
abstract or based on interfaces. Time will tell...

Differential Revision: https://phab.mercurial-scm.org/D3256

--- a/tests/test-check-interfaces.py	Tue Apr 10 18:47:09 2018 -0700
+++ b/tests/test-check-interfaces.py	Tue Apr 10 19:09:35 2018 -0700
@@ -94,6 +94,8 @@
 
     ziverify.verifyClass(repository.ipeerconnection,
                          httppeer.httpv2peer)
+    ziverify.verifyClass(repository.ipeercapabilities,
+                         httppeer.httpv2peer)
     checkzobject(httppeer.httpv2peer(None, '', None, None, None, None))
 
     ziverify.verifyClass(repository.ipeerbase,