FAQ

User Acceptance Tests - verify that the application meets user expectations and business requirements.

Key testing performance metrics - e.g. number of bugs, test coverage, defect fix rates, etc.

A single test scenario with precise inputs, expected outputs and success conditions.

A document that defines what will be tested, how, when and by whom. It also includes risks and metrics.

Basic verification of system functionality - checking whether the application is running at all and is testable

Retesting already tested parts of the application after changes to avoid new regressions (errors).

A bug or deviation in the application that causes malfunction or undesired behavior.

International certification scheme for software testers. Includes Foundation, Advanced and Expert levels.

A global standard for software testing, defining processes, documentation and testing techniques.

Informal testing based on testers' intuition and experience, with no predefined steps.

Matrix linking requirements and tests - used to verify completeness of test coverage.