Test automation
Tools perform defined testing tasks, such as execution and comparison with expected results.
Run repeatable checks with tools
Test automation assigns defined testing tasks to tools, including step execution and result comparison. Expected outcomes, test data and boundaries must be clear. A tool does not choose the right business questions by itself.
In a fictional example, a script should approve a request and check the intended stored state. Executing clicks alone is insufficient. Plan test setup, maintenance and failure investigation too. Changing data or unclear waiting conditions can produce unstable results. Investigate the cause rather than treating one successful rerun as sufficient evidence. Which tasks additionally need human judgment, such as clarity, remains a separate decision.
Sources
Related terms
- Unit testA focused check of a small, defined part of software, such as a rule or function.
- End-to-end testA check of an agreed workflow across the system parts essential to it.
- Regression testA check for unwanted effects of a change on behaviour that is still required.
- Test coverageThe share of an explicitly defined set, such as executable statements or requirements, that has been tested.
- 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.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps