Run a test before other tests in a suite?
I want to create a test suite in which the 1st test case supplies test data to the subsequent test cases via its custom properties. I want the first test case to run only once before any other test c...
Forum Discussion
HimanshuTayal, nmrao - Could you please point me to the documentation for suite and test level setup? Does the suite level setup run only if you run the entire suite or does it also run if you run only one test ? I require both.
Hey rajs2020,
Using the approach i outlined would just be at testsuite level.
However you could alter my approach so it runs at testcase level (as you want) instead by not bothering adding an inital single "setup" testcase (that contains "Run testcase" step that executes the disabled "setup" testsuite) in the functional testsuites. Instead you would add the "Run testcase" step as the first step in each of the testcases in the functional testsuites.
E.g.
-Setup testsuite (disabled)
--Generate access token testcase
---Generate token RESTstep
---Property Transfer (xfers the access token to project level property)
-Functional testsuite (enabled)
--Create new record testcase
---Run testcase teststep (executes Generate access token testcase)
---Create new record REST step (that sources access token from project level property)
Using the above approach has the advantage that the "setup" testsuites arent executed by default until the functional testcases execute cos the setup testsuites are disabled. Also, having the Run testcase steps in each test or suite means that if the token expires before the end of the session it doesnt matter cos it is re-generated each time the testcase (suite) is run.
The above approach is what nmrao showed me a while back and Ive been using this approach ever since.
Ta
Rich
Using the approach i outlined would just be at testsuite level.
However you could alter my approach so it runs at testcase level (as you want) instead by not bothering adding an inital single "setup" testcase (that contains "Run testcase" step that executes the disabled "setup" testsuite) in the functional testsuites. Instead you would add the "Run testcase" step as the first step in each of the testcases in the functional testsuites.
E.g.
-Setup testsuite (disabled)
--Generate access token testcase
---Generate token RESTstep
---Property Transfer (xfers the access token to project level property)
-Functional testsuite (enabled)
--Create new record testcase
---Run testcase teststep (executes Generate access token testcase)
---Create new record REST step (that sources access token from project level property)
Using the above approach has the advantage that the "setup" testsuites arent executed by default until the functional testcases execute cos the setup testsuites are disabled. Also, having the Run testcase steps in each test or suite means that if the token expires before the end of the session it doesnt matter cos it is re-generated each time the testcase (suite) is run.
The above approach is what nmrao showed me a while back and Ive been using this approach ever since.
Ta
Rich
richie- I have some questions about your approach. I have shared an example below to help you better understand what I am trying to achieve. It am not sure if your test above approach will work like the example below.
The groovy script sets custom properties of TestCase1-Datasource which any other test case can use, for example the TestCase 1-DataUser, TestCase 2-DataUser, TestCase 3-DataUser etc. Contents of the script:// Set the outputs. context.testCase.setPropertyValue("output1", "v1"); context.testCase.setPropertyValue("output2", "v2");
I want the data source (i.e. TestCase1-Datasource) to run only one time when (1) I run the entire TestSuite2, OR (2) I run only one test in TestSuite2. Example - If I run TestSuite2, then TestCase1-Datasource is run only once. If I run only TestCase 2-DataUser, even then TestCase1-Datasource is run only once.
richie, nmrao, HimanshuTayal - Does this example give a better idea of what I am trying to achieve? Do you know how it can be done in ready api?Thank you.
- 1. Setup script at suite level works in the same way as test case. But just before beginning of the suite.
2. As per the screen shot, and script sample, I don't see any need for the separate suite / test case for that. The same script content be used for the Setup script for suite 2. Not sure though the sample script you gave is exact or does it have some changes.
3. If you need it to run in manner you desired, then it should not be at the test suite setup script. There can be other approaches to achieve.
Need to have more inputs what exactly the script is doing and is that contains anything specific to particular test? or is it common? what do you access in the Test case 2 (which was set in proposed setup script of suite)?nmrao- Here is an explanation for the photo for the project which I attached.
TestSuite1 > TestCase1 > Groovy script :This pulls "default test data" from a "data store" and stores them inside the test case custom properties. This test data can now be used by other tests. We want to read the data store only once.
TestSuite2 > TestCase 1 and 2 :
In both of these test cases, the first test step is to get part of the test data (not all of it) stored in the custom properties of TestSuite1 > TestCase1. To do that, the first test step of each test case in TestSuite2 will call TestSuite1 > TestCase1. For the remaining test data, test cases 1 and 2 can use auto generated values or hard coded values depending on what is being tested. The problem with this approach is that TestSuite1 > TestCase1 is called once for each test case in TestSuite2 which we want to avoid.
Here is my requirement - I wanted to ensure that TestSuite1 > TestCase1 is called only once if you run the entire TestSuite2 *OR* if you run only one test in TestSuite2. To do that, I had earlier copied TestSuite1 > TestCase 1 into TestSuite2 and made it the 1st test case. It will run once before all the tests if you run the entire test suite. But, the problem is that it will not run if you run only one test in TestSuite2. That is why I call TestSuite1 > TestCase1 inside each test case of TestSuite2.
I hope this clarifies. Thanks.
