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

Compare with Current View Page History

« Previous Version 69 Next »

Testers may either put their results directly in this wiki page, or in the testing Google spreadsheet.


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.10.0-RC-1

cd ../VIVO
git checkout rel-1.10.0-RC-1


cp ./installer/example-settings.xml local-settings.xml
# Update local-settings.xml with appropriate `vivo-dir` and `tomcat-dir`

Sanity Builds

CommandPlatformTested bySuccess?Notes

mvn clean install -s local-settings.xml

Linux(tick)Built from source

mvn clean install -s local-settings.xml

Mac

Mac

(tick)

(tick)

Built from source

mvn clean install -s local-settings.xml

Mac

Linux

Mac

(tick) 


(tick)

Built from distribution

mvn clean install -s local-settings.xml

Windows(tick)Built from source

New Installation Tests

  1. Prepare installation, see above
  2. 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';
  3. Remove application data

    rm -rf ${VIVO_HOME}/tdbModels/*
    rm -rf ${VIVO_HOME}/solr/data/*
  4. Start Tomcat

    sudo service tomcat8 restart

UI Tests


TestPlatformTested bySuccess?Notes
1

Smoke tests do not produce error

(warning about email server is OK)

Mac

Linux

Windows

(tick)

(tick)

(tick)


2

Home page displays correctly

Mac

Linux

(tick) 

(tick)

Wait for indexing, refresh.
3Log in as admin

Mac

Linux

(tick) 

(tick)


4Site Admin page displays correctly

Mac

Linux

(tick) 

(tick)

Shows startup status warning re email
5Each function on site admin display correctlyMac

(tick) 

(tick)

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

(tick)

(tick)

Works as designed
7Check required fields in creating classesMac(tick)

 

Not sure what this test is? VIVO only requires labels as individuals are created.
8

Check menu entries

(Home, People, Organizations, Events, Capability Map)

Mac

Linux

(tick)

(tick)

Works as designed.
9

Check Person display

(logged out, logged in)

Mac

Linux

(tick)

(tick)

 

Works as designed.
10Add values to all Person attributesMac(tick)

 

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.

11Add research areas using vocabulary servicesMacUnable to completeUMLS service requires registration key. See Release Notes. Unclear where this key would go. Other services respond as expected.
12

Check tabs on Person display

(overview, publications, contact, etc.)

Mac

Linux

(tick)

(tick)

Works as designed.
13

Add new publication to person

(check required fields)

Mac

Linux

(tick)

(tick)

Works as designed.
14Check publication sparklineMac

(error) Test failed

(error)

The Information icon (info) below the sparkline can not be clicked.


^^^ confirmed. This may have been broken for awhile. The link doesn't work on Scholars@Duke either.

15

Check manage publications

(hide / show publications)

Mac

Linux

(tick)

(tick)

Works as designed. (I don't think I'd ever tried this. Works well.)
16

Check Publication view

Mac

Linux

(tick)

(tick)

Works as designed.
17

Check AltMetric badge

(e.g. doi: 10.1038/nrmicro2331)

Mac(tick)

 

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".
18Add author(s) to publicationMac(tick)

(tick) 

Works as designed.
19Check Person has co-author networkMac(tick)

(tick)

Works as designed.
20Check co-author network displayMac(tick)

(tick)

Works as designed
21Add grants to PersonMac(tick)

 

Works as designed
22Add co-investigators to grantsMac(tick)

 

Works as designed
23Check Person has co-investigator networkMac(tick)

 

Works as designed
24Check co-investigator network displayMac(tick)

 

Works as designed
25Load Sample DataMac(tick)

 

sample-data.n3 loaded from https://github.com/vivo-project/sample-data/blob/master/sample-data.n3
26Check Capability MapMac(tick)

 

Works as designed. Need more sample data with more concepts for more extensive tests.
27Check Map of ScienceMacUnable to completeTesting requires google maps key configured in runtime.properties.
28Check Temporal GraphMac(tick)

 

Works as designed
29Search for "Derrida"Mac(tick)

 

Works as designed
30Check index pageMac(tick)

 

Works as designed
31Create self editor login associated with profile

Mac


(tick)

 

Works as designed. Updated documentation to describe how this is done. See Creating and Managing User Accounts#AssociatingUserAccountswithProfilePages
32Log in as self editor. Verify can edit self, cannot edit others.Mac(tick)

 

Works as designed.
33Add and confirm an ORCiDMacUnable to completeORCiD API configuration requires clientId and clientPassword and public VIVO. See Activating the ORCID integration
34Create editor and assign proxy editing

Mac

Windows

(tick)

(tick)

Works as designed.

Created user account with editor role and assigned proxy editing.  Also switched to self-editor role.

35Log in as proxy editor. Verify can edit proxied profile, cannot edit others.

Mac


Windows

(tick)


(tick) (question)

 

works as designed.


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. (Hence the question mark - I'm unsure whether this is desired behavior or not)

36Check TPF endpoint

Mac

Windows

(tick)

(tick)

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)

37Run a SPARQL query

Mac



Windows

(error) Test failed



(tick)


Chrome: Screen appeared to be showing all prefixes, then flashed and was replaced by screen showing just five prefixes. Query ran fine, but prefixes should appear in the default SPARQL query window. See SPARQL Prefixes missing 2018-06-03 14.50.25.png May be user error – perhaps caching this screen? I removed all cache and retried, but behavior remained.

Note from Benjamin Gross: Re: Above... I'm not sure what the mechanism for caching is, but I think that's what is happening. I got all the normal prefixes the first time as expected.

Safari: works as designed

On Windows, tested in Firefox with same query as in screenshot above: "PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#> SELECT ?s ?o WHERE {?s rdfs:subClassOf ?o .}" and items were returned. In Chrome, ran default query that shows up when you first to the Sparql query page (if you haven't been there in that browser) and that also ran successfully.

API Tests (reference: VIVO APIs)


TestPlatformTested bySuccess?Notes
1

Linked Open Data

Linux(tick)

# From Site Admin: Create a new `Faculty Member` (Add individual)
** Record the new URI: http://localhost:8080/vivo/individual/n1323
# Verify `individual` endpoint:

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"

ListRDF
(tick)curl http://localhost:8080/vivo/listrdf -d 'vclass=http://vivoweb.org/ontology/core#Continent'
3

Triple Pattern Fragments

http://localhost:8080/vivo/tpf/core

http://localhost:8080/vivo/tpf

curl http://localhost:8080/vivo/tpf/core


(tick)

# Verify browsing:
http://localhost:8080/vivo/tpf/core
http://localhost:8080/vivo/tpf

# Verify direct access:
curl http://localhost:8080/vivo/tpf/core?subject=http://localhost:8080/vivo/individual/n1323

4SPARQL Query API



5SPARQL Update API



6Search Indexing API



7Data Distribution API



8Direct2Experts API



Unload/Load Tests


TestPlatformTested bySuccess?Notes
1Load data using the HarvesterLinux | Mac | Windows


2Unload using jena2tools -e



3Load using jena3tools -i



4Load sample data to a named graph



5Remove sample data named graph



Upgrade Tests

  1. Install previous release
  2. Prepare installation per instructions above for previous release
  3. Start Tomcat - check that smoke test passes
  4. Stop Tomcat
  5. Export data with jena2tools

    java -jar jena2tools.jar -e -d /usr/local/vivo/home
  6. 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';
  7. Remove application data

    rm -rf ${VIVO_DIR}/tdbModels/*
    rm -rf ${VIVO_DIR}/solr/data/*
  8. Import data with jena3tools

    java -jar jena3tools.jar -i -d /usr/local/vivo/home
  9. Start Tomcat
  10. Verify application per `UI Tests` above

    TestPlatformTested bySuccess?Notes
    All UI TestsLinux | Mac | Windows


    All API TestsLinux | Mac | Windows


    All Unload/Load tests



    All performance tests



Vagrant Tests

  1. Clone VIVO Vagrant

    git clone https://github.com/vivo-community/vivo-vagrant.git
  2. Checkout release candidate 

    cd vivo-vagrant
    git checkout rel-1.10.0-RC-1
  3. Load local or sample data

  4. Verify application per `UI Tests` above
TestPlatformTested bySuccess?Notes
All UI TestsLinux | Mac | Windows


All API Tests



All Unload/Load Tests



All performance tests



Performance Tests

Performance tests should compare run times for a 1.9.3 vs a 1.10 on same hardware, same data.
Timing collection may be facilitated by enabling The Developer Panel.


TestPlatformTested bySuccess?Notes
1Compare firsttime starttime timeLinux | Mac | Windows


2Compare performance data load time



3Compare profile display time



4Compare SPARQL query time



5Compare Search Index rebuild time



6Compare Inferencer rebuild time



7Compare jenatools export time



8Compare jenatoools import time



9Compare Data Distribution API response time



  • No labels