Responsible for registering a system under test for a test session.
As an operator, when I access a test session during the evaluation phase, I want to see a summary of the status of my evaluation for all the SUTs from my organisation to have an overview of the evaluation process.
That is to say, for each accepted system under test, a card displays information about the statuses of the SUT capabilities.
A shortcut allows the user to access the Evaluation page, filtered to display only the content related to the SUT.
A lot of information are shared with the test event participant through the tool and they are available in various places. As a consequence, the participant has to regularly consult the various pages to check if a status changed or if a new information is available.
To inform the information in a timely manner, a notification system should be put in place.
Inform the participant in a timely manner of any useful information through an instant messaging system.
Improve the user experience;
Save time to the participant, he does not have to look in the tool to find the information.
As a SUT Operator, I want to be notified when the status of a test instance changes.
As a SUT Operator, I want to be notified when my SUT is accepted to the session.
As a SUT Operator, I want to be informed when my SUT is graded.
As a SUT Operator, I want to be notified when someone posts a message in the chat window of a test run in which I am involved.
As a SUT Operator, I want to be notified when a milestone is reached: registration starts, registration ends, session starts...
The SUT edition page shall be reworked in order to make it clearer, and more complete, so that the participants to not have to jump in multiple locations to manage their systems.
Avoid using tabs and use a navigation bar instead.
Centralize the information about the SUT for the participant
Reduce the number of pages to maintain
Ease the work of the SUT operator
As a SUT operator, I want to set the name of my SUT.
As a SUT operator, I want to give a type for my SUT (Gateway, Workstation, PACS).
As a SUT operator, I want to communicate to my partners the links to my capability statements (HL7, IHE, DICOM, FHIR).
Do we really need a keyword ? It brings confusion because there is no consistency in the tool (names and keywords are used in several places)
As a SUT operator, I want to list the capabilities of my SUT that I want to test.
As a SUT operator, I want to be aware of the testing status of each AIPO (testable, not testable, at risk) when it has already been decided by the test session manager.
As a SUT operator, I want to know when a profile is not testable:
As a SUT operator, I want to ask the test session manager to allow me to test a capability as supportive.
As a SUT operator, I want to filter out the list of capabilities my system is registered for (filter on actor, profile, domain, option, supportive, result).
As a SUT operator, I want to see the result for each capability.
As a SUT operator, I want to see the notes from the domain manager on a given capability (if any).
As a SUT operator, I want to see where I have to sit in the room.
As a SUT operator, I want to access the communication channel dedicated to my system.
Give information to the users about their current/previous participations to the testing events.
Help participants to promote their attendance to test events and to have an overview of their past results.
not sure there's any...
Dashboard
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.
Adapt the wording to the event supported by Gazelle TM.
Use a common language.
Improve the user experience.
Sharazone, Inter-AMC and EPD projects will directly take advantage of this update.
As a first action, we should make the current Connectathon menu agnostic of the type of test session:
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 |
In order to follow-up with their progresses during the event, the SUT operators need to access some graphics to show them their progresses in terms of:
Allow participants to move their focus to their remaining work
Quickly see what to work on
Gain in efficiency
For the each Connectathon (Europe/NA), we maintain a documentation page for the participants to the event. Ex: https://gazelle.ihe.net/content/EU2021
Participants complain that the documentation is spread out several places and that it is complicated to understand where to find the relevant information. In addition, we have no placeholder for the documentation related to a given Projectathon.
It would be convenient to have an editable panel in Gazelle Test Management or, at least, to be able to define iframes so that, from the point of view of the user, all the documentation is available in Gazelle Test Management.
Give a single pointer to the Connectathon/Projectathon participants for accessing both the documentation and the features they need to access.
Improve the user experience and centralize all the documentation.
There is currently no placeholder for the Projectathon documentation (need to create a specific page somewhere), have the ability to create this page directly in TM would help the test session manager.
As a test session manager, I want to give access to the documentation of the event on a landing page for the Connectathon/Projectathon. It also includes publishing the daily morning news during the Connectathon/Projectathon.
As a test session manager, I may want to send a notification to the participants to inform them that content has been added/updated.
Gazelle test bed and in particular Gazelle Test Management is a complex system offering a lot of features to the users. In the context of a testing event (Projectathon or Connectathon), a workflow has to be followed by participants but it is not reflected in the GUI. In the contrary, all the features are listed in menus (with sometimes meaningless names) with no particular order.
Based on the last years' Connectathon surveys, user are expecting more guidance in the tool itself. Walking through the Connectathon/Projectathon process should be smooth and should not require hours of trainings.
Milestones are available in the tool for each testing session, as well as a few other parameters that should be used to help the user understanding where to go and when.
Make the navigation in Gazelle Test Management smooth enough that participants do not have to read the user manual or wait for webinars to understand where to go in the tool.
Reduce the amount of work (training/support) for the test session manager.
Enhance the Connectathon/Projectathon experience for users.
More and more Projectathons are being held and, in most of the cases, participants are new to Gazelle. We can use those testing event as lab to test our developments.
One-click operations that shall be available to the user: