Connectathon Using Gazelle Test Management Only

From IHE Wiki
Revision as of 17:55, 7 February 2020 by Smoore (talk | contribs) (Created page with "=Connectathon Using Gazelle Test Management Only= ==Assumptions== * You have access to a copy of Gazelle Test Management: ** You are using an existing managed copy ** You hav...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Connectathon Using Gazelle Test Management Only

Assumptions

  • You have access to a copy of Gazelle Test Management:
    • You are using an existing managed copy
    • You have an agreement with Kereval for them to install (or manage) a copy for you.
    • Both of these options include database replication to have all appropriate test definitions. You write test definitions in the Gazelle Master Model, and these are replicated to individual copies of Gazelle through an automated process.
  • All profile definitions and test definitions that you need are entered in Gazelle Master Model.
    • Profile definitions and test definitions are normally entered by the Domain Technical Project Manager. You should consult with the appropriate manager or managers, especially if you are extending tests in a domain.
    • If you have created a new domain or own your own profile, that implies you have entered the profile definitions and test definitions in the Gazelle Master Model.
  • You have reviewed all test definitions / requirements and know:
    • They do not need extra tools (or you have those tools)
    • You have support on site or remotely to respond to participant questions. The amount of support required depends on the nature of the event. A strict testing evening might require more support. A collaborative event that is designed to educate and not post results might require less support.

Steps

This is not a User's Manual, but it does provide a general set of steps to follow in Gazelle Test Management.

  1. Create a Testing Session in Gazelle Test Management. This is not a full list, but some essential items are:
    1. Registration close date / time
    2. Start and end date / time of the Connectathon
    3. List of profiles to be tested (only include those you want to test).
  2. Decide if you want to use Gazelle Test Management to generate a contract.
    1. You do not need to use the contract generated by Gazelle Test Management to run a Connectathon.
    2. If you do want that contract, there are some manual steps outside the Web UI. Please contact Kereval.
  3. Prune profiles that do not have sufficient test partners
  4. Decide if you want to use Gazelle to capture system configuration
  5. Enter and assign test monitors
  6. Provide training to participants and monitors
  7. Repeatedly execute test cases with individual test validation
  8. Provide overall grading. Review the body of work for each system/profile/actor and assign a grade (pass, did not complete, ....)