Testing Plans - Leila E
For each feature area of Leila E, a QA engineer will build test cases in the mifosforge "test case" project. These acceptance tests validate requirements and create the foundation of tests that will be executed in an automated build process for subsequent builds.
Process and Responsibilities
Tests are built using following process:
- Stories for features include acceptance criteria developed by PM and QA lead.
- Depending on size of feature, test plan may be written to cover test data requirements, performance testing, etc. Part of test planning will be to write test cases for feature on mifosforge.
- automated acceptance tests can be written prior or following feature implementation. Automated tests are flagged in mifosforge test cases.
- acceptance tests are executed. QA engineer asks for help whenever blocked, unsure of feature design, etc.!
- exploratory testing of feature during acceptance testing of feature, report bugs, enhancements.
- verify bug fixes, update or add to test cases as by bug fixes.
- update schedule and status page with testing results.
The QA Oversight engineer:
- reviews acceptance criteria,
- reviews test cases,
- answers testing questions,
- performs some exploratory testing of features.
- evaluates if testing is complete, and confers with QA engineer if feature is ready to ship
Feature Area |
Test Plan & Cases |
Developers |
QA |
QA Oversight |
Comment |
---|---|---|---|---|---|
Udai |
Jeff |
Kay |
feature complete / manual testing complete |
||
 |
TW |
Deepak |
Jeff, Tejus |
feature complete |
|
Sol |
Lukasz |
Jeff |
Quartz batch jobs test progress |
||
Van/Adam M/Sol |
Jeff |
Kay |
|||
TW/Sol |
Tejus/Wojciech |
Jeff |
|||
TW/Sol |
Wojciech/Jeff |
Jeff |
|||
Sol |
Lukasz |
Jeff |
|||
Keith W/Udai |
Kojo |
Jeff, Keith |
 |
||
Freemarker pages |
Sol |
Lukasz |
Jeff/Kay |
||
Regression testing, bug fix verifications |
 |
all |
all |
Jeff |
 |