devops:tests
This is an old revision of the document!
Table of Contents
Tests
| Unit Tests | |
| Smoke Tests | A simple integration test. It is inspired from hardware testing, which checks for the smoke from the hardware components once the hardware's power is switched on. Similarly in Software testing context, smoke testing refers to testing the basic functionality of the build. |
| Integration Tests (I&T) | Integration testing (sometimes called integration and testing) is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before validation testing. |
| System Integration Test (SIT) | System integration testing involves the overall testing of a complete system of many subsystem components or elements. The system under test may be composed of hardware, or software, or hardware with embedded software, or hardware/software with human-in-the-loop testing. |
| Validation Test | |
| Regression Tests | Regression testing is a type of software testing that verifies that software that was previously developed and tested still performs correctly after it was changed or interfaced with other software. Changes may include software enhancements, patches, configuration changes, etc. |
| Acceptance Test | Test that a feature or use case is correctly implemented. It is similar to an integration test, but with a focus on the use case to provide rather than on the components involved. |
| System Test | Tests of a system as a black box. Dependencies on other systems are often mocked or stubbed during the test (otherwise it would be more of an integration test). |
| Pre-flight check | Tests that are repeated in a production-like environment, to alleviate the 'builds on my machine' syndrome. Often this is realized by doing an acceptance or smoke test in a production like environment |
devops/tests.1460615431.txt.gz · Last modified: (external edit)