Krishna Logo
CLICK HERE TO SEE THE LOCATIONS
Divied
Ria / Kumar @ 1-(877) 864-8462

 

Loading
Latest News
Home Navigation Divied
SOFTWARE TESTING Navigation Divied TESTPLANS
TESTPLANS
 
1TEST PLAN TEMPLATE
Date Posted: 02/20/2013

 
 

testapproach document This document identifies the Testing Depa...  

 
 
3TEST PLAN FOR ARC & SUGAR CRM
Date Posted: 05/04/2012

 
 
4
TABLE OF CONTENTS

 1. Test Plan Identifier.. 4

2. Introduction.. 4

2.1 Objectives. 4

2.2 Background. 4

2.3 Scope. 5

2.4 References. 5

3. Test Items.. 5

3.1 XYZ Procedures. 5

3.2 Consumer Procedures. 5

3.3 Channel Owner Procedures. 6

3.4 Management and Reporting Procedures. 6

3.5 Scaling Ability Procedures. 6

4. Features to be Tested.. 6

5. Features not to be Tested.. 7

6. Approach.. 7

6.1 Functional Testing. 8

6.2 Interface Testing. 8

6.3 Regression. 8

6.4 Security Testing. 8

6.5 Recovery Testing. 8

6.6 Performance Testing. 9

6.7 Comprehensiveness. 9

6.8 Constraints. 10

7. Item Pass/Fail Criteria.. 10

8. Suspension Criteria and Resumption Requirements   10

8.1 Suspension Criteria. 10

8.2 Resumption Criteria. 10

9. Test Deliverables.. 10

10. Environmental Needs.. 11

10.1 Hardware. 11

10.2 Software. 11

10.3 Security. 11

10.4 Tools. 11

11. Responsibilities.. 11

11.1 System Test Group. 12

11.2 Development Project Group. 12

11.3 Test Manager. 12

11.4 Senior Test Analyst. 12

11.5 Test Analyst. 12

12. Staffing and Training Needs.. 12

12.1 Staffing. 12

12.2 Training. 13

13. Tasks and Schedules.. 13

14. Risks and Contingencies.. 13

15. Document History.. 14

15.1 Significant Changes. 14

15.2 Revision History. 14

15.3 Approvals. 14

15.4 Distribution List. 14

 1. Test Plan Identifier

BR04 P01 STP (Xyz TestingPhaseRelatedDoc, ProjectPhase 01, System Test Plan)

2. Introduction

This document is the System Test Plan for Xyz Software & Web Application being developed by abc Group. Xyz Software & Application is an internet-based technology solution to enable businesses deliver secure advertisements, printed coupons, etc to focused, targeted consumers.

It is to facilitate consumers to trade their demographic data for (geographically focused) money off coupons & vouchers, which they print and redeem at physical stores or web sites. The objective of the solution is to provide advertisers and consumers a simple well-designed customizable internet portal that gives them choice and control and to offer a turnkey solution for the presentation and redemption of money off vouchers and coupons.

2.1 Objectives

The System Test Plan for Xyz Software & Web Application supports the following objectives.

  1. To define the activities required for preparing and conducting the System Test.
  2. To communicate to all responsible parties the tasks that they are to perform and the schedule to be followed in performing those tasks.
  3. To detail the sources of information used to prepare the plan and those required to prepare and execute tests.
  4. To identify and define the testing tools and environment needed to conduct the System Test.

2.2 Background

After careful observations earlier in the Inception phase, abc Technology Group has provided Recommendations and Comparisons of J2EE/ .Net / Microsoft Solutions to Xyz Ltd. for the development of the solution. The Management Review Committee of Xyz approved the option for developing the solution in .NET, while retaining abc NetAdvertiser (J2EE application).

The Xyz Technical Group furnished a Statement of Requirements (Xyz Phase I - Functional Specification 1.1), and Xyz Ltd. and abc India Pvt. Ltd. signed a SOW No.1 on January 23, 2004.

2.3 Scope

This Test Plan covers a full Systems Test of Xyz Software & Web Application. It includes operator and user procedures, as well as programs and job control. In addition to comprehensively testing multi-program functionality of the complete solution, external interfaces, security, recovery, and performance are also evaluated.

2.4 References

The following documents were used as sources of information for the Test Plan:

No. Document Name Document Identifier
1 Xyz_Options_abc.doc BR01-TechOptions
2 Xyz Phase I - Functional Specification 1.1 BR01-StmntOfReqs
3 abc SOW1 Xyz v 1.0.doc BR01-SOW1
4 Xyz - Software Requirements Specification.doc BR02-SRS

 

3. Test Items

All items that make up the Xyz Software & Web Application will be tested during the System Test. The versions to be tested will be placed in the appropriate libraries by the configuration administrator. The administrator will also control changes to the versions under test and notify the test team when new versions are available.

The following documents will provide the basis for defining correct operation:

No. Document Name Document Identifier
1 Xyz Phase I - Functional Specification 1.1 BR01-StmntOfReqs
2 Xyz - Software Requirements Specification.doc BR02-SRS
3 Project Plan for Execution - Xyz BR02-PPE
4 ABC Design Docs BR03-DGN1

BR03-DGN2

BR03-DGN3

BR03-DGN4

The items to be tested are as follows:

3.1 XYZ  Procedures

The procedures specified for the XYZ Advertiser will be tested.

3.2 Consumer Procedures

The procedures specified for the Consumer will be tested.

3.3 Channel Owner Procedures

The procedures specified for the Channel Owner will be tested.

3.4 Management and Reporting Procedures

The procedures specified for the Management and Reporting will be tested.

3.5 Scaling Ability Procedures

The procedures specified for Scaling Ability will be tested.

4. Features to be Tested

The following list describes the various Actors for which testing will be done:

No. Actors
1 Actor - Consumer
2 Actor - Standard User
3 Actor - SAM (System Admin Manager)
4 Actor - Xyz Super Administrator
5 Actor - Advertiser
6 Actor - Channel Partner
7 Actor - Affiliate
8 Global Requirements

 

The following list describes the Features that will be tested:

No. Test Design Specification No. Description
  Test ABC 1 Module ABC 1
1   Will be updated from the latest system documents and covered in version 1.0 of Test Plan (during the first phase preparation of test cases).
2    
3    
4    
5    
     
     
     
     
  Test ABC 2 Module ABC 2
     
     
     
     
     
     
     
     
     
     
  Test ABC 3 Module ABC 3
     
     
     
     
     
  Test ABC 4 Module ABC 4
     
     
     
     
     

 

5. Features not to be Tested

The following features will not be included in the System Tests because they are not to be used when the system is initially installed.

ABC 1 (Will be updated from the latest system documents and covered in version 1.0 of Test Plan)
ABC 2
ABC 3

The development phase 02 documentation will contain a Test Plan for these features.

The test cases will not cover all the possible combinations of options with both phase 01 and phase 02. Only combinations that are known to be required within phase 01 will be tested.

6. Approach

The test personnel will use the system documentation to prepare all test design, test case and procedure specifications. This approach will verify the accuracy and comprehensiveness of the information in the documentation in those areas covered by the tests.

Test personnel will assist in developing the test designs, test cases, and procedure specifications. This will help ensure that the tests represent the production use of the system.

6.1 Functional Testing

Functional testing will occur first and will ensure the following:

  1. The site features function as expected.
  2. The various components have been integrated correctly.
  3. The site features are performing their specific functions within the context of the overall site functionality, as defined in the Functional Specification documentation.

6.2 Interface Testing

The interfaces between the various modules and features wherever communication happens between them will be tested. A separate bed of test data will be prepared and maintained for this purpose.

6.3 Regression

It is assumed that several iterations of the System Test will be done in order to test program modifications made during the System Test period.

A regression test will be performed for each new version of the system to detect unexpected impact resulting from program modification.

The regression test will be done by running all of the tests on a new version that were run on the previous version, and then comparing the resulting files.

6.4 Security Testing

Attempted access with out a valid e-mail address or proper password to the on-line data entry and display transactions will be tested.

As SSL is implemented to ensure the security of the advertisers and channel owners hosted databases, the same for SSL encryption will be tested.

Testing will be done to ensure that possible administrative functions are hidden behind SSL security.

6.5 Recovery Testing

The machine will be halted during stand-alone time, and the recovery procedures will be executed in order to test for Recovery of the system.

6.6 Performance Testing

Performance will be evaluated against the performance requirements by measuring the run times of several jobs using the production data volumes. The performance of the system to some extent is expected to rely on the hosting environment (Functional Spec: Page 11,Para1).

It is assumed that the hosting environment will be:

Environment
OS Windows Server 2003
Hardware Domain Controller (to control front side servers) Single Processor, Raid 1 Mirror, Dual Network Cards, RAM 1Gb
Free hard drive 2 x 18Gb min Hard Drives
Bandwidth Min 1Mb/sec

Performance requirements as per functional specification is given below:

Requirements
Ability to serve pages per month Minimum 1,000,000
Number of records in the database Up to 10,000,000
Database to be constructed with forward compatibility for Oracle 9i  
Number of concurrent users on public site at any one time 50
Number of concurrent users on advertisers’ admin site (AAS) at any one time 50
Number of concurrent users on system admin management (SAM) site at any one time 5

 

6.7 Comprehensiveness

  1. Each of the system features described will have at least one associated test design specification.
  2. Each of the user procedures specified will be tested at least once.
  3. In addition, each job control procedure will be executed at least once.

A coverage matrix will be used to relate test design specifications to each of the areas described above.

6.8 Constraints

Final implementation date ofApril 30, 2004has been planned for Xyz Software & Web Application. It will be necessary to meet this date because the Xyz begins full operation onMay 1, 2004and they must have this Application in production.

7. Item Pass/Fail Criteria

Each test case will define its own pass/fail criteria within the test script. When the test fails, it is entered into the Defect Tracking System and reported to the responsible person. During the test, the test analyst will list all URLs that should be tested and whether the URL listed is passed or failed, and any comments.

8. Suspension Criteria and Resumption Requirements

8.1 Suspension Criteria

Inability to use the main features or the information database will cause suspension of all testing activities.

8.2 Resumption Criteria

When a new version of the system is transmitted to the test team after a suspension of testing has occurred, a regression test will be run.

9. Test Deliverables

The following documents will be generated by the System Test team and will be delivered to the Configuration Management team after test completion.

Test Documentation:

No. Item
1 System Test Plan
2 System Test Design Specifications
3 System Test Case Specifications
4 System Test Summary
5 System Test Summary Log
6 System Test Incident Reports
7 System Test Report

 

10. Environmental Needs

10.1 Hardware

The testing will be done on development hardware configuration. A separate Server is required during the testing for performance evaluation. The details will be confirmed after discussion with the development manager.

Since most of the testing must be done during prime operating hours, three online terminals must be available to the test team during this period.

10.2 Software

10.2.1 Operating System

The production operating system will be used to execute these tests.

10.2.2 Communications Software

All on-line programs will be tested under the control of the test communication software.

10.3 Security

Security will be limited to existing controls.

10.4 Tools

The following test tools are required to develop and evaluate the System Tests:

  1. Bugzilla: This tool will be used to enter test incidents, allocate the incidents, closure and tracking of incidents.
  2. Spread Sheets: Excel Spread Sheets will be used for maintaining and updating test cases and also to communicate the test summary.
  3. .NET ACT: This tool will be used for performance evaluation of the application and the development team will involve with the testing team.
  4. WinCVS: This tool will be used for storage and configuration of test related information, and data.

11. Responsibilities

The following groups have responsibility for segments of the testing.

11.1 System Test Group

This group comprising the test manager, senior test analyst, and test analyst provide the overall management of the testing, technical testing expertise, execution of tests and reporting results.

11.2 Development Project Group

This group transmits the system to be tested and responds to the System Test incidents summary and reports. This group does any program debugging that is required. It also supplies the database auditor.

11.3 Test Manager

Manages the test effort. Reviews and incorporates all existing test documents, verifies functional requirements have been met, identifies necessary QC/test resources, and review and track defect reports.

11.4 Senior Test Analyst

