Model for Testing in software testing methodologies

The image shows a model of testing process
It includes three models: A model of the environment, a model of the program and a model of the expected bugs

Tests

Inputs must be prepared

Outcomes should be pre directed

Tests should be documented
Commands need to be executed
Results are to observed

A unit is the smallest testable piece of software that can be compiled, assembled, linked, loaded etc
A unit is usually the work of one programmer and consists of several hundred or fewer lines of code
Unit Testing is the testing we do to show that the unit does not satisfy its functional specification, or that its implementation structure does not match the intended design structure
A component is an integrated aggregate of one or more units
Component Testing is the testing we do to show that the component does not satisfy its functional specification or that its implementation structure does not match the intended design structure
Unit testing aims at testing each of the components that a system are built upon. As long as each of them work as they are defined to , then the system as a whole has a better chance of working together

Integration is the process by which components are aggregated to created larger components
Integration testing is testing done to show that even through the components were individually satisfactory (after passing componet testing)
It checks if the combination of components are incorrect or inconsistent
It verifying software quality by testing two or more depedent software modules as a group

A system is a big component
System Testing is aimed at revealing bugs that cannot be attributed to components
It includes testing for performance, security, accountability, configuration sensitivity, startup and recovery
System testing enables us to test, verify and validate both the business requirements as well as the applications architecture

CSE Study Material