When the registration to a test event is open, a list of profiles is offered to the participants. In most of the cases, not all the actors of all the profiles will be selected by the registrants. That means that the test session manager needs to assess whether it is possible to test each individual profile or not.
Currently, Gazelle Test Management allows the test session manager to download a PDF file which gives, for each actor of each profile the names of the systems that claim to support it. Then, the test session manager has to maintain, outside of Gazelle, the list of testable profiles.
When time permits, the test session manager marks the SUT AIPO for non-testable profiles as "no peer". It is a manual action that should be avoided.
Support better the test session manager and domain managers in decided whether a profile can be tested or not.
Ease the registration process for the test session manager.
Give a better overview of the scope of the test session to the participants.
As a test session manager, I want to see the list of profiles selected for the current test session and, for each profile, I need the following information:
- What are the actors involved in the profile;
- What are the (non-dropped) SUT registered for each actor of this profile;
- Which ones of the SUT are already accepted to the session.
As a test session manager, I want to be able to give a status to each profile among: not testable, testable, at risk, not assessed yet.
As a test session manager, I want to decide when to make the list of profiles (along with their status) public to the test session participants.
As a test session manager, I want to be able to ask the tool to mark as "no peer" all the AIPOs when the profile's status is set to "not testable".
As a SUT operator, I shall not be able to add a "not testable" profile to my SUT. However, I want to see it in the list of profiles so that I understand why I cannot select it.
As a SUT operator, I shall not be able to start a test for a not testable profile also the actors appear in the test plan (with status = "no peer").