Lihttestus

Lihttestus is a term used in software quality assurance to denote a lightweight, minimal set of tests designed to verify the most important functionality of a software build after changes. The aim is to provide rapid feedback at low cost, rather than comprehensive verification. The term is informal and not part of formal QA standards.

The name appears to derive from Finno-Ugric language roots, with meanings akin to “simple” or “easy” and “testing.” In practice, lihttestus is realized as a small battery of automated checks or quick manual checks that cover core flows, such as login, data entry, and essential business rules, rather than every module in depth.

Common practice is to run lihttestus in continuous integration or deployment pipelines on every commit or pull request. Tests focus on critical paths and integration points, aiming to catch major regressions early. Typical execution times range from a few seconds to several minutes, making them suitable for frequent runs without delaying development.

Lihttestus is often contrasted with a full test suite and with larger smoke or sanity tests. It is intended to complement, not replace, broader testing by quickly identifying obvious regressions after changes and by providing developers with fast feedback on new code.

Limitations include its narrow scope, the risk of missing deeper defects, and the need for careful selection and maintenance of test cases. Its effectiveness depends on accurate identification of critical paths and reliable automation, and it should be integrated with broader testing strategies for best results.

See also: smoke test, sanity check, regression testing, test automation.