Medical Data Management Test Plan

Service Description

See: MDM documentation, the tests can be found here

These are the tests for testing the Medical Data Management components of EGEE. The full MDM components include the MDM CLI tools, a DICOM server, a modified DPM service, Hydra, AMGA and contact to a LFC service. The DICOM server (by default Conquest), Hydra, AMGA and LFC can be external. To make the tests simpler, Hydra, AMGA, and LFC are expected to be external, and not part of the installation. Hence the installation comprises of the MDM CLI tools, the DPM service and the DICOM server. The DICOM server can be on a separate machine, and in many usage scenarios it will be. However it doesn't affect the tests, so for simplicity it can be on the same machine as the MDM tools.

The tests at this point use one machine which acts as a MDM server and a client machine. This will probably change in the future when there are proper client/server package separation. The machine contains the DICOM-DPM, DICOM and the glite-mds* commands. You need at least once test user certificate on the machine. With two certificates the access control will be tested too. The tests can be run with default parameters, or they can use specific parametes/environment variables as described in README.

Features/Scenarios to be tested

Service ping test (implemented)
This test checks the availability of all required services, including the external Hydra and AMGA servers.

Normal workflow - correct input
This test uses the machine's configuration to determine if the required services are responding.

Pass/Fail Criteria
This test succeeds if all services are running, otherwise it fails.

Error workflow - erroneous input
N/A

Pass/Fail Criteria
N/A

DICOM image registration/removal (implemented)
This test tries to register a dicom image to the MDM service, and confirms that is has been registered. It then tries to remove the image and confirms that that also works. This test uses parameters from the configuration files. The test checks that specified input files and certificates exist.

Normal workflow - correct input
This test tries to register a file, and confirms that it is registered. Then the test removes the image, and confirms that it is removed from all services. The test reports the success of the individual steps.

Pass/Fail Criteria
This test succeeds if all stages of the test pass. Any error in the input files, or the tested features make the test fail.

Error workflow - erroneous input
This test checks that it's not possible to register the same image twice, or to register a non-dicom image. It also confirms that removing a nonexisting image gives an error.

Pass/Fail Criteria
This test succeeds if all stages of the test pass (return errors).

DICOM image retrieval (implemented)
This test depends on the previous test. It checks that the registered image can be retrieved. This test uses parameters from the configuration files. The test checks that specified certificates exist.

Normal workflow - correct input
This test tries to retrieve the stored image with the MDM tools, and verifies that it is intact. After that it tries to retrieve the image with standard gLite tools and verifies that it gets the same result. The test reports the success of the individual steps.

Pass/Fail Criteria
This test succeeds if all stages of the test pass. Any errors in the tested features make the test fail.

Error workflow - erroneous input
The test confirms that retrieving a nonexisting image gives an error.

Pass/Fail Criteria
This test succeeds if all stages of the test pass (return errors)

DICOM image permission changes (implemented)
This test depends on the previous tests. It checks that the permissions of the registered image are changed. This test uses parameters from the configuration files. The test checks that specified certificates exist.

Normal workflow - correct input
This test tries to change the permission of the saved DICOM images, with different options. It then checks with standard gLite tools that the permissions are correctly altered in all services. These include LFC, AMGA, Hydra and DPM. This test does not check if permissions are enforced, that's up to the services. The test reports the success of the individual steps.

Pass/Fail Criteria
This test succeeds if all stages of the test pass. Any errors in the tested features make the test fail.

Error workflow - erroneous input
This test confirms that changing permissions for a nonexisting image gives an error. It also tests that giving badly formatted permission strings gives an error.

Pass/Fail Criteria
This test succeeds if all stages of the test pass (return errors). Any errors in the tested features make the test fail.

Features not to be tested

-- KalleHapponen - 04 Feb 2009

Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2009-02-12 - KalleHapponen
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback