Master Test Plan - IPMA by yaoyufang

VIEWS: 3 PAGES: 11

									TESTING, TESTING 1-2-3
              Master Test Plan




                              Date
                  October 14, 2004

                      Prepared For
              Testing, Testing 1-2-3

                      Prepared By
                     Jan McCollum
Manager, Quality Assurance and Test
          (425) 885-2780 ext. 2418
     JMcCollum@SolutionsIQ.com

            www.SolutionsIQ.com
                                               TABLE OF CONTENTS
Introduction ................................................................................................................................... 3
  Document Purpose ...................................................................................................................... 3
  Project Overview ........................................................................................................................ 3
  Application Functionalities ......................................................................................................... 3
  Testing Areas .............................................................................................................................. 3
  Special Areas (i.E. Security Testing) .......................................................................................... 3
Responsibilities .............................................................................................................................. 4
  Project Contacts .......................................................................................................................... 4
  quality assurance engineers......................................................................................................... 4
Documentation .............................................................................................................................. 4
  References ................................................................................................................................... 4
  Project Specifications and Documentation ................................................................................. 4
Test Environment.......................................................................................................................... 5
  Hardware ..................................................................................................................................... 5
  Server Software ........................................................................................................................... 5
  Database ...................................................................................................................................... 5
  Client Operating Systems and Software ..................................................................................... 5
  Browsers ..................................................................................................................................... 5
Test Approach ............................................................................................................................... 5
  Test Analysis Phase .................................................................................................................... 5
  Test Planning Phase .................................................................................................................... 5
  System Functional Testing Phase ............................................................................................... 6
     Test Data Requirements ....................................................................................................... 6
     Test Data Generation ............................................................................................................ 6
  Regression Testing Phase ........................................................................................................... 6
  Functional Tests .......................................................................................................................... 7
  Out of Scope ............................................................................................................................... 7
Release Phase Guidelines ............................................................................................................. 7
  Bug Severity Definitions............................................................................................................. 7
  Test Case Pass/Fail Criteria ........................................................................................................ 7
  Build Acceptance Criteria ........................................................................................................... 8
  Suspension Criteria for failed BAT ............................................................................................ 8
     Resumption Criteria for BAT ................................................................................................. 8
     Criteria for Release to User Acceptance Testing .................................................................... 8
  Release Notes .............................................................................................................................. 8
QA Team Milestones..................................................................................................................... 9
Deliverables ................................................................................................................................. 10
Risks ............................................................................................................................................. 10
QA Test Plan Change Log and Sign Off ................................................................................... 11
  Revision history ........................................................................................................................ 11
  Sign Off ..................................................................................................................................... 11




     d9e3938c-b4f1-47bf-879b-c46119214424.doc                             Page 2 of 11                                             2/15/2013
                                      INTRODUCTION
DOCUMENT PURPOSE

This master test plan outlines the strategy and methodology used for conducting testing for the
project. It is intended to describe the activities necessary to verify the functionality and reliability
of the application before it is released to UAT.

The plan will define the following:

       Describe functionality of the project and the test environment
       Describe materials (deliverables) due upon the completion of testing
       Identify the functional tests to be performed
       Specify requirements and functions to be tested
       Provide schedules and milestones for test activities

PROJECT OVERVIEW
SolutionsIQ Professional Services has contacted the XYZ Group to complete the upgrade of the
XYZ application. The work involved consists of (list change request description here):


APPLICATION FUNCTIONALITIES
This is the system overview for all interfaces. Create a list.


TESTING AREAS
Main areas to be tested include architecture, design, assign, query, admin, and help. For the
purposes of the change requests (CR), the screens/pages that are in-scope only will be modified.
Existing screens/processes include the following:
    Create/modify building/location information
    Create/modify AD site link - XYZ

