Testing Techniques

• Black Box Testing
• White Box Testing
• Regression Testing
• These principles & techniques can be applied to any type of testing.

Black Box Testing

Testing of a function without knowing internal structure of the program.

White Box Testing

Testing of a function with knowing internal structure of the program.

Regression Testing

To ensure that the code changes have not had an adverse affect to the other modules or on existing functions.

Functional Testing

 Study SRS
 Identify Unit Functions
 For each unit function
• Take each input function
• Identify Equivalence class
• Form Test cases
• Form Test cases for boundary values
• From Test cases for Error Guessing
 Form Unit function v/s Test cases, Cross Reference Matrix
 Find the coverage

Unit Testing:

The most ‘micro’ scale of testing to test particular functions or code modules. Typically done by the programmer and not by testers
• Unit - smallest testable piece of software
• A unit can be compiled/ assembled/ linked/ loaded; and put under a test harness
• Unit testing done to show that the unit does not satisfy the functional specification and/ or its implemented structure does not match the intended design structure

Integration Testing:

Integration is a systematic approach to build the complete software structure specified in the design from unit-tested modules. There are two ways integration performed. It is called Pre-test and Pro-test.

1. Pre-test: the testing performed in Module development area is called Pre-test. The Pre-test is required only if the development is done in module development area.
2. Pro-test: The Integration testing performed in baseline is called pro-test. The development of a release will be scheduled such that the customer can break down into smaller internal releases.

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 or others, not by programmers or testers.

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, not by programmers or

System Testing:

• A system is the big component
• System testing is aimed at revealing bugs that cannot be attributed to a component as such, to inconsistencies between components or planned interactions between components
• Concern: issues, behaviors that can only be exposed by testing the entire integrated system (e.g., performance, security, recovery).

Volume Testing:

The purpose of Volume Testing is to find weaknesses in the system with respect to its handling of large amounts of data during short time periods. For example, this kind of testing ensures that the system will process data across physical and logical boundaries such as across servers and across disk partitions on one server.

Stress testing:

This refers to testing system functionality while the system is under unusually heavy or peak load; it’s similar to the validation testing mentioned previously but is carried out in a “high-stress” environment. This requires that you make some predictions about expected load levels of your Web site.

Usability testing:

Usability means that systems are easy and fast to learn, efficient to use, easy to remember, cause no operating errors and offer a high degree of satisfaction for the user. Usability means bringing the usage perspective into focus, the side towards the user.

Security testing:

If your site requires firewalls, encryption, user authentication, financial transactions, or access to databases with sensitive data, you may need to test these and also test your site’s overall protection against unauthorized internal or external access.

Glass Box Testing

Test case selection that is based on an analysis of the internal structure of the component. Testing by looking only at the code.
Some times also called “Code Based Testing”. Obviously you need to be a programmer and you need to have the source code to do this.

Test Case

A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

Operational Testing

Testing conducted to evaluate a system or component in its operational environment.

Validation

Determination of the correctness of the products of software development with respect to the user needs and requirements.

Verification

The process of evaluating a system or component to determine whether the products of the given development phase satisfy the conditions imposed at the start of that phase.

Control Flow

An abstract representation of all possible sequences of events in a program’s execution.

CAST
Acronym for computer-aided software testing.

Metrics
Ways to measure: e.g., time, cost, customer satisfaction, quality.