JMS Status Assertion in SoapUI Pro to ONLY validate/assert JMS requests
I have come across a scenario where I am able to add a JMS status assertion in a http soap request and funny enough it passes.
Would make more sense if JMS Status assertion was unavailable in non-JMS requests unless there is a logic behind this?
It does say in the description of this assertion "Applicable to Request TestSteps with a JMS endpoint", whereas it's applicable to a http/s endpoints too. so yeah, seems like a bug.
Share your thought...