Document and Implement Stress Testing into Coko QA
Context
Once #1456 is implemented, regular stress testing should be conducted as part of Coko QA to ensure performance, data model, XML writing, files management, processing high level acceptance criteria are continually met against real NCBI load and content types as development is ongoing.
Proposal
Coko will document and implement a stress testing QA process acceptable to NCBI to ensure performance, data model, XML writing, fles management, and processing high level user stories are continuously met against real NCBI data load and types. This may include unit and other regular automated QA tests run against this data, such as large file types, combinations of large files in different component types, and XML complexity use cases in chapter-processed books. The process will include how any issues encountered during this process will be reported and addressed.
Testing process
TBD
Design
Acceptance criteria
- A documented process for how all stress test and processing issues including crashes using the NCBI data in Coko QA environment will be regularly monitored, troubleshoot, and timely addressed to meet MVP BCMS user story specifications
- Logging of any bug issues once this QA process is implemented with agreement they will be addressed for MVP deployment, unless NCBI agrees they can be postponed
Definition of ready
-
BCMS User Story / Context has been well defined -
The priority of the user story is specified and agreed -
Digital assets added (design, database scheme, mockups etc if relevant) -
Coko Technical Proposal approved by NCBI -
Testable Acceptance Criteria approved by NCBI -
Estimate of effort to complete (time or points) -
The issue has been broken down into development tasks (if necessary) -
Requirements Clarified -
The product owner and development team agree that the user story is ready for development -
NCBI adds “Dev_Ready”
Definition of done
-
All coding tasks are finished and implemented -
QA approved -
Deployed and tested on “ncbidev” (by Coko team) -
Deployed and tested on “ncbi” (by NCBI team) -
Acceptance Criteria Met
Implementation
Alternative approaches (if applicable)
Scheduling
-
Milestone is linked -
Iteration is linked -
Dependencies: ("None" or list issue numbers if relevant) -
Development estimate is added to issue time tracking