Maya 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:

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

  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

Liquibase Rollback


Jeff / Kojo

 

25-Mar-2011

25-Mar-2011

(plus)

Jeff did testing on expand and undo expand.  see notes TODO for Kojo - contract & undo_contract.  Also should do expand/contract on ongoing upgrades.

Savings Creation FTL

 

Kojo

 

 

 

(plus)

 

 

Do exploratory testing

 

29-Mar-2011

30-Mar-2011

 

(plus)

 

 

Document Test Plan and Cases

 

30-Mar-2011

31-Mar-2011

 

(plus)

 

 

Develop automated acceptance tests

 

1-Apr-2011

5-Apr-2011

 

(plus)

Evaluate existing tests and fill in gaps. Existing test coverage is adequate.

PPI migration for GK

Document test cases and test migration

Kojo

30-Mar-2011

1-Apr-2011

 

(plus)

completed and sent to GK on 30-Mar-2011

Customize Text

 

Lukasz

 

 

 

 

 

 

Document Test Plan and Cases

 

24-Mar-2011

28-Mar-2011

 

(tick)

Customize Text Test Plan.odt

 

Do exploratory testing

 

29-Mar-2011

31-Mar-2011

 

(plus)

 

 

Develop automated acceptance tests

 

29-Mar-2011

1-Apr-2011

 

(tick)

 

Translations

Verify localization bug fixes

Lukasz

 

Feature Complete

 


 

Loan Creation FTL


Lukasz

 

 

 


 

 

Document Test Plan and Cases

 

15-Apr-2011

19-Apr-2011

 

(tick)

Loan Creation FTL Test Plan.odt

 

Do exploratory testing

 

20-Apr-2011

23-May-2011

 

(tick)

1.5 weeks

 

Develop automated acceptance tests

 

22-Apr-2011

23-May-2011

 

(tick)

1.5 weeks

Clients with different meeting frequencies

Document tests and do testing

Lukasz

24-May-2011

25-May-2011

 

 

As part of Loan Creation, test this feature

Redo Loan FTL

 

Kojo

 

 

 

 

 

 

Document Test Plan and Cases

 

18-May-2011

20-May-2011

 

(tick)

subset of Loan Creation, Test plan - https://docs.google.com/document/d/12_nTkNiCdrsl-V2DTEVoiR8Rv9jNeapC-wVqUFoUUQ0/edit?hl=en_US&authkey=CPP6z9kK#

 

Do exploratory testing

 

23-May-2011

25-May-2011

 

(tick)

 

 

Develop automated acceptance tests

 

25-May-2011

27-May-2011

 

(tick)

No new automated 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



 

 

Browser Testing

All

 

 

 

 

 

 

Bug Verification Complete

All

after Code Freeze

before Release

 


 

 

 

 

 

 

 

 

 

 

Test Release Candidate

 



 

 

 

 

Release

 



 

 

Â