DO NOT REPLY [Bug 25212] New: - intermixed output in assertion results with threads

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25212>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25212

intermixed output in assertion results with threads

           Summary: intermixed output in assertion results with threads
           Product: JMeter
           Version: 1.9.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: HTTP
        AssignedTo: jmeter-dev@jakarta.apache.org
        ReportedBy: Joerg-Cyril.Hoehle@t-systems.com


The assertion results text is sometimes confusing when using multiple
threads. One would wish for all text of one sample case to be together. It more 
looks
like the multiple threads manage to intertwine output, so I cannot clearly
tell anymore to what testcase a particular assertion belongs.

An example:
http://localhost:8080/KBA-NCA/EncRequestCollection
Query Data: File:=0001.V1A+Einzelantrag.xml&UserNr=4
Cookie Data:
null
http://localhost:8080/KBA-NCA/EIRequestCollection
Query Data: File:=0002.I1A+Einzelantraege5.xml&UserNr=4
Cookie Data:
null
http://localhost:8080/KBA-NCA/CertRequestCollection
Query Data: File:=0002.C1A+Einzelantraege5.xml&UserNr=3
Cookie Data:
nullhttp://localhost:8080/KBA-NCA/CardCertRequestCollection
Query Data: File:=0002.P1F+Einzelantraege5.xml&UserNr=4
Cookie Data:
null
		Test Failed, expected to contain: <Status>0</Status>

		Test Failed, expected to contain: <Status>0</Status>
Now, what exactly failed?

It looks like the request and result messages are output separately, so other 
thread's output can jump in. Delaying output until the sample's result is 
obtained may be a better approach.

I could switch to other listeners (e.g. table or tree results) to see which 
request failed. However in those other listeners, I cannot see why. So the 
useability of the assertion result listener is very important

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org