SPECIAL AREAS (I.E. SECURITY TESTING)
Security testing is integral to software quality. The purpose of security testing is to expose any
security vulnerabilities in the software product before release to production.




    d9e3938c-b4f1-47bf-879b-c46119214424.doc       Page 3 of 11                            2/15/2013
                                 RESPONSIBILITIES
PROJECT CONTACTS
       Position                  Name                               Email
Project Manager
Development Lead
Developer
QA Lead
QA Engineer

QUALITY ASSURANCE ENGINEERS
     Name                                   Responsibilities
                Test plant and test suite preparation and documentation review
                System functional testing and documentation reviews


                                 DOCUMENTATION
REFERENCES
Here include links and paths to all documentation associated with this project. For example…

SolutionsIQ VSS location:

      SolutionsIQ network - \\PLUTO\VSS - Test and development specifications, test plan
       and manual test cases
      Bug database
      SolutionsIQ network – http://server.solutionsiq.com

PROJECT SPECIFICATIONS AND DOCUMENTATION

Pertinent documents for the project:

          Document                                    VSS/CVS Location
Functional Specification         $/Projects/XYZ/Phase-2/Docs/CETE Phase 2 FuncSpecs.doc
Detailed Design                  $/Projects/XYZ/ Phase-
Specifications                   2/Docs/CETE_Phase2_Detailed_Design.doc
Master Test Plan                 $/Projects/XYZ/Phase-2/Test/CETE Phase 2 Master Test
                                 Plan.doc
Manual Test Suites               $/Projects/XYZ/XYZ Phase-2/Test/CETE Phase 2 Test
                                 Suites.doc
XYZ Phase 2 Builds               $/Projects/Microsoft/XYZ Phase-2/Build/




   d9e3938c-b4f1-47bf-879b-c46119214424.doc    Page 4 of 11                        2/15/2013
                               TEST ENVIRONMENT
The test environment for the XYZ phase 2 project will consist of these machine configurations:
Descriptions of machines, database server(s) and their intended use(s).


HARDWARE
Pentium IV, 512 MB memory

SERVER SOFTWARE
.Net Framework 1.1

DATABASE
MS SQL Enterprise Server 2000 with SP3.

CLIENT OPERATING SYSTEMS AND SOFTWARE
   Windows Server 2003, Standard Edition and Office 2003 Excel
   Windows XP Professional and Office 2003 Excel


BROWSERS
IE 6.0 SP1.

                                   TEST APPROACH
TEST ANALYSIS PHASE
The test analysis phase is to review proposals, technical and functional specifications, and other
available documentation, and to attend meetings and reviews to clearly define the overall scope
of the project.

TEST PLANNING PHASE
The planning phase includes the completion of all steps necessary to begin the actual testing
phases. This time is used to clearly define test tasks so test and development can accurately
schedule their respective tasks and responsibilities.

Tasks to be completed during test planning phase:
    Meet with development to discuss overall test strategy
    Collect any written materials developed for the product, such as requirements
       specifications
    Coordinate requirements for bug tracking methods and communication
    Define minimum hardware configurations to be supported and tested
    Develop master test plan, including test deliverables with milestones
    Develop test casts and scenarios as needed
    Peer-to-peer reviews of test cases
   d9e3938c-b4f1-47bf-879b-c46119214424.doc      Page 5 of 11                          2/15/2013
      Coordinate test team and assign test responsibilities

Test cases prepared during planning are live documents that are constantly updated during the
functional testing phase. This is true whenever a new scenario without a test suite is identified.

SYSTEM FUNCTIONAL TESTING PHASE
The system functional test phase is designed to evaluate and verify the feature functionality as
outlined in the system functional specification. Functional testing will include testing of input
limits and boundaries, data storage and retrieval, security permissions, page comparisons,
modification history and scheduling. New builds should be installed on a CLEAN server and
tested using the latest production database backup.

Tasks to be completed during system functional test phase:
    All input editing, validation and processing
    All outputs
    All decision points in the program

