Skip to content

Definitions in Test

Software Quality Assurance

Software Quality Assurance is the process of monitoring of stages of the software development. This includes requirements gathering and management, software design, software development, application testing and software delivery.

Software Testing

Software Testing is the process to detect differences between requirements and implementation. The purpose is to verify the actual application against the requirements (actual results vs. expected results) and validate, whether the application does what the user wanted to have.

Test Plan

A test plan is a document that describes the scope and objectives of the software testing effort.

Test Case

A test case describes the conditions under which a requirement is satisfied.

Use Case

A use case is a format for specifying a system requirement by the stakeholders. It represents usually a business operation.

Test Case Design

Creating and maintaining an application means not only to design and code the application according to the requirements maintained in the requirements document, but also to design the test cases linked to these requirements and maintained in the test plan.

Test Process

The software test process includes among others to build the test strategy, create the test design, develop the test plan and perform the test execution. A software test process is also about the test techniques. Depending on the software development process, the test process can be waterfall or agile.

Test Suite

A test suite specifies a sequence of actions for the execution of multiple test cases.

Traceability Matrix

A traceability matrix is a two-dimensional table showing traces between different requirements or between requirements and test cases. In a traceability matrix gaps between requirements and test cases can be easily identified.

Bug

A bug is a mismatch between actual and expected behavior of a software application. The expected behaviour is specified in the requirements and the real behaviour is the result of a failed test case.

Software Configuration Management

Software Configuration Management controls the evolution of an application including all artifacts belonging to this application. SCM controls all changes made to the system and notify users.

The different types of testing are explained in the "Test Type" Post here on this page.

To be continued...