2019.6 LexEVS 16x237 QA Face-To-Face

Meeting Details

Attendees

*remote attendee

Release Checklist

• Review and acceptance of live terminology configured test updates and status report in the lexevs-remote project (Swathi, Scott, and others as needed)
• Tag and post the release candidate to the usual sites for download and/or deployment (Cory)
• A refresh and redeployment of the LexEVS API on both dev and qa based on the tag for the latest LexEVSAPI tag (Swathi)
• A refresh of the URI Resolver DB on dev and qa for 1.1.1.FINAL tag (DB/Systems team)
• A refresh of the URI Resolver API (war file) on dev and qa for 1.1.1.FINAL tag (Swathi)
• A refresh and redeployment of the CTS2 REST API on both dev and qa based on the tag for the latest CTS2 tag (Swathi)
  • Update URI Resolver URL in the CTS2 service test properties file prior to running build/testing of CTS2 service for each tier (Cory)
• A refresh of the loading environment on Dev or where ever the test loads for qa and dev take place (Tracy)
• A refresh of the URI Resolver DB on DATA QA for 1.1.1.FINAL tag (Tracy or Systems team)
• A reload of NPO, NCIt, and a load of the value set definition for neoplasm to a resolved value set coding scheme (Tracy has taken these tasks on)
• An initial run of the latest test set for the release tests as well as the legacy regression tests for the live terminologies (Swathi)
• An initial run of the latest CTS2 Service tests (Swathi)
• A follow up reconfiguration and re-evaluation of the test sets iteratively until all tests are passing.  (Swathi and Scott or Cory as needed)
• App scan on QA

Goals

Primary

• Create a test plan from 6.5.2/6.5.3 release items
• Execute a test suite in a pair programming/work environment

Supplementary

• LexEVS API (remote/distributed)
  • Create a test plan that describes full API test coverage method by method and detailing input and expected results (with some exceptions) to be completed in the Dev QA distributed environment. 
  • Leverage some legacy test suites in the lexevs-remote project to implement this test plan
• CTS2 REST API
  • Cory will create a test plan for the CTS2 REST plan that details full coverage of the current CTS2 REST Service. 
  • Cory will leverage some of the Frisbee test suite examples in our full service test to help provide coverage for the CTS2 REST Service
  • This will also target the QA Test environment
• QA Team Training in LexEVS test methods
  • Engage QA in test plan and integration test writing with the goal of allowing that person to configure and maintain the current test plan and create new tests as needed.
  • Decide the best practical approach for a fully automated implementation of that test plan. 
• Evaluate the progress and deliverables at the end of the work week and hand off to the QA team.

Meeting Notes

References

LexEVS 6.0 Test Plan Document

LexEVS 6.5.2 Release Notes

6.5.3 release items

Remote RC1 war file

Items for Consideration

We will need a reload of at least OWL, OBO, Resolved Value Set Coding Schemes, and HL7 mif formatted terminologies and mapping terminologies on QA.

We recommend adopting the loader tests implemented by Tracy Safran as the Test Plan for Loaders. 

We propose a CI server automation of the tests to run nightly against live terminology loads.

We will add as a follow up task, documentation of LexEVS testing

Deliverables

Release Test Plan

LexEVS6.5.3.Release.test plan_V1.0.xlsx

Release Test Suite

https://github.com/lexevs/lexevs-remote/tree/bugfix/LEXEVSREM-388

Release Test Suite Entry Point

org.LexGrid.LexBIG.testUtil.AllLexEVS652Tests

LexEVS Test Plan

LexEVSAPI.xlsx

LexEVS Distributed Test Suite

https://github.com/lexevs/lexevs-remote/tree/bugfix/LEXEVSREM-390

CTS2 Test Plan

CTS2TestPlan.xlsx

CTS2 Test Suite

https://github.com/lexevs/lexevs-service-rest-tests.git

Agenda/Work Schedule

---