]> err.no Git - varnish/commit
Add $NOTES as a hack to document the fact that we know 1.1.2 fails some of
authordes <des@d4fa192b-c00b-0410-8231-f00ffab90ce4>
Tue, 18 Dec 2007 16:47:44 +0000 (16:47 +0000)
committerdes <des@d4fa192b-c00b-0410-8231-f00ffab90ce4>
Tue, 18 Dec 2007 16:47:44 +0000 (16:47 +0000)
commit0a2be29d7dac4cc9ded105c471a5c3d19a7b407a
tree250473047495df9a5b6f3564ba70fb9a9266549a
parent363c7e3602bfad716807dd55e5882a791e54d5c8
Add $NOTES as a hack to document the fact that we know 1.1.2 fails some of
the tests.  This should be revisited later; ideally, the framework should
know which tests are expected to pass and which are expected to fail, and
flag any deviation (if a test is expected to fail but passes, it is
probable that the test is broken)

git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@2297 d4fa192b-c00b-0410-8231-f00ffab90ce4
varnish-tools/regress/lib/Varnish/Test/Case.pm
varnish-tools/regress/lib/Varnish/Test/Case/POST.pm
varnish-tools/regress/lib/Varnish/Test/Case/Pipeline.pm
varnish-tools/regress/lib/Varnish/Test/Report/report.html