...
| width | 20% |
|---|
Main View: Definition View
Workflow:
...
| width | 80% |
|---|
Specific views:
...
Definition Tree, Reading View, Issue Detail View
Workflow: Test Definition
Description
...
Fundamentals
The purpose of test definition is to create and organize test cases for later use in test plans and test execution of tests. The A test definition case is project specifica Jira issue in a project that has been activated for T4J. The issues have enhanced features for testing.
Every test project has its own definition tree which allows structuring tests in a folder hierarchy.
The definition tree , which serves as basis the framework for creating test plans from the the contained tests.
Those tests don't necessarily need to come from the same project the definition tree belongs to.
It's also possible for test including the test cases. (But note that a given plan may include test cases from multiple projects. It is also possible for a test case to be part of multiple definition trees at the same time.
The three main entities used during test definition are tests, test steps and test parameters.
Tests are basically JIRA issues extended with test steps and test parameters.in different projects.)
A test case represents a single executable entity for a specific test casethat tests some aspect of an application. It can be executed on its own or as part of a test plan. Test steps represent atomic actions that have are to be executed carried out and evaluated during the execution of a test. Parameters are simple Test parameters represent key-value pairs and that serve as variables in test steps.
They 're are used to input plan specific or execution specific data to test steps without the need of modifying to modify the actual test definition.
The following pages provide details:
| Child pages (Children Display) |
|---|