Hi,
I've created this post to avoid confusion with my other post.
We have this test for Log on verification.
Scenario 1 for the normal process(Valid Users) and Scenario 2 for the negative test(Invalid Users).
We've put those scenarios in a datasource to be able to leverage the data-driven capability of the test studio.
After running the test, we noticed that Scenario 2 behaves like Scenario 1. Which is not the expected.
We later on observed that Test Studio doesn't closes the browser on every end of each iteration. So credentials for Iteration2 is actually the credentials for iteration1.
We tried adding a 'Clear Cached' step but it still behaves the same.
We also tried to set the Behavior Property ClosesBrowser = True but still the same.
We also tried your suggestion on my other post to put the 'Clear Cached' step on the 1st step but still no luck.
And unfortunately, the design of our application page doesn't have a Log-off button.
Any thoughts on this?
Thanks,
Mariko
I've created this post to avoid confusion with my other post.
We have this test for Log on verification.
Scenario 1 for the normal process(Valid Users) and Scenario 2 for the negative test(Invalid Users).
We've put those scenarios in a datasource to be able to leverage the data-driven capability of the test studio.
After running the test, we noticed that Scenario 2 behaves like Scenario 1. Which is not the expected.
We later on observed that Test Studio doesn't closes the browser on every end of each iteration. So credentials for Iteration2 is actually the credentials for iteration1.
We tried adding a 'Clear Cached' step but it still behaves the same.
We also tried to set the Behavior Property ClosesBrowser = True but still the same.
We also tried your suggestion on my other post to put the 'Clear Cached' step on the 1st step but still no luck.
And unfortunately, the design of our application page doesn't have a Log-off button.
Any thoughts on this?
Thanks,
Mariko