New answers tagged bug-report
I would separate the test case into 2: The first one ends with the confirmation message and the second one continues from there on. I would create a bug, link it to the first test case and keep the test case in 'ready', while I would close the second test case. If this is not a major requirement for you, then the test cases can be prioritized, so that ones ...
If you have specifications that say a confirmation must be displayed, the test fails. If you have user requirements or user expectations that there will be a confirmation dialog, the test fails. In the situation you describe, I would create a bug from the test, but it would have a lower severity rating because it doesn't interfere with functionality. The ...
It may depend on the strategy of your project, but i'd say this test is failed. If the confirmation is part of your specifications/functional need, you can't make this test pass. Imagine this is the only issue in your whole test plan, if you pass the test, then your indicators will be all green for this functionality. Thus, there is no reason to do rework, ...
I can't give you specifics on how to exactly do it, but from what I've read, it is possible. I checked the soapui.org forums and there is quite a bit of material available. Hope this helps! http://forum.soapui.org/viewtopic.php?f=5&t=24581&p=56413&hilit=integrate+jenkins+with+soap+ui&sid=88893521758c90cf82cb5c13c0274628#p56413
Top 50 recent answers are included