Summary
1) Document Status
This document is currently being drafted
2) Perspective
The VIVO webapp is a sophisticated computer program whose evolution is guaranteed by continuous software development using an Agile software engineering methodology. In this engineering approach, the software testing process must also be managed continuously and be adaptive to new developments that occur over time. The Vivo-regression-testing tool aims to provide the software developer with a test bench integrated into its development environment.
Needs
For the IT developer, the test bench is designed to meet the following needs:
- Offer a regression test ecosystem by simulating user actions from the VIVO user interface.
- Enable regression test design
- Allow regression testing to be performed
- Provide unified tools for managing the execution of VIVO instances
- Provide an environment for running comparative tests on multiple instances of VIVO at the same time
- Running Regression Tests in Batch Mode
What we want to test:
In the context of vivo-i18n
- User interface consistency as corrections are made to the various windows
- Integrity of data in the triplestore when updating through the user interface in a multilingual context
- Ontological cohesion and user interfaces between the original version (1.11.1) of VIVO and its corollary en_US of VIVO-i18n (1.11.2-SNAPSHOT)
Usage context
The test bench usage is illustrated according to the process described below
| Test case building process illustration | Description |
|---|---|
| Step 1)Selenium includes a recorder that captures the interaction between the user and the browser. The capture of the interaction is stored in the form of a Selenium script. Step 2)The translation of the Selenium script is translated into a JUnit Test Case to which it is necessary to make adjustments for the interpretation of the actions. Step 3)The Java Unit Test is suited for a generalized use in multiple language contexts. Step 4)The test bench encapsulates a set of features and properties that are necessary to parameterize the execution of test cases. This step aims to integrate the test case into these execution parameters. Step 5)Once integrated into the test bench, the test case can be triggered by the development in a singular way or in batch mode according to the needs of the moment. |
