Automation project

Automation project is the root element in the test editor, select it will show basic information about the current project.

Actions

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

Run all tests: Launch the test of the whole automation project
Stop: When test is launched, stop the test execution.
Report: View the test report or export the test report to a file (in APR format)

Note
Test reports can be generated at any time, you don’t need to run all tests before viewing and exporting test reports.

Project Overview

Project Information

Information related to creation date, saved date are displayed and the author of the automation project.

Please note that author’s name is retrieved from the current user’s session, these values cannot be modified.

Profile

You can edit the test profile, containing Test Settings, Credentials, System Variables and test environments related to your test automation project.

Use Active profile - To embed current active profile into the automation project, which means starting automation which the parameters you are using for manual tests.
Load Profile – gives the possibility to load a test profile from another location.
Edit profile – Edits the current profile embedded in the automation project.

Note
By default, when creating a new automation project, the current copy of active profile will be embedded into the project. The settings changed on one side (either manual test or automation project) will not affect to other side.

List of test suites

Here you can find all the test suites of the current automation project.

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
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