25/02/2009 INDEX Introduction 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 4 5 DRI Repository generator tool DRI Generic viewer DRI Test tool Conclusions DRI Test architecture Layers Structure of the test environment is similar to gLibrary/DRI platform The internal processes the test performs are quite similar to the steps a normal user would perform in a complete use case in which he access to the repository by uploading and then saving a complete-structure node, including those data marked as LFN which will be stored on the SE. Two main parts: The entry point, which includes testing the login applet, the application server testing and the PHP-Java Bridge. The other part is aimed to test the whole gLibrary/DRI and repositories deployed at the platform and focusing on the functionality of the core operations, such us insert, load and remove a certain number of nodes. The test check also APIs gLibrary/DRI platform (LFC, Servlet, etc) The test is aimed to repository providers for checking the integrity of their repositories 17