Process
For Elsie F, 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 QA Lead also:
- 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
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 F branch build. Manual acceptance tests executed by team, with division of feature areas as follows:
Manual test responsibilities by component:
TESTER |
COMPONENTS |
Status |
|---|---|---|
Deepak |
LSIM, GLIM, Clients, Loan Account, Holidays |
|
Jeff |
Localization, Financial Calc and Loans, Reports, Admin Docs, Surveys/PPI |
|
Kojo |
Centers, Groups, Clients, Savings |
|
Lukasz |
Chart of Accounts, ImportExport, |
|
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 |
|---|---|---|---|---|---|---|---|
Early Repayment of Fees (PAWDEP) |
|
Lukasz |
|
|
|
|
|
Declining Balance – Interest Recalculation (PAWDEP) |
|
Deepak |
|
|
|
|
|
Variable Loan Installments (enda) |
|
Deepak |
|
|
|
|
|
Cash Flow Validation |
|
Deepak |
|
|
|
|
|
Permission to adjust last day’s backdated transactions (enda) |
|
Deepak |
|
|
|
|
|
conversion to service facades |
|
All |
|
|
|
|
|
MPESA disbursals and loan fees |
|
Lukasz |
|
|
|
|
|
improved Tally accounting integration |
|
Jeff |
|
|
|
|
|
GENERAL TASKS>> |
---------------------- |
--------- |
------------- |
------------- |
---------------- |
---------------------- |
|
|
Performance tests (in parallel with functional testing) |
Sungard |
continuously |
|
|
|
|
|
|
|
|
|
|
|
|
|
Upgrade tests |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Elsie F features functional testing complete |
|
n/a |
18-Feb-2011 |
|
|
|
|
Regression testing |
All |
14-Feb-2011 |
28-Feb-2011 |
|
|
|
|
Bug Verification Complete |
All |
n/a |
28-Feb-2011 |
|
|
|
|
|
|
|
|
|
|
|
|
Test Release Candidate |
|
28-Feb-2011 |
3-Mar-2011 |
|
|
|
|
Release |
|
n/a |
see F Release page |
|
|
|
Process
For Elsie F, 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 QA Lead also:
- 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
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 F branch build. Manual acceptance tests executed by team, with division of feature areas as follows:
Manual test responsibilities by component:
TESTER |
COMPONENTS |
|
|---|---|---|
Deepak |
LSIM, GLIM, Clients, Loan Account, Holidays |
|
Jeff |
Localization, Financial Calc and Loans, Reports, Admin Docs, Surveys/PPI |
|
Kojo |
Centers, Groups, Clients, Savings |
|
Lukasz |
Chart of Accounts, ImportExport, |
|
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 |
|---|
= no serious bugs
= issues to be fixed for this release
= blocked by serious bugs,
= no status yet
Draft || Comment
||tusEarly Repayment of Fees (PAWDEP)
Lukasz
Declining Balance – Interest Recalculation (PAWDEP)
Deepak
Variable Loan Installments (enda)
Deepak
Cash Flow Validation
Deepak
Permission to adjust last day’s backdated transactions (enda)
Deepak
conversion to service facades
All
MPESA disbursals and loan fees
Lukasz
improved Tally accounting integration
Jeff
GENERAL TASKS>>
----------------------
---------
-------------
-------------
----------------
----------------------
Performance tests (in parallel with functional testing)
Sungard
continuously
Upgrade tests
Elsie F features functional testing complete
n/a
18-Feb-2011
Regression testing
All
14-Feb-2011
28-Feb-2011
Bug Verification Complete
All
n/a
28-Feb-2011
Test Release Candidate
28-Feb-2011
3-Mar-2011
Release
n/a
see F Release page