Thread

Skip Navigation LinksForums > SpiraTeam Forums > SpiraTeam Issues & Questi... > Global Parameters

Global Parameters RSS Feed

Friday, December 13, 2013
For each test case, you can have parameters, but as far as I can tell they have to be redefined for every test case.  There is no global parameter list to pull from?

If anyone knows of a way to have a global parameter list, please let me know. 

Basically an example of this would be that I need to insert entityID's or URL's etc. into multiple test cases.  If those ID's change or those URL's change (which does happen) then all test cases have to be edited one by one, and for that matter they had to be set up one by one.  Where if there was a global parameter list I could create a Development URL or an EntityID at that level, and if it was changed, it would then be changed in all of the tests appropriately.
5 Replies
Jim R.Jim R.
re: S Wycoff on Friday, December 13, 2013
Friday, December 13, 2013
There are no global parameters currently available in SpiraTeam I'm afraid.

Jim.
S WycoffS Wycoff
re: Jim R. on Friday, December 13, 2013
Friday, December 13, 2013
Thank you Jim, I appreciate your response!

Shelley
Dennis WeisgramDennis Weisgram
re: S Wycoff on Friday, December 13, 2013
Thursday, January 23, 2014

Shelly,

We are in the process of adopting a test case "Framework". Out intention was to write our test cases to be more like our automation framework where we build objects and call them as needed. For example, we have a login screen which can be accessed from multiple URL paths (from a portal, directly to the application, via third party links).

Even though we come at this login page from different paths, the screen is always the same. So we have created test cases which only have one or two steps. One test case is Enter User Name. Another is Enter Password. And another is clicking the Login button (I know, a little broken up, but it is to support negative testing and for testing "forgot my password" link, etc.) All three of these use parameters (${UserName}, ${Password}).

We then either Link these test cases into another test case, so we can reuse the parameters OR create Test Sets containing the test cases and modify the parameters in the test case.

So we can have "Global Parameters" as long as we use the framework.

Clear as mud? Think of it like Lego Blocks. Each Block is a test case and we link them together to make a house or whatever. The red brick (user name 1) is always a red brick. The yellow brick (password 1) is always a yellow brick. You snap those together and now you have your entryway for that user and you can change the parameter per test set.

Chris M MetivierChris M Metivier
re: Dennis Weisgram on Thursday, January 23, 2014
Monday, May 12, 2014
Is this existing functionality or is it something you are still working to develop?  Parameters are only mentioned in a very limited fashion in the guide available online.  I would appreciate any updates available or additionaly how to information that you have.
Dennis WeisgramDennis Weisgram
re: Chris M Metivier on Monday, May 12, 2014
Thursday, September 4, 2014
Chris,

Sorry about the late response.

It is mostly existing functionality. We've found that Spira allows users to create a parameter for a test case and you may:
  1. Set the parameter once for multiple calls within the test case
  2. Set the parameter for multiple calls within test cases with links to test cases.
#1 is pretty obvious. You have multiple steps in a test case which all have the same parameter (example ${LoginName}). You only have to set the value once and everywhere within the test case that parameter value is shared.
But we found that if you have a test case which calls other test cases, with the same parameter name, you can call that parameter within a test step. For example, Test Case 1 has the parameter ${LoginName} (at least once). Next, you create Test Case 2 and you link Test Case 1 to it as step 1. Then for step two, you can have a step which says, "Login page displays the user name, ${LoginName}. You do NOT have to add ${LoginName} as a parameter (via Edit Parameters) to Test Case 2. It will carry over automatically.

Finally, you create a TEST SET and call Test Case 2 as one of the tests. Check the checkbox next to it and enter a value for the LoginName parameter. When you execute the test set, the parameter appears for both Test Case 1 and Test Case 2 -
Tagged
Statistics
  • Started: 12/13/2013
  • Last Reply: 9/4/2014
  • Replies: 5
  • Views: 1004
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2016 | Licensed to Inflectra Corporation.