Currently the SUT operator can execute tests from two pages:
- Connectathon > Pre-Connectathon > Pre-Connectathon results
- Connectathon > Connectathon > Connectathon
It is confusing and both pages need to be reviewed in order to give a better level of information to the SUT operator.
As a SUT Operator, I want to execute preparatory tests as soon as my system is accepted to the test session.
As a SUT Operator, I want to execute the Connectathon/Projectathon/Conformity assessment tests during the test event, for accepted systems.
As a SUT Operator, I want to filter the test plan based on my system's capabilities.
As a SUT Operator, I want to see a summary of all the test runs for my systems along with their status.
As a SUT Operator, I want to create quick links to display the results of a previous search on test runs (currently named preset).
As a SUT Operator, I want to see indicators about my progresses in executing the test plan.
As a test designer, I want to decide whether a test shall be graded by a monitor or if the operator can mark it as self-verified.
As a test session manager, when I assign the test to the monitors, I do not want to see those that have to be self-verified by the operator; because they do not need to be reviewed by a monitor.
Make the event preparation and the test execution during the event smoother and easier to understand.
Create a page intuitive enough for SUT operators to find their way without loosing time in reading documentation or watching webinars.
Reduce the number of pages to maintain by reusing the same layout for both types of tests.
Review the way we build the test plans.