I. Presentation

TestManagement Tests are dedicated to simulate the main actions a user can do on the Gazelle application, from creating a new institution account to configuring a system.
All the tests are described as scenarios, each one is associated to a particular object as institution, system, users.

The developpment tools used for these tests are:
• Java
• Selenium
Implemented as a Firefox extension, it allows the generation of automated tests for web applications. Hence, it is possible to record, edit, and debug tests.
• TestNG
It is a testing framework designed to simply implement a broad range of testing needs

The package for TestManagement tests called "unitTests" is divided into 2 parts:
• testsClasses, containing all the classes of tests. Each of these classes defines a scenario.
• testsMethods, composed of all the methods used in the different tests. Each class contains methods for a given part in the menu bar. This part is described in the title of the class itself.
e.g: RegistrationMethods class contains all the methods linked to the checking of Registration tabs and access to the associated pages

The unitTests package also contains the TestsParametersConfiguration class at its root, encharged of defining all the variables used in the different tests' classes. Hence, to update a value, it is only necessary to update it in this file.


• While tests processing, some screenshots of the application are taken and stored in the folder defined as "testng-screenshot" in the build-dev/build-prod.properties file of TestManagement-ear project.
• In order to optimize this processing, the tests in a scenario are grouped into phases. Each phase corresponds to the login of a user, e.g. the Gazelle administrator, or the institution of an given institution. The phases chronologically depend on the others.
• In the "doc" folder, some FreeMind files are defined to allow an ergonomic management of the scenarios.
  A scenario is represented as a cloud, and each phase among it is represented by specific number and color.
  Each node defines a test in the scenario. Depending on the phase, a node can be represented with a coloured background.
  e.g: The phase corresponding to the login of the Gazelle Administrator is representated by nodes with a yellow background.
• In the same folder is the TestsScenarios document (.xls format), which contains all the tests' name with associated definition and phase

III. Tests description

Here are the followings tests' scenarios and their main features:


• UserAccountManagement
This scenario is encharged of testing institution and user account definition, parameters' updates and verifications of correct display on pages.
The UserAccountsTests file gives an accurate description of the scenario, whose phases are identified by specific colors in the background of the nodes (each node stands for a test)


• SystemAccountManagement
This scenario consists in creating a system, adding/deleting integration profiles/actors, attributing HL7/DICOM integration statement URLs.
The SystemsManagementTests file describes this scenario in details.


• GazelleAdminAvailablePagesTests
Logged as the Gazelle administrator, the scenario consists in checking that all the required tabs are available and that the pages are accessible.


• UsersAvailablePagesTests
After creating all kinds of users, the tests are to check that the pages available for each type of user are accessible.