project progress (Day-4)

   TEST APPROACH/ STRATEGY

QA will use the Alprus FRS for performing the functionality testing. Basic focus of testing will be on task functionality and usability testing. The following details the type of testing applied to this application.

·         Functionality testing

·         Compatibility testing

·         Usability testing

·         Regression testing

      BUILD PLAN AND TEST ENVIRONMENT CONFIGURATION

QA will be notify of the new build deployed on QA environment so that QA can regress the   fixed defect and perform testing on the new implemented or blocked areas in the application.

Alprus development team will update QA team along with release notes once the new build has been deployed on QA environment (TBD)

OS / Browsers  compatibility matrix.

OS                                             BROWSER	IE 6.0	IE 7.0	Firefox 2.0	Safari
Window vista	NA	Supported	Supported	NA
Window XP	Supported	Supported	Supported	NA
Macintosh OSX	NA	NA	Supported	Supported

      DEFECT TRACKING

Defect tracking will be done through a centralized bug tracking system.

QA will be reporting all the defects in bug base related to Alprus under one predefined project.

                  ENTRY AND EXIT CRITERIA

QA team will be reporting the defect during the Alprus and project team management will be deciding about the releasing the application to the market.

                         COMMUNICATION PLAN

Bug will be reported in an online bug tracking system. Once the testing starts , a clear escalation path will be defined to ensure timely resolution of the issues(TBD).

                     RISK

Smooth execution of the testing plans will be dependent on following:

a.       Development teams timely input.

b.      New build in time as per plan.

c.       Minimal downtime of Alprus application which Minimizes testing time.

d.      Availability of hardware resources to perform the testing.

e.       Timely fixing the bugs to perform the regression testing.

f.       Critical bugs, which may impact the complete testing of the application, be fixed right always.

g.      Bug base to  have minimal downtime.

    ASSUMPTIONS

QA team will not be executing any other test cases at the time of  Fixed Bugs Regression.QA team will only  be doing the regression of the bugs that have been fixed.

QA team will not be testing any areas/ features which are not defined in the project scope of the   testing.