TestSuite Element/en: Unterschied zwischen den Versionen
Cg (Diskussion | Beiträge) |
Cg (Diskussion | Beiträge) |
||
| Zeile 1: | Zeile 1: | ||
"''Testsuite''" is the term used for a packaged test project. It contains a collection of elements like testplans, blocks and datatypes as well as resources, attachments and documentation. Depending on the context, the term "''test suite''" is used both to refer to a complete packaged suite (as present in a ".ets"-file) or to the top node in the tree-representation as shown in the editor. |
|||
These elements are called tree elements as they can be managed in a navigation tree of the expecco GUI. The testsuite itself is represented by its own top-level element in the tree. It is used to access the testsuite related editors, where settings and parameters which affect the execution are managed. |
These elements are called tree elements, as they can be managed in a navigation tree of the expecco GUI. The testsuite itself is represented by its own top-level element in the tree. It is used to access the testsuite related editors, where settings and parameters which affect the execution are managed. |
||
When a test suite element is selected, a [[Testsuite Editor/en|Testsuite Editor]] is shown on the right side of the tree. |
When a test suite element is selected, a [[Testsuite Editor/en|Testsuite Editor]] is shown on the right side of the tree. |
||
Test suites can be imported into other test suites and can therefore also be used as libraries which contain blocks for reuse. When a suite is imported into another suite, all of the imported elements are visible and usable inside the importing suite. That includes type definitions, test plans, test cases, attachments and of course action blocks. |
|||
Typically, suites are organized in a hierarchical fashion, and low-level functions (device control and access, protocols, data format handling etc.) are packaged into separate libraries, which are used by higher level component test and support actions, which are then further reused by system-, acceptance or end-to-end test scenarios. |
|||
[[Category:Tree Elements]] |
[[Category:Tree Elements]] |
||
Version vom 30. September 2016, 06:37 Uhr
"Testsuite" is the term used for a packaged test project. It contains a collection of elements like testplans, blocks and datatypes as well as resources, attachments and documentation. Depending on the context, the term "test suite" is used both to refer to a complete packaged suite (as present in a ".ets"-file) or to the top node in the tree-representation as shown in the editor.
These elements are called tree elements, as they can be managed in a navigation tree of the expecco GUI. The testsuite itself is represented by its own top-level element in the tree. It is used to access the testsuite related editors, where settings and parameters which affect the execution are managed.
When a test suite element is selected, a Testsuite Editor is shown on the right side of the tree.
Test suites can be imported into other test suites and can therefore also be used as libraries which contain blocks for reuse. When a suite is imported into another suite, all of the imported elements are visible and usable inside the importing suite. That includes type definitions, test plans, test cases, attachments and of course action blocks.
Typically, suites are organized in a hierarchical fashion, and low-level functions (device control and access, protocols, data format handling etc.) are packaged into separate libraries, which are used by higher level component test and support actions, which are then further reused by system-, acceptance or end-to-end test scenarios.
