Test Plan Template

Format Of Test Plan:

Project Name : XYZ

1. Introduction :

The Software Test Plan (STP) is designed to prescribe the scope, approach, resources, and schedule of all
testing activities. The plan must identify the items to be tested, the features to be tested,
the types of testing to be performed, the personnel responsible for testing, the resources and schedule
required to complete testing, and the risks associated with the plan.

1.1 Objectives :

 Describe, at a high level, the scope, approach, resources, and schedule of the testing activities.
Provide a concise summary of the test plan objectives, the products to be delivered,
 major work activities, major work products, major milestones, required resources,
and master high-level schedules, budget, and effort requirements.


1.2 Testing Strategy : 

Continue read the Blog ..

Software Testing FAQ’s

Software Testing FAQ’s
Some Important Software Testing FAQ's :

1)      Explain difference between QA and Testing?
2)       If tester go in vacation, how he handle situation in his absence?
3)      Explain Black box testing and White box testing?
4)      What is V & V model? Or what is Verification & Validation?
5)      How many test cases written by you in one day?
6)      When testing should stopped?

For more FAQ please Click here ..

Waterfall Model

Testers have very well known about these models-

Waterfall Model
V Model
Spiral Model
Agile Model
'W' Model
Butterfly Model

 Let we discuss about waterfall model, later on we will study about remaining models.
Waterfall model - is a step by step method for achieving the task. In this model one can go to the next phase only after the completion of current phase.
In this model each phase of activity is followed by the verification and validation activity. Every phase is
Completed with testing then going to the next phase of cycle. Here we can move immediate previous phase.
Like, here we take one example - We cannot go from testing phase to the design phase.

Software Testing Types

These are some software testing types,

• Black box testing: In black box testing you don't need to know the internal design in detail or have a good knowledge about the code for this test. It's mainly based on functionality and specifications, requirements.

• White box testing: White box testing based on detailed knowledged of the internal design and code. Tests are performed for specific code statements and coding styles.

• Integration testing: Testing of combined parts of an application to determine if they function together correctly. It can be any type of application which has several independent sub applications, modules.

• Functional testing: Black box type testing to test the functional requirements of an application. Typically done by software testers but software programmers should  also check if their code works before releasing it.

• Unit testing: The most micro scale of testing to test specific functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code.

• System testing: Black box type testing that is based on overall requirements specifications. Covers all combined parts of a system.

• End to End testing: It's similar to system testing. Involves testing of a complete application environment similar to real world use. May require interacting with a database, using network communications, or interacting with other hardware, applications, or systems.

• Regression testing: Re-testing after software is updated to fix some problems. The challenge might be to determine what needs to be tested, and all the interactions of the functions, especially near the end of the sofware cycle.

• Sanity testing or smoke testing: An initial testing effort to determine if a new sw version is performing well enough to start for a major software testing.

• Load / stress / performance testing: Testing an application under heavy loads. Such as simulating a very heavy traffic condition in a voice or data network, or a web site to determine at what point the system start causing problems or fails.

• Usability testing: Testing to determine how user friendly the application is. It depends on the end user or customer.

• Security testing: Testing to determine how well the system protects itself against unauthorized internal or external access and intentional damage.

• Compatability testing: Testing how well software performs in different environments. Particular hardware, software, operating system, network environment etc. Like testing a web site in different browsers and browser versions.

• Install / Uninstall testing: Testing of full, partial, or upgrade install / uninstall processes.

• Recovery / failover testing: Testing to determine how well a system recovers from crashes, failures, or other major problems.

• Alpha testing: Testing of an application when development is nearing completion. Minor design changes may still be made as a result of such testing. Typically done by end users.

• Beta testing: Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end users or others.