Based on registration, participants to the connectathon need to perform a series of test in order to be successful. Some of the tests need to be performed ahead of the connectathon and some need to be performed during the connectathon.
All participants are required to run a series of software tests in advance of the Connectathon. These tests, typically done with tools provided by IHE, are designed as auditing tests to make sure you have prepared in advance; these are not full test suites or certification tests for a profile.
Each participant system is assigned a table that typically seats two people comfortably. Participants bring their equipment to the table and use the Gazelle system to identify specific tests as defined by their choice of actor/profile pairs. A participant will select a test to be run, and Gazelle presents a list of test partners. The participant will walk over to a peer’s table and arrange a time for testing. After a specific test is completed, the participant marks the test complete in Gazelle. A volunteer monitor is observing a worklist. He/she will see an item for grading and walk over to grade the test. Some tests can be graded without visiting the participants who ran the test. The monitor enters the test result in Gazelle, and the cycle continues. During the evenings, Connectathon Managers review the individual test results and enter pass/fail grades in Gazelle for specific profile/actor pairs.
Items to bring to your attention:
- You can run tests in any order. With the exception of a few “Do This First” tests, order is not important.
- After you complete a test, you should start another test. Monitors are limited resources and may not appear immediately.
- The test cases indicate the kind of evidence needed to document the tests, and Gazelle provides a mechanism to store log information and screen captures. This is designed to make it easier for participants and monitors to find test results.
- In many instances, client applications initiate tests because that is a natural workflow. If you have server applications, you should be pro-active and seek out client applications for testing. Do not stand in the corner and wait for someone to ask you to dance.
- If you find a problem while running a test, you are allowed to update your application during the event and re-run the test later.