Test Data Requirements
The data for testing comes from the users implementing the test, computers, and software being
tested.

Test Data Generation
Test data from user and hardware/software provides the following:

      Nominal and expected input data values to test the effect of normal data
      Default and null data to test default processing
      Critical values to validate calculations
      Maximum and minimum values to test range processing
      Different data types to verify data type validation


REGRESSION TESTING PHASE
In order to verify build acceptance, some limited testing will be performed following new builds
and setup to verify that the release is ready for regression testing. This testing will include
general functionality testing to verify the build meets the build acceptance criteria.

Tasks to be completed during regression test phase are as follows:

      Verify build acceptance (release is ready for testing)
      Review/analyze list of fixes and resolutions to determine detailed test strategy and
       coverage of regression test phase




   d9e3938c-b4f1-47bf-879b-c46119214424.doc       Page 6 of 11                          2/15/2013
FUNCTIONAL TESTS
Detailed test suites are created for every feature that has to undergo testing. These test suites are
available in the VSS path mentioned above. An overall picture of the kind of manual tests has
been planned for XYZ application is given below:

      Ensure functionalities as documented in the functional specification are provided and
       working properly.
      All test cases, per the unit test plans, are executed and the system behaves in compliance
       to these test cases. There should be no test case failure scenarios.

OUT OF SCOPE
SolutionsIQ QA group will not perform the following testing:

      UAT testing
      Any load, stress, or performance testing
      Security testing
      Localization or globalization testing
      Cross domain testing
      Phase 1 UAT bugs (change requests)
      User guide verification
      Data inconsistency from upstream system
      Automated testing


                         RELEASE PHASE GUIDELINES

BUG SEVERITY DEFINITIONS
JIRA will be used to log and track all bugs. Bug reports are categorized as either a code defect or
suggestion, and given a severity code as defined below:

      Severity Blocker: Bug blocks development and/or testing work
      Severity Critical: Bug causes crashes, loss of data, or severe memory leak
      Severity Major: Bug causes major loss of function
      Severity Minor: Bug causes minor loss of function, or other problem where easy
       workaround is present
      Severity Trivial: Bug is cosmetic or a minor design issue (misspelled words or
       misaligned text)

TEST CASE PASS/FAIL CRITERIA
The feature will be tested using the criteria outlined below.

Pass criteria:
    All processes will execute with no unexpected errors.

   d9e3938c-b4f1-47bf-879b-c46119214424.doc        Page 7 of 11                          2/15/2013
      All processes will execute in an acceptable amount of time based on benchmarks
       documented by development and test.

BUILD ACCEPTANCE CRITERIA
Once code is dropped and the build is applied on a clean production backup environment, the test
team can execute planned tests. A build acceptance test (BAT) is run to ensure the new build
from development is ready for testing. The BAT will test the basic functionality of the system. If
an excessive number of items fail, the build is sent back to development and no testing will begin
until the BAT has passed. After passing, a build e-mail is produced by the test team stating the
general functional condition of the build as well as bugs/fixes addressed in the build.

SUSPENSION CRITERIA FOR FAILED BAT
The system test team may suspend partial or full-testing activities on a given build if any of the
following occur:

      A fault with a feature prevents further testing
      An application or build does not contain the specified change(s)
      A severe problem occurs that does not allow testing to continue, such as the application
       crashing during set up
      Development has not corrected the problem(s) that previously suspended testing
      A new version of the software is available to test

Resumption Criteria for BAT
The steps necessary to resume testing:

      Clean previous code from machines or restore clean drive image (ghost image as needed)
      Re-install the application
      The problem encountered resulting in suspension is corrected

Criteria for Release to User Acceptance Testing
Release criteria necessary to allow the code to migrate to user acceptance:

      There are no open bugs with a severity of critical, major or blocker
      It successfully passes the final regression testing
      There are no discrepancies between the master setup and the version used during the final
       regression testing
      Test cases scheduled for both integration and system test phases have passed. The project
       manager, lead developer and QA lead sign off the project
      Release notes will be complete, submitted to release management and approved

