Contributions
Check if Currently in Execution Plan
I tried searching the documentation of Execution Plans but couldn't find what I'm looking for. Currently my test python scripts are opening a CSV to read values and closing it afterwards. This means only 1 script can be run at a time since files can't be reopened once closed in a single run. I was wondering if there was a way for TestComplete to identify if it's currently in an Execution Plan. That way I can do a simple IF statement to see if we're in an Execution Plan or not and close the CSV when applicable. I can definitely code a project variable that is just a Y or N to accomplish this but wanted to use any integrated functions TestComplete has prior to going that route.193Views0likes1Comment- 12 months agoPlace Zephyr Squad QuestionsZephyr Squad Questions235Views0likes0Comments
Test Case calling a Test Case with Parameters
I tried searching around for similar questions but didn't have any luck, so forgive me if this has been answered before. I have a test case with 2 steps. We'll call this TEST-T10. T10's very first step has a parameter that can be set. This is fine and works as expected. The problem is when I create another test case that calls upon TEST-T10 and then call a test case that calls upon that test case, I cannot set the parameter for T10's first step. This is pretty crucial to our how we're using Zephyr Scale, as many of the test cases we plan to create will use calls to test cases with simple parameters. Example: TEST-T10 has a parameter that is set in step 1. TEST-T11 calls TEST-T10, and you can set the parameters there. A final test, TEST-T12, calls TEST-T11 and thus I cannot set parameters for TEST-T10. Is there a setting I missed or a button I'm missing?774Views1like4CommentsRe: Test Case calling a Test Case with Parameters
Hi Andrew, Thanks for the response! I think I didn't explain it well. Everything you've done above I have also done. It's when the test scripts start getting nested even more that I'm running into issues. Basically TEST-T12 calls TEST-T11 which will have TEST-T10 as a step. That's where the breakdown is happening. Sorry for the confusion!738Views0likes0Comments