Execution stops if a scenario has a dependency on login call and variable is mapped to an input file
I am having issue when adding condition to map the scenario folder name (to method name from input excel file) and add success dependency on login call before executing the scenario. The scenario does not get executed. It stops execution after login and does not move on the scenario.
Note: if I have the test outside of the scenario folder than it works fine. it executes the login call and checks for the success and then move on the test call.
Not sure why the script stops if the test is under the scenario folder
Comments
-
How did you configure the Test Flow Logic tab in the parent suite? Do you mean that you configured the scenario to only execute if "login" passed? Did "login" pass or fail?
0 -
Login is passing. I have the test flow logic as shown in the attached screenshot.
0 -
What is your variable condition? Probably that is evaluating to false.
0 -
Match the scenario with the MethodName from excel input file and use the data provided in that row.
0 -
If you remove the variable condition and see the scenario execute then you know it is a problem with the variable condition returning false. In other words, you need to isolate what is causing the scenario to be skipped.
0 -
If I have the test suite outside of the scenario folder than it works fine. But, when the test suite is inside the scenario folder then it does not execute. Can you please let me know why it would not work at scenario level?
0 -
It's really not clear from the information that you have given why the behavior is as you described. It depends a lot on where the variable gets set and how you have configured the execution of your test suites. I would suggest contacting Parasoft support since your question is likely very specific to how you set up this particular test scenario.
0