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
