 |
Page History
...
| Name | Role | Attend? (Y/N) |
|---|---|---|
Bauer, Scott | Mayo | y |
Endle, Cory | Mayo | y* |
Konareddy, Swathi | NIH/NCI | y |
| Chen, Yang | NIH/NCI | y |
| Tran, Tin | NIH/NCI | y |
*remote attendee
...
Goals
Main Goal
Primary
- Create a test plan from 6.5.2/6.5.3 release items
- Execute a test suite in a pair programming/work environment
- We recommend some pair programming/work items that will result in a test plan and test suite for the release items.
- This would be our primary purpose for the face to face.
Supplementary
- LexEVS API (remote/distributed)
- We can also create 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 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 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
...
