Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Current »

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

(tick)

Jeff

Localization, Financial Calc and Loans, Reports, Admin Docs, Surveys/PPI

(tick)

Kojo

Centers, Groups, Clients, Savings

(tick)

Lukasz

Chart of Accounts, ImportExport,

(tick)

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

  1. (plus) =  no serious bugs
  2. (warning)  = issues to be fixed for this release
  3. (error)  = blocked by serious bugs,
  4. (question) = no status yet
    Draft

Comment

Early Repayment of Fees (PAWDEP)


Lukasz

 

 

 

(plus)    

 

Declining Balance – Interest Recalculation (PAWDEP)


Deepak

 

 

 

(plus)

 

Variable Loan Installments (enda)


Deepak

 

 

 

(plus)

 

Cash Flow Validation

 

Deepak

 

 

 

(plus)

 

Permission to adjust last day’s backdated transactions (enda)


Deepak

 

 

 

(plus)


conversion to service facades


All

 

 

 

(plus)

 

MPESA disbursals and loan fees

 

Lukasz

 

 

 

(plus)       

 

improved Tally accounting integration


Jeff

 

 

 

(plus)

 

GENERAL TASKS>>

----------------------

---------

-------------

-------------

----------------

----------------------

 

 

Performance tests (in parallel with functional testing)

Sungard

continuously

 


 

 

 

 

 

 

 

 

 

 

 

Upgrade tests

 



 

(plus)

 

 

 

 

 

 

 

 

 

 

Elsie F features functional testing complete

 

n/a

18-Feb-2011

 

(plus)

 

 

Regression testing

All

14-Feb-2011

28-Feb-2011

3-Mar-2011

(plus)

 

 

Bug Verification Complete

All

n/a

28-Feb-2011

7-Mar-2011

(plus)

 

 

 

 

 

 

 

 

 

 

Test Release Candidate

 

28-Feb-2011

3-Mar-2011

 

Jeff going to pair with Kojo/Lukasz on Release Candidate testing

 

 

Release

 

n/a

see F Release page on internal wiki

 

 

 

  • No labels