Testing Blocker Tickets
None
Testing Plan
Prepare installation (build from source)
git clone https://github.com/vivo-project/Vitro.git Vitro git clone https://github.com/vivo-project/VIVO.git VIVO cd Vitro git checkout rel-1.11.0-RC-1 cd ../VIVO git checkout rel-1.11.0-RC-1 cp ./installer/example-settings.xml local-settings.xml # Update local-settings.xml with appropriate `vivo-dir` and `tomcat-dir`
Sanity Builds
Command | Platform | Tested by | Success? | Notes |
---|---|---|---|---|
mvn clean install -s local-settings.xml | Linux | |||
mvn clean install -s local-settings.xml | Mac Mac | |||
mvn clean install -s local-settings.xml | Windows | Used version of settings that I already had (with appropriate directories specified). |
New Installation Tests
- Prepare installation, see above
Empty MySQL database
mysql -u root -p mysql> drop database vitrodb; mysql> CREATE DATABASE vitrodb CHARACTER SET utf8; mysql> GRANT ALL ON vitrodb.* TO 'vitrodbUsername'@'localhost' IDENTIFIED BY 'vitrodbPassword'; *Note: For MySQL 8, the commands for setting up the user and granting permissions are separated: mysql> CREATE USER'vitrodbUsername'@'localhost' IDENTIFIED BY 'vitrodbPassword'; mysql> GRANT ALL ON vitrodb.* TO 'vitrodbUsername'@'localhost';
Remove application data
rm -rf ${VIVO_HOME}/tdbModels/* rm -rf ${SOLR_HOME}/server/solr/vivocore/data/*
3.5. Ensure runtime.properties is set up in ${VIVO_HOME}/config by copying over example,runtime.properties and specifying the URL of the Solr instance you wish to use with this VIVO deployment. Also you've copied over example.applicationSetup.n3 to applicationSetup.n3 in the same folder.
Start Tomcat
sudo service tomcat8 restart
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
Test | Platform | Tested by | Success? | Notes | |
---|---|---|---|---|---|
1 | Smoke tests do not produce error (warning about email server is OK) | Mac Linux Windows | Linux Mint 19 Cinnamon | ||
2 | Home page displays correctly | Mac Linux Win/Lnx Windows | |||
3 | Log in as admin | Mac Linux Win/Lnx Windows | |||
4 | Site Admin page displays correctly | Mac Linux Win/Lnx | |||
5 | Each function on site admin display correctly | Mac Linux Win/Lnx Windows | All 24 links (including Data Input Pull down) display normally. Ontology list All looks good | ||
6 | 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). | ||
7 | Check required fields in creating classes | Mac Linux Win/Lnx Windows | |||
8 | Check menu entries (Home, People, Organizations, Events, Capability Map) | Mac Linux Win/Lnx Windows | |||
9 | Check Person display (logged out, logged in) | Mac Linux Windows | |||
10 | Add values to all Person attributes | Mac |
| 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. | |
11 | Add research areas using vocabulary services | Mac | UMLS service requires registration key. See Release Notes. Unclear where this key would go. Other services respond as expected. BG: Created Jira issue for UMLS | ||
12 | Check tabs on Person display (overview, publications, contact, etc.) | Mac Linux Win/Lnx | |||
13 | Add new publication to person (check required fields) | Mac Linux Win/Lnx | |||
14 | Check publication sparkline | Mac | |||
15 | Check manage publications (hide / show publications) | Mac Linux | |||
16 | Check Publication view | Mac Linux Win/Lnx | |||
17 | Check AltMetric badge (e.g. doi: 10.1038/nrmicro2331) | Mac Win/Lnx | Poor UI experience. I copied in the link, which copied in the HTML tagging, which led to showing the HTML tagging in the display. The edit form is open ended HTML, should be plain text. Should indicate what form of DOI is expected , or should accept with or without http:// without without "doi". | ||
18 | Add author(s) to publication | Mac Linux Win/Lnx | |||
19 | Check Person has co-author network | Mac Linux Win/Lnx | |||
20 | Check co-author network display | Mac Linux Win/Lnx | |||
21 | Add grants to Person | Mac Linux Win/Lnx | |||
22 | Add co-investigators to grants | Mac Linux Win/Lnx | |||
23 | Check Person has co-investigator network | Mac Linux Win/Lnx | |||
24 | Check co-investigator network display | Mac Linux Win/Lnx | |||
25 | Load Sample Data | Mac Linux | |||
26 | Check Capability Map | Mac Linux | Need more sample data with more concepts for more extensive tests. | ||
27 | Check Map of Science | Mac Win/Lnx | |||
28 | Check Temporal Graph | Mac Linux | |||
29 | Search for "Derrida" | Mac Linux | |||
30 | Check index page | Mac Linux Win/Lnx |
| ||
31 | Create self editor login associated with profile | Mac | Updated documentation to describe how this is done. See Creating and Managing User Accounts#AssociatingUserAccountswithProfilePages | ||
32 | Log in as self editor. Verify can edit self, cannot edit others. | Mac | |||
33 | Add and confirm an ORCiD | Mac | ORCiD API configuration requires clientId and clientPassword and public VIVO. See Activating the ORCID integration | ||
34 | Create editor and assign proxy editing | Mac Windows | Created user account with editor role and assigned proxy editing. Also switched to self-editor role. | ||
35 | Log in as proxy editor. Verify can edit proxied profile, cannot edit others. | Mac Windows | When logged in as self-editor designated as a proxy editor, I can only edit the proxied profile and not a different profile. When logged in as editor (i.e. the editor role which is different from self-editor), I can edit the proxied profile but also other profiles. Works as it should. | ||
36 | Check TPF endpoint | Mac 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) | ||
37 | Run a SPARQL query | Mac Windows |
API Tests (reference: VIVO APIs)
Test | Platform | Tested by | Success? | Notes | |
---|---|---|---|---|---|
1 | Linked Open Data | Linux | Ralph O'Flinn | # From Site Admin: Create a new `Faculty Member` (Add individual) 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" for windows using cURL for Windows 7.46 | |
ListRDF | Linux | Ralph O'Flinn | 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 | ||
3 | Triple Pattern Fragments http://localhost:8080/vivo/tpf/core | Linux | # Verify browsing: # Verify direct access: | ||
4 | SPARQL Query API | Linux Windows | |||
5 | SPARQL Update API | Linux Windows | API works. In the course of loading approx. 90K triples via the API, this search index-related warning appeared in the logs 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 | ||
6 | Search Indexing API | Linux | |||
7 | Data Distribution API | 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. Huda KhanDo you have the ability to create instructions on cul-it.github.io for 1.11? | ||
8 | Direct2Experts API | Linux Mac |
Unload/Load Tests
Test | Platform | Tested by | Success? | Notes | |
---|---|---|---|---|---|
1 | Load data using the Harvester | Linux | |||
2 | Unload using jena2tools -e (using jena3tools -e Andrew Woods ) | Windows | Linux | |||
3 | Load using jena3tools -i | Windows | Linux | |||
4 | Load sample data to a named graph | Windows | Linux | Ralph O'Flinn | ||
5 | Remove sample data named graph | Windows | Linux | Ralph O'Flinn |
Triplestores Tests
Test | Platform | Tested by | Success? | Notes | |
---|---|---|---|---|---|
1 | SDB | ||||
2 | TDB | Windows | Brian Lowe | ||
3 | BlazeGraph |
Upgrade Tests
- Install previous release
- Prepare installation per instructions above for previous release
- Start Tomcat - check that smoke test passes
- Stop Tomcat
Export data with jena2tools
java -jar jena2tools.jar -e -d /usr/local/vivo/home
Empty MySQL
mysql -u root -p mysql> drop database vitrodb; mysql> CREATE DATABASE vitrodb CHARACTER SET utf8; mysql> GRANT ALL ON vitrodb.* TO 'vitrodbUsername'@'localhost' IDENTIFIED BY 'vitrodbPassword';
Remove application data
rm -rf ${VIVO_DIR}/tdbModels/* rm -rf ${VIVO_DIR}/solr/data/*
Import data with jena3tools
java -jar jena3tools.jar -i -d /usr/local/vivo/home
- Start Tomcat
Verify application per `UI Tests` above
Test Platform Tested by Success? Notes All UI Tests Windows | Linux All API Tests Windows | Linux All Unload/Load tests Windows | Linux All performance tests
Vagrant Tests
Clone VIVO Vagrant
git clone https://github.com/vivo-community/vivo-vagrant.git
Checkout release candidate
cd vivo-vagrant git checkout rel-1.11.0-RC-1
Load local or sample data
- Verify application per `UI Tests` above
Test | Platform | Tested by | Success? | Notes |
---|---|---|---|---|
All UI Tests | Linux | Mac | Windows | |||
All API Tests | ||||
All Unload/Load Tests | ||||
All performance tests |
Performance Tests
Performance tests should compare run times for a 1.10 vs a 1.11 on same hardware, same data.
Timing collection may be facilitated by enabling The Developer Panel.
Test | Platform | Tested by | Success? | Notes | |
---|---|---|---|---|---|
1 | Compare firsttime starttime time | Linux | Mac | Windows | |||
2 | Compare performance data load time | ||||
3 | Compare profile display time | ||||
4 | Compare SPARQL query time | ||||
5 | Compare Search Index rebuild time | ||||
6 | Compare Inferencer rebuild time | ||||
7 | Compare jenatools export time | ||||
8 | Compare jenatoools import time | ||||
9 | Compare Data Distribution API response time |