Difference between revisions of "Thorough Supportive Connectathon Testing"

From IHE Wiki
Jump to navigation Jump to search
(Created page with "== Thorough / Supportive Testing Explained == === What is Thorough Testing? === The list of required tests for each actor and profile is developed by the Connectathon Management...")
 
Line 1: Line 1:
== Thorough / Supportive Testing Explained ==
+
= Thorough / Supportive Testing Explained =
  
=== What is Thorough Testing? ===
+
== What is Thorough Testing? ==
 
The list of required tests for each actor and profile is developed by the Connectathon Management Team and is published for each Participant in Gazelle. '''Thorough testing''' at the Connectathon consists of successful completion by a Participant of three instances of each peer-to-peer test with three different test partners, and one instance of each no-peer test assigned for the Actor and Profile(s) it is testing during the Connectathon.  
 
The list of required tests for each actor and profile is developed by the Connectathon Management Team and is published for each Participant in Gazelle. '''Thorough testing''' at the Connectathon consists of successful completion by a Participant of three instances of each peer-to-peer test with three different test partners, and one instance of each no-peer test assigned for the Actor and Profile(s) it is testing during the Connectathon.  
  
 
An exception to the "three-instance" rule of Thorough testing is: In some profiles, there may not be sufficient registration to provide three different test partners for a test. In this case, the "three-instance" requirement is relaxed, and participants are required to test with each of the available partners, pehaps only one or two.
 
An exception to the "three-instance" rule of Thorough testing is: In some profiles, there may not be sufficient registration to provide three different test partners for a test. In this case, the "three-instance" requirement is relaxed, and participants are required to test with each of the available partners, pehaps only one or two.
  
=== What is Supportive testing?  Why would we do Supportive testing? ===
+
== What is Supportive testing?  Why would we do Supportive testing? ==
 
Participants who have successfully tested at a previous Connectathon may qualify to perform '''Supportive testing'''. The benefits of Supportive testing are:
 
Participants who have successfully tested at a previous Connectathon may qualify to perform '''Supportive testing'''. The benefits of Supportive testing are:
  
Line 12: Line 12:
 
* Participants receive full Connectathon credit for testing (ie a "pass) if they successfully perform one instance of at least one test for an Actor/Profile combination. Of course, you may choose to do more than one. This frees you up to spend more time testing new profiles if you wish.
 
* Participants receive full Connectathon credit for testing (ie a "pass) if they successfully perform one instance of at least one test for an Actor/Profile combination. Of course, you may choose to do more than one. This frees you up to spend more time testing new profiles if you wish.
 
* Participants undertaking Supportive testing are also required to assist other participants testing that profile who need a partner even if you have already completed your 'one required test'. Connectathon Managers will coordinate this additional testing as necessary.
 
* Participants undertaking Supportive testing are also required to assist other participants testing that profile who need a partner even if you have already completed your 'one required test'. Connectathon Managers will coordinate this additional testing as necessary.
 +
 +
== Who qualifies for Supportive testing? ==
 +
In order to qualify for Supportive testing, a Participant:
 +
 +
* Must previously have passed Thorough testing for that particular Actor and Profile at a Connectathon whose results are reported in the IHE database at http://connectathon-results.ihe.net/
 +
* Must also have published an IHE Integration Statement in the IHE Product Registry (http://product-registry.ihe.net/) for that Actor/Profile.
 +
 +
== How do we request to do Supportive testing? ==
 +
Supportive requests are now made directly in gazelle (''no more spreadsheet!'') and must be complete by the close of Connectathon registration.
 +
 +
*After logging in, select menu ''Registration --> Manage systems''
 +
* Edit the system of interest
 +
* Select the ''Profile/Actors'' tab.
 +
* In the column ''Requested testing type'', select ''Supportive'' for the corresponding profile/actor.
 +
After registration closes, the Connectathon Technical Project Managers will review and approve your request based on the criteria in the previous section. If you don't meet the criteria, you will do Thorough testing.

Revision as of 14:53, 25 February 2014

Thorough / Supportive Testing Explained

What is Thorough Testing?

The list of required tests for each actor and profile is developed by the Connectathon Management Team and is published for each Participant in Gazelle. Thorough testing at the Connectathon consists of successful completion by a Participant of three instances of each peer-to-peer test with three different test partners, and one instance of each no-peer test assigned for the Actor and Profile(s) it is testing during the Connectathon.

An exception to the "three-instance" rule of Thorough testing is: In some profiles, there may not be sufficient registration to provide three different test partners for a test. In this case, the "three-instance" requirement is relaxed, and participants are required to test with each of the available partners, pehaps only one or two.

What is Supportive testing? Why would we do Supportive testing?

Participants who have successfully tested at a previous Connectathon may qualify to perform Supportive testing. The benefits of Supportive testing are:

  • Participants are not required to perform pre-Connectathon tests for a supportive profile/actor pair (because you have done it in the past).
  • Participants receive full Connectathon credit for testing (ie a "pass) if they successfully perform one instance of at least one test for an Actor/Profile combination. Of course, you may choose to do more than one. This frees you up to spend more time testing new profiles if you wish.
  • Participants undertaking Supportive testing are also required to assist other participants testing that profile who need a partner even if you have already completed your 'one required test'. Connectathon Managers will coordinate this additional testing as necessary.

Who qualifies for Supportive testing?

In order to qualify for Supportive testing, a Participant:

How do we request to do Supportive testing?

Supportive requests are now made directly in gazelle (no more spreadsheet!) and must be complete by the close of Connectathon registration.

  • After logging in, select menu Registration --> Manage systems
  • Edit the system of interest
  • Select the Profile/Actors tab.
  • In the column Requested testing type, select Supportive for the corresponding profile/actor.

After registration closes, the Connectathon Technical Project Managers will review and approve your request based on the criteria in the previous section. If you don't meet the criteria, you will do Thorough testing.