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:
TESTER |
COMPONENTS |
Status |
|---|---|---|
Kojo |
Savings FTL, Redo Loan FTL stories, PPI migration, database rollback (new liquibase upgrade/rollback) |
|
Lukasz |
Loan creation FTL stories, Customize Text, Translations, Misc bug fixes |
|
Additional Manual release tasks
In addition to functional test cases, with Release candidate we must execute release test checklist
Testing tasks and status
Feature |
Task |
Resource |
Planned start date |
Planned completion date |
Actual completion date |
Overall Status
|
Comment |
|---|---|---|---|---|---|---|---|
Liquibase Rollback |
|
Jeff / Kojo |
|
|
|
|
see |
Savings Creation FTL |
|
Kojo |
|
|
|
|
|
|
Document Test Plan and Cases |
|
|
22-Mar-2011 |
|
|
|
|
Do exploratory testing |
|
23-Mar-2011 |
28-Mar-2011 |
|
|
|
|
Develop automated acceptance tests |
|
23-Mar-2011 |
28-Mar-2011 |
|
|
Evaluate existing tests and fill in gaps |
PPI migration for GK |
Document test cases and test migration |
Kojo |
28-Mar-2011 |
30-Mar-2011 |
|
|
need to coordinate w/ Tejus - Udai and Kojo could pair |
Customize Text |
|
Lukasz |
|
|
|
|
|
|
Document Test Plan and Cases |
|
21-Mar-2011 |
23-Mar-2011 |
|
|
|
|
Do exploratory testing |
|
23-Mar-2011 |
25-Mar-2011 |
|
|
|
|
Develop automated acceptance tests |
|
23-Mar-2011 |
28-Mar-2011 |
|
|
|
Translations |
Verify localization bug fixes |
Lukasz |
|
Feature Complete |
|
|
|
Loan Creation FTL |
|
Lukasz |
|
|
|
|
|
|
Document Test Plan and Cases |
|
|
|
|
|
4 days |
|
Do exploratory testing |
|
|
|
|
|
1.5 weeks |
|
Develop automated acceptance tests |
|
|
|
|
|
1.5 weeks |
Redo Loan FTL |
|
Kojo |
|
|
|
|
|
|
Document Test Plan and Cases |
|
|
|
|
|
subset of Loan Creation |
|
Do exploratory testing |
|
|
|
|
|
|
|
Develop automated acceptance tests |
|
|
|
|
|
|
GENERAL TASKS>> |
---------------------- |
--------- |
------------- |
------------- |
---------------- |
---------------------- |
|
|
Upgrade tests from previous release to G |
Kojo |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Release G Features functional testing complete |
|
|
2 weeks after FC |
|
|
|
|
Manual Regression tests |
All |
after Code Freeze |
before Release |
|
|
|
|
Bug Verification Complete |
All |
after Code Freeze |
before Release |
|
|
|
|
|
|
|
|
|
|
|
|
Test Release Candidate |
|
|
|
|
|
|
|
Release |
|
|
|
|
|
|
= no serious bugs
= issues to be fixed for this release
= blocked by serious bugs,
= no status yet