Page History
...
Panel | ||||
---|---|---|---|---|
| ||||
|
The purpose of this document is to document the technical face to face meeting details between NCI and Mayo.
Meeting Details
NCI Shady Grove Campus Rooms: | Conference Details |
Attendees
Name | Role | Attend? (Y/N) |
---|---|---|
Bauer, Scott | Mayo | y |
Endle, Cory | Mayo | y* |
Konareddy, Swathi | NIH/NCI | y |
*remote attendee
Meeting Notes
References
Chen, Yang | NIH/NCI | y |
Tran, Tin | NIH/NCI | y |
*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
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
LexEVS Distributed Test Suite
https://github.com/lexevs/lexevs-remote/tree/bugfix/LEXEVSREM-390
CTS2 Test Plan
CTS2 Test Suite
https://github.com/lexevs/lexevs-service-rest-tests.git
Agenda/Work Schedule
...
Monday, June 24th | |||
---|---|---|---|
Time (EST) | Location | Topics | Resources |
8:00 AM - 10:00 AM |
7W032 | Release Items Test Plan
CTS2 Test Plan
| ||
10:00 AM - 10:20 AM | Break | ||
10:20 AM - 12:00 PM |
7W032 | Pair Programing Exercise
CTS2 Test Plan
| ||
Noon - 1:00 PM | Lunch | ||
1:00 PM - 3:00 PM |
7W032 | Pair Programing Exercise
|
CTS2 Test Plan
| |||
3:00 PM to 3:20 PM | 7W032 | Break | |
3:20 PM - |
4:30 PM |
7W032 | Pair Programing Exercise
CTS2 Test Plan
| ||
4:30 PM - 5 PM | 7W032 | Progress Review
| |
Tuesday, June 25th | |||
---|---|---|---|
Time | Location | Topics | Resources |
8:00 AM - |
10: |
30 AM |
Value Set management and workflow
1E034 | Pair Programing Exercise
| |
10:30 AM -11AM | Break |
11:00 AM - 12:00 PM |
Value Set and Mapping Data with Hierarchical structure Discussion
- Determine requirements and propose options to hierarchical structure and mapping.
- Discuss how VS could retain their multiple hierarchical structure that it came from.
- Discuss what changes would be needed to CTS2 for this.
OWL Restrictions in LexGrid Model
- Discuss approach and propose additional features.
- Determine if there are LexEVS model changes needed.
- Loader considerations.
- Additional problems and solutions
Overflow/Additional Topics
1E034 | Pair Programing Exercise
| ||
Noon - 1:00 PM | Lunch | ||
1:00 PM - 3:00 PM | 6W032 | Pair Programming Exercise
| |
3:00 PM - 3:20 PM | Break | ||
3:20 PM - 4:30 PM | 6W032 |
NCI Systems Discussions
- Nexus Deployment Discussion
- Current status of LexEVS artifacts on NCI Nexus server
- Discuss current technical challenges.
- CI and Docker Status/Roadmap
- Discuss the current status of the Docker scripts used to build/test LexEVS components.
- Discuss NCI's current status and future plans to use Docker.
- Discuss security challenges associated with NCI's environment and Docker.
- Discuss a separate DEV environment for CI server deployment
- Tech Stack Upgrades
- Discuss DB upgrade:
- MySQL 5.6 vs. MariaDB (10.1 Supported 2017.01)
- Discuss CentOS 7 upgrade
- Discuss DB upgrade:
- Tier Deployment testing responsibilities
- Mayo development team responsibilities
- NCI development team responsibilities
FHIR and terminology services (CTS2)
- Harold to provide update on CTS2 and FHIR.
Pair Programming Exercise
| |||
4:30 PM - 5:00 PM | 6W032 | Progress Review
| |
Wednesday, June 26th | |||
---|---|---|---|
Time | Location | Topics | Resources |
9:00 AM - 10:00 AM | 2W030 | LexEVS API Test Plan Implementation
| |
10:00 AM - 10:20 AM | Break | ||
10:20 AM - 12:00 PM | 10 - 11am Room 1W032 11am - 12pm Room 2W030 | LexEVS API Test Plan Implementation
| |
Noon - 1:00 PM | Lunch | ||
1:00 PM - 3:00 PM | 2W030 | LexEVS API Test Plan Implementation
CTS2 Test Plan Implementation
| |
3:00 PM - 3:20 PM | Break | ||
3:20 PM - 4:30 PM | 3W030 | LexEVS API Test Plan Implementation
| |
4:30 PM - 5:00 PM | 3W030 | Progress Review
| |
Thursday, June 27th |
Time | Location | Topics | Resources |
---|
8:00 AM |
LexEVS Admin Tooling
Discuss current and future requirements.
- GUI
- Consider a web based tool. A simple way to look at the data.
- Command Line loader requirements
- Other considerations
to 4:30 PM with breaks as needed | 8 – 10am Room 1E030 10 – 11am Could not get conference room 11am – 5pm Room 1E030 | LexEVS API Test Plan Implementation
| |
4:30 PM - 5:00 PM | 1E030 | Progress Review
| |
Friday, June 28th | |||
---|---|---|---|
Time | Location | Topics | Resources |
8:00 AM to 4:30 PM with breaks as needed | 7E030 | Test Plan Execution and DebuggingExecution of automated testing with debugging and adjustment of any parameters, scenarios. | |
4:00 PM - 5:00 PM | 7E030 | Wrap up, Review
|
Prioritization and Debrief
- Discuss OWL2, RRF, LexEVS, CTS2, Browser, and all previous topics
- Discuss future architecture
- Determine next steps/road map and priorities
...