Adding some meaning to the assertion failures while diagnosing a test failure

git-svn-id: svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/jetty/trunk@1858 7e9141cc-0065-0410-87d8-b60c137991c4
This commit is contained in:
Joakim Erdfelt 2010-05-24 22:15:47 +00:00
parent 15c5e54628
commit a7fb0f4729
1 changed files with 4 additions and 4 deletions

View File

@ -190,10 +190,10 @@ public abstract class AbstractDoSFilterTest
String last="GET /ctx/dos/test HTTP/1.1\r\nHost: localhost\r\nConnection: close\r\n\r\n";
String responses = doRequests(request+request+request+request,1,0,0,last);
//System.out.println("responses are " + responses);
assertEquals(5,count(responses,"HTTP/1.1 200 OK"));
assertEquals(1,count(responses,"DoSFilter: delayed"));
assertEquals(1,count(responses,"DoSFilter: throttled"));
assertEquals(0,count(responses,"DoSFilter: unavailable"));
assertEquals("200 OK responses", 5,count(responses,"HTTP/1.1 200 OK"));
assertEquals("delayed responses", 1,count(responses,"DoSFilter: delayed"));
assertEquals("throttled responses", 1,count(responses,"DoSFilter: throttled"));
assertEquals("unavailable responses", 0,count(responses,"DoSFilter: unavailable"));
other.join();
}