You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Testing Plan

Before testing, please review the VIVO 1.12.x Documentation.

Cloning the release candidate from GitHub

To test the release candidate of VIVO 1.12.0, you will need to build the correct versions of Vitro-languages and VIVO-languages even if you only use VIVO in American English.


Clone the rel-1.12.0-RC branch of the four required GitHub projects into parallel directories.  Then build Vitro-languages and VIVO-languages.


git clone --single-branch --branch rel-1.12.0-RC https://github.com/vivo-project/Vitro-languages.git
git clone --single-branch --branch rel-1.12.0-RC https://github.com/vivo-project/VIVO-languages.git
git clone --single-branch --branch rel-1.12.0-RC https://github.com/vivo-project/Vitro.git
git clone --single-branch --branch rel-1.12.0-RC https://github.com/vivo-project/Vitro.git

cd Vitro-languages
mvn install
cd ../VIVO-languages
mvn install


Then proceed with the rest of the VIVO installation or upgrade according to the VIVO 1.12.x Documentation.  Be sure that if you are testing a clean installation, be sure to supply an empty vivo-dir in your settings.xml file.  If you are testing an upgrade, make a copy of your existing VIVO 1.11 vivo-dir directory and supply the location of that copy as the value of vivo-dir in your settings.xml file.

Performing the Tests and Submitting Results

Please follow the test items and submit your results using the Google forms below.  Any parts of any of the forms that you are able to complete will be most welcome.  To see what items still need testing, you can use the reponse summary links to check for questions that do not yet have responses.

1. Internationalization Tests (response summary) : these tests exercise new functionality in version 1.12.0.

2. Standard UI Tests (response summary) : these tests exercise standard functionality in the VIVO user interface.

3. Advanced Tests (response summary) : these tests are intended for software developers.


  • No labels