Software Testing Strategies: Verification, Validation, and Integration

Test Strategy

• Test Planning
• Design test cases
• Test Run
• Collection and evaluation

The software is tested to discover errors made inadvertently when carrying out their design and construction.

The tests are a set of activities you can plan ahead and carry out systematically. For this reason, you must define the process of software engineering template for software testing.

A software testing strategy should include: evidence of low-level, high level evidence.

Verification: a set of activities to ensure that software correctly implements a specific function.

Validation: different set of activities to ensure that software built is consistent with customer requirements.

Only once the software architecture comes into play is completed Independent Test Group.

The role of independent test group (GIP) is to eliminate problems of letting the builder proves what he has built.

Test Strategy for Conventional Software Architectures

• Test Drive: Focus on each unit (component) source code.
• Integration testing: How is integrated into the design and software architecture.
• Test validation: the requirements are validated by comparing them with the software built.
• Test system: We tested the software as a whole.

The test drive the verification process focuses on the smallest unit of software design: the software component or module.

They focus on the internal processing logic and data structures within the boundaries of a component.

Unit Test

• Interface: Ensure that the information is properly flowing outward and inward.
• Local ED: Ensuring that data integrity is maintained throughout the implementation.
• Boundary conditions: Ensure that it operates properly within the limits.
• Independent Roads: Ensure that all instructions have been executed at least 1 time.
• Roads error handling: Ensure all error handling paths.

Integrity Test: The objective is to take the modules tested by unit testing and build a program structure that is in accord with the dictates of the design.

Incremental Integration: It is often a tendency to attempt an integration that combines all components. The program is tested as a whole and there is chaos. You will find lots of errors. The correction is difficult. Incremental integration is the antithesis. It is built and tested in small increments, where it is easier to isolate and correct errors.

Integration in descending modules are integrated moving down the control hierarchy, beginning with the main control module (main program).

The modules subordinates (followers anyway) the main control module are incorporated into the structure.

Integration ascending begins construction and testing with atomic modules.

The smoke test is an approach to integration testing is often used while developing software products.

It is designed as a mechanism for setting the pace in projects where time is critical.

Test-Integration Test Phases

• User interaction (selection of commands, create drawings, representation of the deployment)
• Handling and analyzing data (creation of symbols, assignment of dimensions)
• Processing and generation of deployment (two-and three-dimensional display, images and graphics)
• Administration database (access, update, integrity, performance)

The alpha test is performed by a client in the place of development.

Software is used naturally with the developer and user observer and recording errors and usage problems. The alpha test is conducted in a controlled environment.

The beta test is performed by end users of software in the workplaces of customers.

Unlike the alpha test, the developer is not present normally. Thus, the beta test application is a "live" software in an environment that can not be controlled by the developer.