erwinfeijns
2 months agoNew Member
Updating multiple call-to-tests in a test cycle not all updated
Hi all,
We have some behaviour we cannot explain when working with call-to-test. This is the case:
- Our test script A consists of "normal" steps and several call-to-test steps (more than 10).
- Test script is added to a test cycle. So far, test works fine.
- Multiple changes are made to test scripts that are "call-to-test" steps in test script A.
- In Test Player a message is shown to update the script, because of the multiple changes.
- The update script message keeps coming back, no matter how often the update button is clicked. (It seems like this behaviour doesn't apply when it is only 1 or 2 call-to-test steps. When it is reasonably more, problems seem to appear.)
- The status of the call-to-test steps stays "outdated", no matter how often the update button is clicked.
- The work-around so far seems to be removing test script A from the cycle, and add it again, thus losing the already executed steps and results.
Our questions:
- Do more users experience the above outlined behaviour?
- Is there a max to the amount of call-to-test steps in a single test script?
- Is this a bug?
Any suggestions highly appreciated. Thanks in advance.
Cheers, Erwin