marcl
10 years agoOccasional Contributor
Message content assertion: null, cannot rename test steps
Hello,
my team is currently encountering a problem with SoapUI NG which cause it to be really hard to use, so I was hopping you could provide some help. I tried to get as much data as possible below, but don't hesitate to ask if I can provide any extra information.
SoapUI NG version: 1.2.2
Environment: Windows 7 / 64 bits. Reproducible on multiple different hosts.
Problem:
- When executing a Test Suite, message content assertions fails with error message "null".
- Test steps cannot be renamed. Trying to rename them will cause them to keep their current name, without any error message
How to reproduce:
- In an existing Test Case with multiple Test Steps, add a new step
- Move this new step around, for example by pressing CTRL+UP a couple time
- [optional] Disable this new step
- Try to run the Test Suite. all Message Content Assertions will fail. Other assertions seems to work properly (e.g. Script Assertion, JSONPath Count Match, JSONPath Match).
Note that sometime this bug will also trigger without moving test steps around - but in this case we couldn't find a way to reproduce it at will. With the steps described above, it triggers systematically.
Workaround:
- Restart Ready!API
Frequency:
- Dozen times a day :-(
Just a message to let anyone following this topic know that it was indeed fixed with release 1.4, which is now available :).