RELEASE NOTES
Release notes will be provided to the release management representative and the lead for project.
It may/may not include the following for each module/program turnover:

      Backup plan instructions
   d9e3938c-b4f1-47bf-879b-c46119214424.doc       Page 8 of 11                         2/15/2013
         Versions of software, libraries, hardware, database, etc. used.
         VSS/CVS source code version and location
         Build (make file) instructions
         Installation/setup instructions
         Account and security permission for database objects and COM+ objects
         Steps to setup SQL and NT jobs
         Dependencies (other executables, database, browser, etc.)
         Scheduled functionality for this iteration or release
         Change requests
         Open problems/problem bug reports
         Known limitations

                              QA TEAM MILESTONES
Milestones defined, schedule, phase and assigned test team member.



        Milestone               Description of Milestone          Team Member Responsible

                         Analysis of project scope and           Program Manager, Project
   Analysis and          responsibilities, review of technical   Manager, QA Lead
    Planning             specifications, and identification of
                         staffing needs
                         Complete preliminary drafts and final   Program Manager, Project
    Test Plan
                         version of test plan for input and      Manager, QA Lead
   Development
                         approval
Test Suite/Test Case     Design and develop Test Suites and      QA Lead, QA Engineers
   Development           Test Cases
                         “Black box” level of testing that is    QA Lead, QA Engineers
System Functional        based on overall requirements
     Testing             specifications; covers all combined
                         parts of the system
                         Release from test to customer for       QA Lead
  Release to UAT
                         UAT.




    d9e3938c-b4f1-47bf-879b-c46119214424.doc     Page 9 of 11                     2/15/2013
                                    DELIVERABLES
Below are common and recommended test deliverables for a project, in which phase they should
occur and the responsible parties for each. Deliverables are included in, but not restricted to,
established project milestones.


                                                                                 QA Team
    Phase                                Deliverable                              Member
                                                                                Responsible
                 Create Test Plan. After functional specifications from        QA Lead, QA
 Test Plan       development have been approved the Test Plan for the          Engineers
Development      project will be created.
                 Create Test Cases. Once the Test Plan has been created
                 and reviewed by the test and development teams, test          QA Lead, QA
    Test
                 cases are created. Test Cases are stored in VSS/CVS.          Engineers
 Suite/Test
                 Each test case includes the steps necessary to perform the
   Case
                 test, expected results and also contains (or refers to) any
Development
                 data needed to successfully perform the test.
                 Software Test Reports. (STRs) Software Test Reports           QA Lead, QA
                 will be generated from Test Suites as they are completed.     Engineers
 Functional
                 Bug reporting information from bug database will be
  Testing
                 included in these reports.
                 Status Reports. A weekly status report will be sent to the
                 SIQ Project Manage and Microsoft Test Lead. This report       QA Lead
                 will identify accomplishments completed during the week,
   Weekly        the assignments and goals for the following week, metrics,
                 testing statistics, (once testing begins) and any issues or
                 risks that need to be addressed.


                                              RISKS
Greatest possible risks to successful, timely completion of the combined system test phases are
as follows:

      Delayed start date due to delayed build or un-installable build
      Instability of new software builds due to introduction of new bugs
      Failure of regression tests causing need for new build prior to next test phase




   d9e3938c-b4f1-47bf-879b-c46119214424.doc     Page 10 of 11                            2/15/2013
                 QA TEST PLAN CHANGE LOG AND SIGN OFF
REVISION HISTORY

Date changed          Changes made                               Modify by
April 20, 2004       Created Document                            Stein Wang




SIGN OFF
                      Date              Sign Off By:
Project Manager

QA/Test Manager

Test Lead

Tester




   d9e3938c-b4f1-47bf-879b-c46119214424.doc      Page 11 of 11    2/15/2013

								
To top