Do you manage product or software development programs?
Do you need to run unit tests to check compliance or non-regression?
Use the "Unit Tests" app to plan your hardware, software, graphics and ergonomics tests, as well as performance and security tests.
Monitor and check your systems' compliance as a team
If you're involved in a quality approach, this app will enable you to organize your product development, monitor testing and present a functional map.
Activating the app adds a "Tests" menu to the "Production" tab, allowing you to :
- Building a functional map
- Design test programs
- Define your test scenarios
- Performing and validating tests
1. Test campaign
The "Test Campaign" menu allows you to designate the object of a set of test cases to be executed over a given period.
This is a category for classifying tests, carried out within a context and functional scope defined by you.
A campaign will thus group together a series of programs, themselves linked to scenarios, themselves associated with series of tests.
To run a test campaign is thus to organize and associate a set of test scenarios to be carried out.
2. Test environment
On this page, create a list of working and production environments to be tested.
This may be a software or hardware version, or a production context to be tested.
In this list, you can keep a history of the environments tested.
Each test is linked to a test environment.
3. Mapping
Mapping provides an overall hierarchical view of the system to be tested.
This architecture diagram allows you to associate programs, scenarios and tests with each function to be tested.
Start by creating a test program to run the mapping composition.
Then, from the "Mapping" page, click on the "More" button to add test functions, programs and scenarios.
4. Test program
A program is defined by :
- A name
- Associated legal references
- Type of features processed
5. Test scenario
Adding a scenario to a campaign allows you to design and document scenario descriptions.
A new test scenario is defined by :
- A linked program
- A name
- A type of test (functional, performance, security, etc.). The criteria are already listed and proposed by the app)
- Test objects
- How it works
- Acceptance criteria
Once you've saved the scenario, you can organize the tests.
6. Tests
For each test scenario, add one or more tests.
Each test contains the following information:
- Linked program name
- The name of the linked test scenario
- The name you give the test to differentiate it
- The name of the linked test campaign
- Name of the test environment
- Test status (drafting, testing, validated, failed)
- Tester's name
As soon as your test has been created, the test's "note" tab lets you archive the content of tests carried out. Depending on your testing rules and challenges, this free block enables you to check that a product element complies with its specifications (technical and functional), and to trace the content of the test execution stages, in the documented format used by your teams, to specify any anomalies encountered and corrective needs, and to follow up the test with the in-house team.
If the particular objective (functional, performance, etc.) you wish to check is validated, change the status to : "test OK"
If the objective is not validated, change the test status to: "failed".
Each modified status is time-stamped
