What’s Test Plan?

What’s Test Plan?

. Verify and ensure that a product or system meets its design specification and other requirements.

. Control and monitor

In software testing, a test plan gives detailed testing information regarding an upcoming testing effort, including

.Test Scope

. Test Requirements

. Strategy

. Risk

. Test Environment Configuration

. Test Tools

. Schedule

. Resource

. Test deliverables

From Test Plan, we will know a detail of how the testing will proceed, who will do the testing, what will be tested, in how much time the test take place, and to what quality level the test will be performed.

How to use Test Plan?

Test Plan could be describle by excel and microsoft project file. We can create many sheet.

           

Who write/read Test Plan?

       § QC Lead/QC Manager

       § QC team

       §  Project Manager

Table of Test Plan such as:

1. Coverage:

§ Coverage is included some items such as:

§  Project Name

§  Project Release version

§  Document version

§  Date

§  Prepared by

2. Test Scope:

2.1 Features to be Tested:

§  List the features of the software/product to be tested.

§  Provide references to the Requirements and/or Design specifications of the features to be tested

2.2 Features Not to Be Tested:

§  List the features of the software/product which will not be tested.

§  Specify the reasons these features won’t be tested.

3. Test Requirement:

3.1 Functionality to be Tested:

§  List the functionality of the software/product to be tested.

3.2 Usability

§  Good performance

§   Easy to use

§  Friendly user

   3.3 Reliability

§  Verify all function run correctly

3.4 Performance

§  Fastly and correctly

   3. 5 Supportability

4. Strategy:

4.1 Test type

Function test	Benchmark test	Volume test
Load test	Performance test	Stress test
Integrity test	Add hoc test	Usability test
Installation test	Structure test	Security test

4.2 Test phase

Integration test

System test

4.3 Test Priority

List of module/function list are arranged from top to bottom

5. Risk:

§  Risk list is describled in here

Example:

§Cannot catch change requirements when executing test phase

§Code delivery is late: Code for application under test is behind schedule

6. Test Environment:

6. 1 What is a Testing environment for software testing

§A testing environment is a setup software and hardware on which the testing team is going to perform the testing of the newly built software product. it's included hardware and logical setup that includes Server Operating system, client operating system, database server, front end running environment, browser(if  web application), IIS (version on server side) or any other software components required to run this sofware product.

Nowadays, most testing looks like this: you get a physical environment, execute tests on it, and revert it to a clean state by using images. This approach is convenient because you don’t have to configure everything all over again. But there are some negatives as well.

§  When you modify the hardware configuration, you must update the image, because it’s hardware specific;

§  If the hardware configuration fails, you can lose all your data and test results, which is a potential risk for the project.

§  The approach doesn’t scale well because a single hardware configuration can be at most a single test environment.

Virtualization has the same advantages as images-driven test environment setup and more:

§  Better utilization – you can run more than one virtual machine (VM) on a single piece of hardware as long as there are enough resources. Provide your Quality Engineers their own environment to play with!

§  Revert to a previous state – cleanup is easy because VMs are designed with that in mind. You can easily debug a problem by using snapshots. They are quite fast, too.

§  Hardware failure – it’s irrelevant for the virtualized infrastructure. Since VMs are just files, you can back them up, in order to minimize loss, in case of server crashes

§  Pool of resources - no need to reconfigure and recreate images when you buy new hardware. You just add it to the pool of resources.

§  Maintenance & automation – with minimal effort you can replicate VMs by using virtualization and the already available automation scripts. You can even create your own automation scripts!

6.2 Test Environment Configuration

Example:

§  Cannot catch change requirements when executing test phase

§  Code delivery is late: Code for application under test is behind schedule

By HoaLe