Verfication Versus Validation

Verification ensures that the application complies to standards and processes. 

This answers the question " Did we build the right system? "

Eg: Design reveiws, code walkthroughs and inspections.

Validation ensures whether the application is built as per the plan. This answers

the question " Did we build the system in the right way? ".

Eg: Unit Testing, Integration Testing, System Testing and 
UAT.

Endurance And Volume Testing

Load testing can be conducted in two ways. Longevity testing, also called endurance testing, evaluates a system's ability to handle a constant, moderate work load for a long time. Volume testing, on the other hand, subjects a system to a heavy work load for a limited time. Either approach makes it possible to pinpoint bottlenecks, bugs and component limitations. For example, a computer may have a fast processor but a limited amount of RAM (random-access memory). Load testing can provide the user with a general idea of how many applications or processes can be run simultaneously while maintaining the rated level of performance.

Load testing differs from stress testing, which evaluates the extent to which a system keeps working when subjected to extreme work loads or when some of its hardware or software has been compromised. The primary goal of load testing is to define the maximum amount of work a system can handle without significant performance degradation.

What is spike Testing

Spike Testing is a testing process in which an application is tested with sudden increment and decrement in the load.The system is suddenly loaded and unloaded.It is done to see how the system reacts with unexpected rise and fall of users.

What is heuristic testing?

Testing the application based on Experience is referred to as heurisitics testing.

What is alpha and Beta testing?

• Forms of Acceptance testing .
• Testing in the production environment
• Alpha testing is performed by end users within a company but outside development group
• Beta testing is performed by a sub-set of actual customers outside the company

What is acceptance testing

Acceptance testing is one of the last phases of testing which is typically one at the customer place. Testers usually perform the tests which ideally are derived from the User Requirements Specification, to which
the system should conform. The focus is on a final verification of the required business function and flow of the system.

What is installation testing ?

Basic installation
Installation of various configurations
Installation on various platforms
Regression testing of basic functionality

What are the types Of Integration Testing?

Big-bang Integration (non-incremental)

• All components are combined in advance.
• Correction is difficult because isolation of causes is complicated
• Incremental Integration
• Incremental integration can be defined as continuous testing of an
• application by constructing and testing small components.

Top-Down Strategy
It is an incremental approach which can be done Depth-first or Breadth First
Stubs are used until the actual program is ready
Bottom-up Strategy
Process starts with low level modules where critical modules are built first
Cluster approach and test drivers are used
Often works well in less structured applications

What is Black Box Testing ?

Black box testing is derived from functional design specifications, without regard to the internal program structure. This test is done without any internal knowledge of system / product being tested. Functional tests examine the observable behavior of software as evidenced by its outputs, without any reference to internal functions. This is the essence of  ‘black box’ testing.

• Black box tests better attack the quality target. It is an advantage to create the quality criteria from this point of view from the beginning.

• In black box testing, software is exercised over a full range of inputs and the outputs are observed for correctness. How those outputs are achieved, or what is inside the box are immaterial.

• Black Box testing technique can be applied once unit and integration testing is completed i.e. each line code has been covered through white-box testing

Explain Static Testing

In Static Testing, the requirement specification, design, code or any document may be inspected and reviewed against a stated requirement and for some standards against some guideline/checklist. It is part of verification
technique that is not necessarily restricted to testing phase of project lifecycle.


Static Testing includes:

• Walk-through: Code reading and inspections with a team

• Reviews: Formal techniques for specification and design, code reading and inspections.

 Guidelines for conducting a code walkthrough:

•Have review meeting chaired by the project manager.            
•The programmer presents his/her work to reviewers.
•The programmers walk through the code in detail, focusing on the logic of the code.
•Reviewer asks to walk through specific test cases.             
•The chair resolves the disagreements if the review team cannot reach agreement among themselves
and assign duties, usually to the programmer, for making specific changes.                                               
•A second walk through is scheduled.

Many studies show that the single most cost-effective defect reduction process is the classic structural test - the
code inspection or walk-through. Code inspection is like proof-reading - it can find the mistakes the author
missed - the "typo's" and logic errors that even the best programmers can produce.