Posts Tagged ‘Test Plan’

What is a Test Plan ?

A test plan is a systematic approach to testing a system such as a machine or software. The plan typically contains a detailed understanding of what the eventual workflow will be.
It can also be defined as the high level testing documents that describe test project.
Test plan includes :
1. Scope of Testing
2. Schedule : It contains Test Strategy or Approach.
3. Test Deliverables
4. Release Criteria
5. Risks and Contingencies

What is a Test Case ?

The good test case is one which has maximum probability of finding the bugs.
The test cases should be good enough explanator, because problem well stated means its half solved.
“The essential value of any test case lies in its ability to provide information (i.e. to reduce uncertainty).”
Test Cases usually have the following components.

* Test Case Summary
* Configuration
* Initial Condition
* Steps to run the test case
* Expected behavior/outcome
* Priority

Click here for Test case format.


Read Full Post »

When we test a Software Product, we have to fix a Test Plan first. While creating a Test Plan, deciding the Testing methodology plays a vital role followed by writing the Test Cases. Test Methodology is the strategy used to test the system.
Following are the steps included in Testing Methodology,
1) Unit Testing – Unit Testing is done @the developers’ end. In this they have to check whether the functionality implemented by them is working properly or not. Each smallest unit of the application is tested whether it is correctly working.

2) Integration Testing – In this kind of Testing, tester test various modules of the application. It deals with the defects in the interfaces and interaction between the modules.

3) System Testing – It tests a completely integrated system to verify whether the software meets the requirements.

4) System Integration Testing – verifies that a system is integrated to any external or third party systems defined in the system requirements.

Before shipping the final version of software, alpha & beta testing are done finally.

5) Alpha Testing – Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing.

6) Beta Testing – Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users.

7) Acceptance Testing – Finally Acceptance Testing can be conducted by the End-user, customer or client whether or not to accept the product. This testing can be performed as the part of Hand-off process between any two phases of developement. Successful Acceptance Testing is required before handing over the product to the customer.

8 ) Regression Testing – After modifying the software, either for a change in functionality or to fix defects, a Regression Test reruns the previously run Test cases. Regression Tests are often automated, they can be performed at any or all level of Testing.

Read Full Post »