Unit test
A focused check of a small, defined part of software, such as a rule or function.
Check a small unit deliberately
A unit test examines a small, defined part of software. This can be a rule, function or closely related group. The team should clarify what it treats as a unit and which dependencies the test includes or replaces.
In a fictional example, a rule checks whether a justification is filled in. The test expects rejection for empty input and acceptance for suitable completed input. This checks that rule’s behaviour, not the whole approval workflow. Whether interface, permissions and storage work together correctly needs further suitable checks. Meaningful expected results matter more than a bare count of unit tests.
Sources
Related terms
- Integration testA check that selected software parts work together as intended through their interfaces.
- End-to-end testA check of an agreed workflow across the system parts essential to it.
- Test automationTools perform defined testing tasks, such as execution and comparison with expected results.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps