Implementation status
Available
Targetted user
Feature
Description
The test plan for systems under test that are not accepted to the test session shall not be displayed to the user, whatever his role.
Test cases shall be sorted by capability (former AIPO - Actor Integration Profile Option).
For each capability, shall be displayed:
- Profile,
- Actor,
- Profile Option,
- Testing depth (Supportive vs Thorough)
- Result of the evaluation when available
For each test case, shall be displayed:
- Its name,
- Its type (Connectathon, PreConnectathon, ...)
- Whether it is optional or required,
- How many times it shall be repeated (in terms of targetted number of test runs),
- Whether peers are available (if peer to peer or group tests)
- The list of test runs for this test case with their status
- A play icon to start a new test run (unless the test session is closed)
The operator shall be able to filter on domain, profile, transaction, results, system, actor, profile option, testing depth (thorough/supportive), test peer type, test type (PreConnectathon, Connectathon etc...), test run status.
A user with role tool administrator, monitor, or test session manager shall also be able to filter by organisation.
Documentation (Snapshot)
Acceptance criteria
As a SUT operator,
- I can list the capabilities to be tested by my SUT and which are the test cases to execute;
- I can list all the test runs along with their status,
- I can filter on: domain, profile, transaction, results, system, actor, profile option, registration status (thorough/supportive), test peer type, test type (PreConnectathon, Connectathon etc...), test run status;
- I can save my search as a preset, presets are listed, and the page is filtered accordingly when I use them;
- I can mark one of the preset as favorite and the browser set this filter when I access the page;
- I can start a new test run unless the test session is closed.
Jira issue