| Table of Contents |
|---|
Testing
...
None
Resources
RC-1
- Link to RC-1 war file
- Link to RC-1 Docker container
Testing Plan
New Installation Tests
Remove application data
| Code Block | ||
|---|---|---|
| ||
rm -rf ${VIVO_HOME}/tdbModels/
rm -rf ${VIVO_HOME}/tdbContentModels/
rm -rf ${VIVO_HOME}/rdf/ |
Start Tomcat
| Code Block | ||
|---|---|---|
| ||
sudo systemctl start tomcat9.service |
UI Tests
Note these are run manually, it might be possible to reconcile these test with this automated test suite : https://github.com/vivo-community/vivo-acceptance-tests
...
Smoke tests do not produce error
(warning about email server is OK)
...
Mac
Linux
Windows
...
Home page displays correctly
...
Mac
Linux
Win/Lnx
Windows
...
Mac
Linux
Win/Lnx
Windows
...
Mac
Linux
Win/Lnx
...
Mac
Linux
Win/Lnx
Windows
...
Site Admin - Add Individual of this class:
Faculty Member (People)
Project (Activities)
Course (Courses)
Academic Article (Research)
Presentation (Events)
Academic Department (Organizations)
Populated Place (Locations)
...
Mac
Linux
Win/Lnx
Windows
...
Creation of a FacultyMember without a middle name results in extra whitespace attached to the end of rdfs:label value.
The default list view for publications doesn't show the issue number for articles, which seems weird, but it appears to have been this way since at least 1.9 (as with the rds:label bug above).
...
Mac
Linux
Win/Lnx
Windows
...
Check menu entries
(Home, People, Organizations, Events, Capability Map)
...
Mac
Linux
Win/Lnx
Windows
...
Check Person display
(logged out, logged in)
...
Mac
Linux
Windows
...
All is a heavy lift. 64 attributes accessible from the person page, some of which lead to entities (publications, positions, etc)) each with their own attributes.
Recommended: Add photo, overview, URL, research areas, position. Each exercises different functionality.
...
Check tabs on Person display
(overview, publications, contact, etc.)
...
Mac
Linux
Win/Lnx
...
Add new publication to person
(check required fields)
...
Mac
Linux
Win/Lnx
...
Check manage publications
(hide / show publications)
...
Mac
Linux
...
Check Publication view
...
Mac
Linux
Win/Lnx
...
Check AltMetric badge
(e.g. doi: 10.1038/nrmicro2331)
...
Mac
Win/Lnx
...
Mac
Linux
Win/Lnx
...
Mac
Linux
Win/Lnx
...
Mac
Linux
Win/Lnx
...
Mac
Linux
Win/Lnx
...
Mac
Linux
Win/Lnx
...
Mac
Linux
Win/Lnx
...
Mac
Linux
Win/Lnx
...
Mac
Linux
...
Mac
Linux
...
Mac
Win/Lnx
...
Mac
Linux
...
Mac
Linux
...
Mac
Linux
Win/Lnx
...
Mac
Linux
...
Mac
Linux
...
Mac
Linux
...
Mac
Windows
...
Mac
Windows
...
Check TPF endpoint
(enable if necessary)
...
Mac
Linux
Windows
...
Works as designed. 45,279 triples with VIVO data, sample data, and some manually entered test data. Design needs work.
/tpf/core displayed triples and enabled triple pattern matching by subject,predicate, or object. (43,173 triples in total)
...
Mac
Linux
Windows
...
API Tests (reference: VIVO APIs)
...
Linked Open Data
...
# From Site Admin: Create a new `Faculty Member` (Add individual)
** Record the new URI: http://localhost:8080/vivo/individual/n1323
# Verify `individual` endpoint:
| Code Block |
|---|
curl http://localhost:8080/vivo/individual/n1323/n1323.ttl
curl http://localhost:8080/vivo/individual/n1323/n1323.n3
curl http://localhost:8080/vivo/individual/n1323 -L -H "Accept: text/turtle" |
...
curl http://localhost:8080/vivo/listrdf -d 'vclass=http://vivoweb.org/ontology/core#Continent'
curl http://localhost:8080/vivo/listrdf -d vclass=http://vivoweb.org/ontology/core#Continent
...
Triple Pattern Fragments
http://localhost:8080/vivo/tpf/core
http://localhost:8080/vivo/tpf
curl http://localhost:8080/vivo/tpf/core
...
# Verify browsing:
http://localhost:8080/vivo/tpf/core
http://localhost:8080/vivo/tpf
Minor observation: When TPF is disabled, it's great that the exception thrown explains how to enable it, but returning a 500 code with a stacktrace doesn't necessarily seem like the most graceful way of handling the situation. I might expect a 404 (TPF server simply doesn't exist on the site) or maybe a 501? (Request is valid, but functionality is not implemented.) The 500/stacktrace suggests to me that something is wrong with my installation.
# Verify direct access:
curl http://localhost:8080/vivo/tpf/core?subject=http://localhost:8080/vivo/individual/n1323
...
Linux
Windows
...
Linux
Windows
API works. In the course of loading approx. 90K triples via the API, this search index-related warning appeared in the log a handful of times: 2019-09-26 16:26:39,453 WARN [ConcurrentUpdateSolrClient] No more runners, but queue still has 1 adding more runners to process remaining requests on queue
Plan
Before testing, please review the VIVODOC112x.
Cloning the release candidate from GitHub
| Note |
|---|
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 rel-1.12.0-RC branch of the four required GitHub projects into parallel directories. Build Vitro-languages and VIVO-languages.
| Code Block |
|---|
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 VIVODOC112x. 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.
...
This works in the UI, but unable to get "curl" to work. Using:
curl -i -XPOST -d 'email=vivo_root@mydomain.edu' -d 'password=xxx' -d 'datafile=@uriList.txt' 'http://localhost:8080/vivo/searchService/updateUrisInSearch'
...
macOs
Linux
...
Did not work following instructions for 1.10. Changing the DDAPI version from 1.1 to 1.1.1 DID work. Following instructions for building a snapshot version, which involved adding a repository tag, also worked.
Pull request submitted to DDAPI repo to update documentation: https://github.com/vivo-community/vivo-data-distribution-api/pull/9
...
Linux
Mac
...
Unload/Load Tests
...
Unload using jena2tools -e
(using jena3tools -e Andrew Woods )
...
Triplestores Tests
...
Upgrade Tests
...
Export data with jena2tools
| Code Block | ||
|---|---|---|
| ||
java -jar jena2tools.jar -e -d /usr/local/vivo/home |
...
Performance Tests
Performance tests should compare run times for a 1.11 vs a 1.12 on same hardware, same data.
Timing collection may be facilitated by enabling The Developer Panel.
...