This topic explains how you can check that the client and server parts of a URA System are working correctly when it has been moved into a production environment.
Prerequisites: The production URA System should have been either updated from v1.0.0.14 or result from a new database setup.
Note: The troubleshooting section may help you resolve problems detected during testing
Testing the Client (v1.0.0.17 only)
To test the client part of the URA System you should install osImageManager's UAT Feature and alter your Configuration File so you can run the User Acceptance Tests using a system test database rather than the one you use for production. In this way you should be able to resolve any problems with osImageManagerApp on a particular PC.
Caution: Remember to deinstall the UAT feature and restore your Configuration File upon the completion of your testing.
Testing the Server (v1.0.0.14 and v1.0.0.17)
To test the server part of the URA System you should check that the stored procedures on the Image and Patient databases are working correctly when invoked from osImageManagerApp. This can be acheived by logging on as a URA-Admin and then running the functional test described below.
Patient Database - the URA System only reads data from the Patient database so you can run these functional tests without making any changes to production data.
GetNameFromVolunteerRef and MatchScanDateForVolunteerRef - Open the Import Images dialog box and use the browse button to select an image file that you know has already been added to the Image database without requiring any correction. Press the read button and check that the file appears in the corrections list as a duplicate and doesn't have a name mismatch or orphan error.
ListVolunteerRefForNames, ListNameForVolunteerRef, ListScanDatesForVolunteerRef - open the Database Admin dialog box and enter a known Volunteer Reference number as well as the corresponding names in the text boxes. Press the Test PatientDb button and check the results box displays the expected name, volunteer reference and list of scan dates.
Image Database - the URA System writes data to the Image database and reads data from it. Accordingly you should backup the Image database before performing any of the functional tests marked write and restore it again afterwards.
GetAllmageDetailsForDiskRef and GetImageDetails - Open the Images For Disk Ref dialog box and enter a known Disk Ref number in the text box. Press 'OK' and check that the treeview is populated as you expect.
GetAlImageDetailsForVolunteer and GetImageDetails - Open the Images For Volunteer dialog box and enter a known Volunteer Reference number in the text box. Press 'OK' and check that the treeview is populated as you expect.
GetImage - Perform the above tests and then select an image item in the treeview. The ultrasound record should appear in the image view.
GetImageIDFromDICOMRef - Open the Import Images dialog box and use the browse button to select an image file that you know has already been added to the Image database. Press the read button and check that the file appears in the corrections list as a duplicate.
UpdateImage (write) - Perform the above test and then press the accept button to move the file into the ready for import list. Enter 'SysTest-1' in the Disk Ref text box, press import and check that the treeview then contains this image record.
InsertImage (write) - Open the Import Images dialog box and use the browse button to select one of the test image files. Press the read button and check that the file appears in the corrections list. Apply any corrections to the file so that you can move it into the ready for import list. Enter 'SysTest-2' in the Disk Ref text box, press import and check that the treeview then contains this image record.
DeleteImage (write) - Perform the above test and then select the imported image item in the treeview. Apply delete image from the edit menu and check that the image disappears. Open the Images For Disk Ref dialog box and enter 'SysTest-2' in the text box. Press 'OK' and check that the treeview doesn't contain the image.
DeleteDiskRefImages - only used for UAT. It has no production application and so doesn't need to be tested.