Ask a Question

Test Case calling a Test Case with Parameters

jhanely
New Contributor

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?

4 REPLIES 4
MisterB
Community Hero

It seems to be working for me.  I'm on the Cloud version.  In case you've not seen the Help documentation on that feature's use, it's here: Calling a Test Case with Parameters | Zephyr Scale Server/Data Center Documentation (smartbear.com)

 

Here's an example of it working for me:

 

Setup of Test-T10 to use a default parameter of 12345678:

MisterB_0-1673530692720.png

 

Setup of Test-T11 (calling Test-T10), using a different parameter of 11112222 that is set in T-11:

MisterB_2-1673530921122.png

Test Player view of Test-T10 and Test-T11 with different values.  Note: each time you update the parameter of Test-T10 or T11 you will have to click the option to update the Test Player with the latest version of the test case to see the new values:

 

MisterB_3-1673531158799.pngMisterB_4-1673531208461.png

Hope that helps.



Need more help? Feel free to connect with me on LinkedIn: https://www.linkedin.com/in/andrew-barbet-548a234/
jhanely
New Contributor

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!

MisterB
Community Hero

Hi,

 

Sorry, I missed that point in your original post.  I run into the same issues that you do.  It seems that the functionality is limited to only 1 layer and you can't go deeper than that.  Probably best you speak to the SmartBear support team for help.  I'd be interested in what they say if you don't mind sharing 🙂

 

SmartBear Support

 

Andy



Need more help? Feel free to connect with me on LinkedIn: https://www.linkedin.com/in/andrew-barbet-548a234/

 I also ran into this same issue. Could the SmarBear Support help here ?

cancel
Showing results for 
Search instead for 
Did you mean: