Click or drag to resize

Test suite

Test Suite contains a collection of Test Cases. The test automation engine implemented in Hummingbird project supports two kind of test suites:

  • Normal test suite: consists of test cases related to Functional test. Automation engine will run the test cases one after another.

  • Load test suite: consists of test cases related to Performance Test. Only performance test cases can be inserted into a Load test suite. Automation engine will run ALL the performance test cases simultaneously.

Note Note
A Load test suite aims to run one or more performance test scenarios in the SAME time, to simulate loads on different services. If you want to run performance test cases one after another, please place them into different Load Test Suites.
Actions

On the top of detailed view there are several buttons users can interact with

  • Run test suite: Execute all test cases of the current test suite

  • Stop: When test is launched, stop the test execution.

Custom Variables

Custom variables holds variables declared by the user. The variables declared in the Project level can be accessed in the whole automation project level.

Note Note
In Hummingbird test framework, variables can be declared and used at any level: Project, Test Suite, Test Case and Test Step.
Runtime variables

Runtime variables cannot be declared by the user. They are declared and assigned by the automation script itself. For example, for Data Generator, Data Driven Test Case.

Runtime variables are more priority than Custom Variables. When there are variables of the same name in both Custom Variables and Runtime Variables, the value from Runtime variables will be used.

Variable rules

Automation engine will use the variable following the rules described as below:

1. Variables are private, and can be accessed only in its scope. For example, Variables declared in the Test Case can be accessed in all its Test Steps, but cannot be accessed from its container Test Suite or another Test Case.

2. Variables are retrieved from the nearest level when there are more than one variables having the same name. For example: If the variables of the same name is declared in Test Suite and Test Case, for a Test Step, the one declared in Test Case will be used.

3. For the same level, runtime (script defined) variables are more priority than custom (user defined) variables