Test definition
APIJockey TEST uses a flat hierarachy to organize test definitions. A test definition describes a test case with its test steps and the assertions defined on the teststeps. That means, a test case can be passed in a test run only, when all teststeps can be run through and all assertions have passed.
Repository
First step in the test definition is the creation of a repository. You can create as many repositories as you want. Some Test tools use the term project. APIJockey TEST does explicitly not apply this term, as test cases are used in regressions tests, and the term project would imply a limited duration of the test definitions. A Repository contains a structure of test cases AND you can execute the contained testcases. This approach makes sure you're always able to assess the status of your system under test. See Repository
Testset
Once you have created a repository, you start to create Testsets. Testsets contain the actual Testcases. Testsets can be applied for various differenciations like use cases, types of tests (regression tests, new development). Testsets should not be used to differenciate test environments. Testsets make also sense, when Testcases use common variable data. See Testset.
Testcase
You define the actual Testcase on a Testset. You can create an arbitrary number of Testcases on a Testset.
Teststep
APIJockey TEST knows the following teststeps that you can create and arrange however you like and need to
- SOAP Teststep
- Datatransfer Teststep
- Randomize Teststep
The following sample demonstrate two SOAP Teststeps, together with a Datatransferteststep and a Randomizeteststep.
The Datatransferteststep would read data from SOAP Teststep 1 and store the derived value to a variable. SOAP Teststep 2 would access the variable value.
The Randomize Teststep would create random values and store the derived value to a variable.
SOAP Teststep 2 would access the variable value.
