Author: Scott Bauer,
Email: craig.stancl2@nih.gov, scott.bauer@nih.gov, cory.endle@nih.gov
Team: LexEVS
Contract: 16X237
Client: NCI CBIIT
National Institutes of Heath
US Department of Health and Human Services
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
Proposal
Main Goal
- We recommend some pair programming/work items that will result in a test plan and test suite for the release items.
- This is our main goal for the face to face.
Supplementary
- LexEVS API (remote/distributed)
- We can also 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.
- We will 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
We can discuss the best practical approach for a fully automated implementation of that test plan.
We'll 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 adopt 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.
Deliverables
Release Test Plan
Release Test Suite
LexEVS Test Plan
LexEVS Distributed Test Suite
CTS2 Test Plan
CTS2 Test Suite
Agenda/Work Schedule
Monday, June 24th | |||
---|---|---|---|
Time (EST) | Location | Topics | Resources |
8:00 AM - 10:00 AM | TBA | Release Items Test Plan
CTS2 Test Plan
| |
10:00 AM - 10:20 AM | Break | ||
10:20 AM - 12:00 PM | TBA | Pair Programing Exercise
CTS2 Test Plan
| |
Noon - 1:00 PM | Lunch | ||
1:00 PM - 3:00 PM | TBA | Pair Programing Exercise
CTS2 Test Plan
| |
3:00 PM to 3:20 PM | Break | ||
3:20 PM - 4:30 PM | TBA | Pair Programing Exercise
CTS2 Test Plan
| |
4:30 PM - 5 PM | TBA | Progress Review
| |
Tuesday, June 25th | |||
Time | Location | Topics | Resources |
8:00 AM - 10:30 AM | TBA | Pair Programing Exercise
| |
10:30 AM -11AM | Break | ||
11:00 AM - 12:00 PM | TBA | Pair Programing Exercise
| |
Noon - 1:00 PM | Lunch | ||
1:00 PM - 3:00 PM | TBA | LexEVS API Test Plan
| |
3:00 PM - 3:20 PM | Break | ||
3:20 PM - 4:30 PM | TBA | LexEVS API Test Plan
| |
4:30 PM - 5:00 PM | TBA | Progress Review
| |
Wednesday, June 26th | |||
Time | Location | Topics | Resources |
9:00 AM - 10:00 AM | TBA | LexEVS API Test Plan Implementation
| |
10:00 AM - 10:20 AM | Break | ||
10:20 AM - 12:00 PM | TBA | LexEVS API Test Plan Implementation
| |
Noon - 1:00 PM | Lunch | ||
1:00 PM - 3:00 PM | TBA | LexEVS API Test Plan Implementation
CTS2 Test Plan Implementation
| |
3:00 PM - 3:20 PM | Break | ||
3:20 PM - 4:30 PM | TBA | LexEVS API Test Plan Implementation
| |
4:30 PM - 5:00 PM | TBA | Progress Review
| |
Thursday, June 27th | |||
Time | Location | Topics | Resources |
8:00 AM to 4:30 PM with breaks as needed | TBA | LexEVS API Test Plan Implementation
| |
4:30 PM - 5:00 PM | TBA | Progress Review
| |
Friday, June 28th | |||
Time | Location | Topics | Resources |
8:00 AM to 4:30 PM with breaks as needed | Test Plan Execution and DebuggingExecution of automated testing with debugging and adjustment of any parameters, scenarios. | ||
4:00 PM - 5:00 PM | Wrap up, Review
| ||