diff tests/test-http-api-httpv2.t @ 40049:a732d70253b0

tests: don't be as verbose in wireprotov2 tests

I don't think that printing low-level I/O and frames is beneficial to
testing command-level functionality. Protocol-level testing, yes. But
command-level functionality shouldn't care about low-level details in
most cases. This output makes tests more verbose and harder to read.
It also makes them harder to maintain, as you need to glob over various
dynamic width fields.

Let's remove these low-level details from many of the wireprotov2
tests.

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

--- a/tests/test-http-api-httpv2.t	Wed Oct 03 12:57:01 2018 -0700
+++ b/tests/test-http-api-httpv2.t	Wed Oct 03 09:48:22 2018 -0700
@@ -188,7 +188,7 @@
   s>     0\r\n
   s>     \r\n
 
-  $ sendhttpv2peer << EOF
+  $ sendhttpv2peerverbose << EOF
   > command customreadonly
   > EOF
   creating http peer for wire protocol version 2