Technical organization of a test session

This page gives guidance to organize a testing session "Connectathon" or "Projectathon" when the team at KEREVAL is asked to provide the technical support. The content of this page is aimed to describe the various tasks compiled in the Google spreadsheet "RIDA - Technical support to test session". This spreadsheet is a template and shall be duplicated for each new test session.

RIDA Structure

This section gives an overview of the tabs available in the document.

  • Decisions: List all the decisions made in relationship with the organization of the event.
  • Informations: List all the informations which are shared in the context of the organization. This tab is a place for everybody to have the same level of information and to log all useful informations which have an impact on the organization of the event.
  • Actions: Each line is an action that shall be conducted before, during or after the event takes place. The owner of the task has the responsibility to make sure that the task has been executed within the agreed period. He/she might not execute the task hisself/herself. When a date is highlighted in red, it means that the associated task is overdue.
  • KPI Actions: Overview of the progress based on the status of the actions.
  • Machines: When we organize an on-site event (European connectathon, EPD projectathon, etc), we move some of tools to the testing floor. This tab lists the physical devices along with their IP addresses and hosted applications. It is used to configure the devices on site but also to communicate to the person in charge of the network what are the ports to open and the NAT to be performed to allow access to the tool from outside the event network.
  • VM transport: This tab has two purposes:
    • on which physical devices are the virtual machines hosted during the event
    • where are located the back ups when we go back home and who is responsible for bringing the storage device
  • VM Retour actions: List of all the actions to be performed from Friday, noon when we shutdown Gazelle in order to have all the applications running in production servers the earliest.
  • A emporter: List of the items that shall be brought to the testing floor.
  • Found issues: The place to list the issues found during the installation test campaign on Sunday (or any day prior to the test event once the tools have been moved locally)
  • Paramètres: This is the tab where you can list the participants to this spreadsheet in order to select them in the other tabs.

Actions

This section gives guidance on how to execute the actions which are listed in the spreadsheet under the "Actions" tab. Not all the actions are listed below, only those which are not trivial.

Management

Provide local IHE with the list of t-shirts

Prepare the table label for printing:

  • Make sure that all systems and monitors have the right table in Gazelle TM
  • All the resources needed are in the project CAT_setup (https://gforge.inria.fr/scm/viewvc.php/gazelle/scripts/CAT_setup)
  • use the script get_list_of_tables.sql to get the table with the Name, the Keyword and the Label from Gazelle TM. Save it in a .csv file (do not forget to update the Test Session id)
  • Open the file tablesLabelTemplate.docs. Edit the list used by the mailing to use the csv file just created.
  • Click on finish and merge. That creates new .docs file with all the labels
  • Check that all pages are well displayed. Do not hesitate to adapt police size.
  • Test by printing one page with the real format.

Technical tasks before the event

Rsync data from OVH1 to CAT server (Also to do on-site before the event)

All the scripts can be found in ~/CAT_setup/data_and_databases on the CAT server :

  • copy-data-from-OVH1-to-CAT.sh : synchronize the /opt/gazelle/2010 from ovh1 with the /opt/gazelle folder
  • copy-gazelle-proxy.sh : retrieve the proxy database from OVH1
  • copy-ihe-europe-2010.sh : retrieve the ihe-europe-2010 database from OVH1

Technical tasks on-site (before event)

Configure the Central Archive

The Central Archive stands for a PACS that is used by some systems to store/retrieve images for testing purpose. Central Archive only allowed a well-known list of AETitle to contact it. A script allows to update this list by reading the systems' configurations in Gazelle Test Management. Read here how to configure it for each test event.

Technical tasks on-site (after event)

Technical tasks after the event

Update Connectathon results matrix

Once the connectathon report gets approvals from the IHE Intl board, results shall be published at https://connectathon-results.ihe.net Instructions to update the Connectathon result matrix are given at https://gazelle.ihe.net/content/management-connectathon-result-matrix

Training material and other templates