Release G Test Plan and Schedule

Process

For Release G, testing following this process:

1. Stories for features include acceptance criteria.
2. 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.
3. automated acceptance tests can be written prior or following feature implementation. Automated tests are flagged in mifosforge test cases.
4. acceptance tests are executed. QA engineer asks for help whenever blocked, unsure of feature design, etc.!
5. exploratory testing of feature during acceptance testing of feature, report bugs, enhancements.
6. verify bug fixes, update or add to test cases as by bug fixes.
7. update schedule and status page with testing results.

The Project Lead (Kay) also:

• answers testing/feature questions,
• performs some exploratory/showcase testing of features.
• evaluates if testing tasks are complete, and confers with QA engineers if feature is ready to ship

Jira/Standup Process

• Send standup reports every day
• M/W/F - look at issues in ready for testing, and assign to yourself if it's not assigned to anyone

Manual functional testing

Functional regression testing consists of a combination of automated and manual test cases logged on mifosforge. Automated regression run continuously on each build. Manual acceptance tests executed by team, with division of feature areas as follows:

Manual test responsibilities by component:

Additional Manual release tasks

In addition to functional test cases, with Release candidate we must execute release test checklist

Testing tasks and status