Testcykler

Testcykler are predefined sequences of steps and inputs used to evaluate a product, system, or process under controlled conditions. The term is used in Danish and Norwegian contexts to describe cycles that simulate typical usage, extreme conditions, or regulatory requirements. They are applied across software, hardware, automotive, consumer electronics, and industrial testing.

The primary purpose of testcykler is to verify functionality, assess performance and reliability, identify defects, and ensure compliance with specifications or standards. A cycle specifies the starting state, input signals, environment, duration, and expected result. Repetition of cycles enables measurement of wear, degradation, or stability over time.

Design of a testcykel involves deriving representative scenarios from requirements, selecting boundary and corner cases, and defining acceptance criteria. Cycles can be functional (validating features), load or stress (pushing limits), endurance (long-run stability), or recovery (post-stress reset).

In software testing, a testcykel may refer to an iteration of test planning, case execution, defect reporting, and retesting within a release cycle. Testcykler may be organized by risk, module, or user story. Both automated and manual tests can be part of a cycle.

Metrics associated with testcykler commonly include pass rate, defect density, cycle count, and reliability indicators such as mean time between failures. Examples include a smartphone battery test cycle that charges from 5% to 100%, discharges to 5%, rests, and repeats for hundreds of cycles to assess capacity fade.