Use a standardized language
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:
- 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 |