Prepares the test cases. Analyzes the application under test from the perspective of user. Conducts testing that addresses site functionality, end user, integration, operation, and various hardware configurations including browsers, and operating systems. Logs defects found during testing into the defect-tracking database.

11.5 Test Analyst

Assists in the preparation of test cases. Conducts testing that addresses site functionality, end user, integration, operation, and various hardware configurations including browsers, and operating systems. Logs defects found during testing into the defect-tracking database.

12. Staffing and Training Needs

12.1 Staffing

The following staff is needed to carry out this testing project.

12.1.1 Test Group

Test Manager                1

            Senior Test Analyst       1

            Test Analyst                  1

12.1.2 Xyz User

            Client’s Employee         1

12.2 Training

The testing personnel must be trained in using any third-party tools/applications provided by Client, which might be used in integration with the application being developed. The development manager accepts this responsibility.

The testing personnel must be trained in any new testing tools that might be incorporated in the testing of the application. The development manager and test manager accept this responsibility.

13. Tasks and Schedules

Testing will be performed by testing personnel according to the schedule in the following table that lists important milestones to be met and their required due dates. The testing process as a whole should follow the overall development effort of the application.

Milestones Date(s) Resources
System Test Plan 9.3.2004 - 19.3.2004 1 Test Manager full time
System Test Cases 9.3.2004 - 19.3.2004 1 Sr Test Analyst full time
Module 1 Testing   1 Test Analyst full time
Module 2 Testing   1 Test Analyst full time
Module 3 Testing   1 Test Analyst full time
Module 4 Testing   1 Test Analyst full time
Module 5 Testing   1 Test Analyst full time
Module 6 Testing   1 Test Analyst full time
Actor 1 Testing   1 Test Analyst full time
Actor 2 Testing   1 Test Analyst full time
Actor 3 Testing   1 Test Analyst full time
Actor 4 Testing   1 Test Analyst full time
Alpha Release 1 Testing (Internal)   1 Sr Test Analyst full time

1 Test Analyst full time

Alpha Release 2 Testing (Internal)   1 Sr Test Analyst full time

1 Test Analyst full time

Hardware, software, and testing tools will be used for testing during the period fromMar 20, 2004throughApril 30, 2004.

14. Risks and Contingencies

No. Risk or Contingency Resolution
1 If testing schedule is significantly impacted by system failure, … The development manager has agreed to assign a full time person to the test team to do debugging.
2 If testing schedules are significantly effected by delayed schedules in development and the project deliverable schedules have to be met, … The development manager has agreed to assign a full/part time test analyst.
3 If the hardware problems impact system availability during the day, … The test team will schedule their activities during the evening (or, if effected during the evening, then the activities will be carried to the next day).
4 If Change Requests significantly impact the testing schedules, … The development manager has agreed to accept a change in testing schedules.

 

15. Document History

15.1 Significant Changes

1. Added more sections for Test Plan.

2.[v1] 

15.2 Revision History

Date Version Changes Made by Change Description
3.17.2004 0.9 QC Team Added more sections for Test Plan. Modified content with reference to updated Project Docs.
  1.0 QC Team  
  1.1 QC Team  

 

15.3 Approvals

Approved By Title Company Date of Approval Version
  Proj Mngr abc    
  QA Mngr abc    
  Client Proj Mngr Xyz    

 

15.4 Distribution List

Name Title Company Date of Issue Version
  Proj Mngr abc    
  QA Mngr abc    
  Delivery Mngr abc    
  Client Proj Mngr Xyz    

Download using below link

SYSTEM TESTPLAN
Date Posted: 05/04/2012

TABLE OF CONTENTS  1. Test Plan Identifier.. 4 2. Introduction.. 4 2.1 Objectives. 4 2.2 Background. 4 2.3 Scope. 5 2.4 References. 5 3. Test Items.. 5 3.1 XYZ Procedures. 5 3.2 Consumer Procedures. 5 3...  

 
 
5HOW TO BUILD AN EFFECTIVE SOFTWARE TESTING PRACTICE
Date Posted: 05/04/2012


CLICK AND DOWNLOAD THE FILE FROM BELOW LINK

 
 

1.      Introduction   The co...  

 
Shadow Bottom
   
© 2005 - 2014 Krishna Training.