Page History
...
| Table of Contents |
|---|
How to use Generic Tests
Automated testing
Automatic provisioning
Generic Tests may be used as an abstraction of automated tests, regardless of the testing framework and the technologies/platforms used.
...
- Implement the automated test code, store it in the source control system, and put the reference to the Test in Jira (i.e., the issue key).
- This depends on the testing framework: it can be as a "tag" or as the test name, if the framework supports that.
- Execute tests in the CI environment.
- Report execution results using the format specific to the automation framewoek framework (either using the REST API directly or through Bamboo/Jenkins add-ons).
- Create our update existing Tests in Xray
- In the first iteration, Tests will be automaticaly created in Xray and the Generic Test Definition field will act as the test identifier (e.g. classname plus classmethod corresponding to automated test). Xray is able to identify uniquely from the report file
- In second and onward iterations, existing Tests will be updated; Xray will use the Generic Test Definition field as the test identifier in order to find the existing Test in JIRA
- Depending on the test automation framework being used, links can also be automaticaly created between the Tests and the requirements
...
| Info | ||
|---|---|---|
| ||
You can see many examples in the page Integrating with Testing Frameworks, including: |
Manual provisioning
You may also create yourself Generic Tests as an abstraction of some test, so you can track its results in Jira. Generic Tests are great if you don't need to have a structured Test composed of steps (otherwise you would have to use Manual Tests as abstractions).
...
| Info | ||
|---|---|---|
| ||
See Automated Tests (Import/Export) for more information on Xray's JSON format and Import Execution Results - REST to know how to import those test results using the REST API. |
Exploratory Testing
Exploratory Testing allows you to better understand your SUT, using your existing knowledge of the system and your expertize to find even more about it. That learning will be used as positive feedback/reinforcement.
You can use Generic Tests as means to abstract some exploratory session. You can use the Generic Test Definition field to identify the session charter (e.g. goals of that session/mission).
During the execution of your session, you can attach evidence, report if all went fine and if not you may create defects. You may also decide to create a Manual Test, with the reproducible steps, for validating that the problem does not arise in the future.
| Info | ||
|---|---|---|
| ||
If you have multiple testers involved in your exploratory session, then you can create different Test Executions each one assigned to a different tester; you may use the Test Execution planning dates to define the fixed timeframe allocated to your session. The Test Execution description can be used to specify the tester charter, which complements and focuses the session charter for the tester(s) involved in that Test Execution. Please note that a Test Execution can only contain the same Test once. |