Sharazone moderator

Is in charge of the correct happening of the Sharazone project. Manage the involved participants and animate the community of participants.

Communication between management, participants, and monitors

Submitted by abe on Mon, 12/20/2021 - 11:28
Priority
Medium - Feature to be considered
Status
Draft
Customer
Renovation
Business owner
Anne-Gaëlle BERGE
Description

In the last years, the Projectathons have been held online as well as the two last European Connectathons. In that context, Rocket.chat has been used as a communication tool between the participants, with the test session managers, and with the monitors. 

The SHARAZONE participants also use this tool for one-to-one communications. It is also the place where the SHARAZONE administrator broadcast information to the participants: new object available, tool maintenance, and so on.

All the involved parties agree that this tool is really useful and might also have an interest during onsite testing events.

What is/are the targeted context(s)?
Targetted goal(s)

Main goal: allow participants to online events to communicate in a timely manner: find test partners, execute test cases, review test cases, share screen.

Secondary goals:

  • Support participants during the preparatory phase
  • facilitate the exchange of information (patient identifier, logs) during on-site events
  • be able to leave a message to an on-site participant (or monitor or TSM) when it is busy on another subject.

 

Expected benefit

Preparatory phase:

  • better support to the participants
  • create a place for exchange

Online:

  • make the test event happens

Onsite:

  • fasten the test execution and debugging

 

Documentation

As a Test Session Manager, I want to broadcast information to all the participants (text message / attachments).

As a Test Session Manager, I want to broadcast information to all the monitors (text message / attachments).

As a Test Session Manager, I want to hold calls with all the participants to the online event (video is optionnal).

As a Test Session Manager, I want to share my screen with all the participants when the event is online.

As a monitor, I want the participant to share his screen with me so that I can verify the outcome of the test even when working remotely.

As a SUT operator, I want to share information with my partners of the test instance.

As a monitor, I want to contact all the SUT operators of a particular test instance when we are working online.

As a SUT operator, I want to contact the management team when I have a question during an online event.

As a participant (SUT operator, monitor, test session manager), I want to receive all the notifications in one place.

As a test session manager, I want to enrol all the participants to the event in the communication tool.

As a participant, I want to use my Gazelle login to access the communication space.

As a test session manager, I want to offer one public channel per system or at least one public channel per organisation.

As a test session manager, I want to reuse the same "default" channels from an event to the other.

As a test session manager, I want to pin a message at the top of a given channel as a reminder to readers.

Use a standardized language

Submitted by abe on Thu, 12/16/2021 - 11:25
Status
Draft
Customer
Renovation
Business owner
Anne-Gaëlle BERGE
Description

In Gazelle, the wording is not always consistent with ISTQB and it is really Connectathon oriented. It leads to confusion to Gazelle users. The wording shall be adapted in several places to improve the user experience.

What is/are the targeted context(s)?
Targetted goal(s)

Adapt the wording to the event supported by Gazelle TM.

Use a common language.

Expected benefit

Improve the user experience.

Opportunities

Sharazone, Inter-AMC and EPD projects will directly take advantage of this update.

Documentation

As a first action, we should make the current Connectathon menu agnostic of the type of test session:

  • Use the "type" (from the testing session configuration) as display name in the menu bar where "Connectathon" is currently used.
  • In case we do not merge the preparatory tests and test session tests:
    • The "Pre-Connectathon" sub menu might be renamed into "Preparatory tests"
    • The "Pre-Connectathon Tests" sub menu might be renamed into "List of preparatory tests"
    • The "Pre-connectathon results" sub menu shall be renamed into "Preparatory test results"
  • The "Connectathon" sub menu might be renamed into "Testing"
  • The "Connectathon" menu entry (lower level) could be renamed "Execute tests" (as well as the short cut in the top menu bar)
  • The "Connectathon result" menu entry should be renamed "Test session results"
  • The "Download connectathon report" menu entry should be renamed "Download test session report"

Then, everywhere in the tool, we should use the following vocabulary:

Current term New (English) New (French)
TF Interoperability model  
Tests list Tests Tests
Test definition Test cases Cas de tests
MetaTest List    
Configuration SUT Configurations Configurations des SUT
Network Network details Informations réseau
All configurations SUT network configurations Configurations réseau des SUT
Connectathon    
PreConnectathon Preparatory tests  
Test instance Test run  
Testing session Test session  
system SUT  

 

Read system in session

Submitted by abe on Wed, 07/28/2021 - 12:32
Description

Access the details about a system in session (identification, list of profile/actor pairs, comments, demonstration ...)

Specification status
To be reviewed
Status
Available
Priority
Essential - Must have, it is essential for the use cases
Is specific to a project ?
No