Time: 11:00 am, Eastern Time (New York, GMT-05:00)
To join the online meeting:
Selenium Tests VIVO Acceptance Tests - Jim Blake
When Androids Dream (codename: androdies) - Huda Khan
March (18-29) sprint planning
Mailing list messages
Status of In-Review tickets
Low-hanging - need one more reviewer - Brian Loweis reviewing
Kitio Fofack ? Orcid and i18n
Draft notes in Google-Doc
Don will open a ticket regarding a proposed change to data properties for courses
AW: Relation of interesting Ontology work to the development call
MC: Seeking separation of concerns. Adding terms to VIVO 1.7 ontology is expected. VIVO 2.0 to remodel things.
RO: perhaps the architecture is naturally separating these concerns.
MC: Perhaps two years down the road.
VIVO Acceptance Tests -- JB
Acceptance tests -- used to accept the product. NOT unit tests.
Selenium -- drives the browser. Mimics a user. Runs on all major platforms. Firefox plug-in to create a test and run the test.
Previously -- 28 test suites for testing presentation, editing, search, indexing, permissions, and much more.
Run manually -- 3 hour process. Run on the release candidates. Not run for 1.10, not maintained. 28 suites, 242 tests, 18,423 steps.
Not portable. Fixed file paths. Difficult to write, difficult to maintain.
Goals for new tests
Multi-browser. Ruby is headless, runs in Selenium.
Easy to write and maintain tests
Will use Ruby and RSpec. Suites are now called tests.
Simple infrastructure: TDB, no MySQL. Run in JettyRunner, no Tomcat. Might run without Solr.
Can write subroutines. Can wait for threads. Automated conversion. Now curating.
Tests become shared_examples in Ruby.
Four suites running. 24 to go (two weeks until Jim retires)
Jim demonstrated one of the suites
Run tests regularly. Continuous integration. Can make it happen.
https://github.com/j2blake/vivo-acceptance-tests dev branch. Can become a vivo-community repo.
Have a reasonable chance of becoming an on-going capability
AW: Needs to go to CI as soon as possible.
Test harness looks good for product evolution
242 externalized, clear text tests is crazy good. These are claims about VIVO can do. If there are missing claims we add more tests.
Next week -- Androdies -- a graphical view of the fly-in
Would be good to review before next week.
Sprint starts this coming Monday -- March 18.
Agenda item 4 -- ORCiD related.
VIVO confirms ORCiDs (might be broken)
Open VIVO uses ORCiD sign-on and pulls from VIVO
Jim has some code in development that would support push to ORCiD