SUT Operator | Drupal

SUT operators and the monitors exchange information about a test run

Priority

Medium - Feature to be considered

Status

Under development

Customer

Renovation

Business owner

Anne-Gaëlle BERGE

Description

During online events, we want the participants to a test run to be able to chat with each other. They might also need to share their screen or to exchange logs or screenshots that do not need to be logged in Gazelle Test Management.

Participants to the online events expect this capability to be offered also for face-to-face test events.

The chat room is convenient to share short information that are relevant to the execution of the test but not for large logs or images.

As a SUT participant, I want to have a dedicated place where I can chat with my test partners, share my screen, share images, and start calls if needed.

As a monitor, I want to be able to chat with the participants to the test run I am grading. When online, I might also need to view their screen or ask them images. I might also need to start a short call with them.

During past events, we created one test channel per test run. Gazelle Test Management shall be able to manage those channels for the users.

What is/are the targeted context(s)?

Connectathon

Projectathon

Who is the targeted audience?

Monitor

SUT Operator

Targetted goal(s)

Automate the creation of a channel in the communication tool.

Expected benefit

Save time to the participants and improve the channel management.

SUT operators schedule a test

Read more about SUT operators schedule a test

Instead of creating a test run, the user wants to simply schedule a test with a list of partners.

When Zoho is enabled in the test session, on the test execution and log page, the user can either create a new run (existing feature), either schedule a run (new).

When he schedule the test case, the tool ask him to select the participating systems (like for test run creation), and to give the date and time when this test run shall be executed.

A reminder is created in the test run channel with the following content:

SUT operator sets a reminder when he pauses a test

Read more about SUT operator sets a reminder when he pauses a test

When Zoho Cliq is enabled in the test session, when a SUT operator set the status of a test run to "paused", the tool shall ask me whether he wants to set a reminder to resume the test later on.

If yes, the user shall be able to set when the reminder shall be sent. In that case, Gazelle Test Management tell Zoho to create a reminder. The reminder shall include the name of the test as well as a link to the test run.

Content of the reminder (self reminder):

Resume test run for test [test name] for [SUT's keyword]: [link to test run].

Operator sees the testing status for each capability of his SUT

Read more about Operator sees the testing status for each capability of his SUT

Currently, Gazelle Test Management computes percentage of progress for each capability. Those figures are often wrong and operators do not really understand how to read them.

Instead of computing indicators for each columns, add a testing status at the capability level. It will be valued:

User creates as many presets as he needs

Read more about User creates as many presets as he needs

In Gazelle Test Management, on several occasions, the user is invited to create preset. He creates a cookie that works like a bookmark. Presets are available:

On the Test execution and logs page;
On the test repository page.

In both cases, the user is allowed to create 4 presets at a maximum. Except there is a technical reason, there is no other reason why the users could no create as many presets as he needs.

Restrict the "Test execution and logs" page to one SUT at a time

Read more about Restrict the "Test execution and logs" page to one SUT at a time

To improve the user's experience on the test execution and logs page and make it less complex, the operator shall not be able to see the test plan for several systems at a time.

The capability to filter on SUT shall remain but the operator is required to choose one.

Operator sees statistics about test execution

Read more about Operator sees statistics about test execution

On top of the "test execution and logs" page, the operator shall see a Testing Dashboard panel that shows:

Review the content of the "Test execution" page

Read more about Review the content of the "Test execution" page

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:

Organisation owner reviews contract status

Read more about Organisation owner reviews contract status

When the session requires a contract, as an organisation owner or an operator, I shall see the status of my contract on the Registration page.

The following pieces of informations shall be displayed:

The date when the contract was generated,
The date when the contract was received (if received)
The PO number
The date when the invoice was sent (if sent yet)
Instructions from participants.

Operator lists the attendees of his organisation for the current session

Read more about Operator lists the attendees of his organisation for the current session

As an operator or organisation owner, I shall see the list of attendees from my organisation for the current session. It is the "Event attendees" section.

If the session does not request the attendees to register, this section shall not be shown.

If no attendee is added yet, the table shall not be shown but instead a text message shall inform the user that attendees are expected to be registered in the tool.

For each attendee, display: