Check out the glossary for definitions on testing essentials, and DevOps related terms.
Action Based Testing (ABT)
A modular-design and action-driven test method that provides a systematic approach to increase the success of automated testing. Modular-design addresses the challenges of test planning and test case management through efficient test organization.
Action-driven test development eliminates the majority of the programming work required to automate and maintain tests long-term.
Continuous Integration/Continuous Delivery (CI/CD)
Continuous integration and continuous deployment merge development with testing, allowing developers to build code collaboratively, submit it to the master branch, and check for issues.
A way of evaluating or cross-checking the code written by developers as the developers need to be at par with each other. The time for peer testing can be mutually decided upon by the developers, which could be a weekly or a fortnightly analysis of their respective codes.
Progressive Web Applications (PWAs)
Web applications that load like regular web pages or websites but can offer the user functionality such as working offline, push notifications, and device hardware access traditionally available only to native applications.
A specification of the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed to achieve a particular software testing objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
A collection of software and test data configured to test a program unit by running it under varying conditions and monitoring its behavior and outputs. It has two main parts: the test execution engine and the test script repository.
A detailed document that outlines the test strategy, testing objectives, resources (manpower, software, hardware) required for testing, test schedule, test estimation, and test deliverables. The test plan serves as a blueprint to conduct software testing activities as a defined process which is minutely monitored and controlled by the test manager.
A structured approach to exploratory testing where the exploration of a product is organized around a specific theme. The theme informs the type of questions that are asked and the type of observations a tester should be making.