Agile testing

The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.

A collaborative approach to development in which the team and customers are using the customers own domain language to understand their requirements, which …

Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance …

The capability of the software product to provide the right or agreed results or effects with the needed degree of precision.

A statement on the values that underpin Agile software development. The values are: individuals and interactions over processes and tools, working software …

A group of software development methodologies based on iterative incremental development, where requirements and solutions evolve through collaboration between …

Testing practice for a project using Agile software development methodologies, incorporating techniques and methods, such as extreme programming (XP), treating …

Simulated or actual operational testing by potential users/customers or an independent test team at the developers' site, but outside the development …

The degree to which users can recognize whether a component or system is appropriate for their needs.

An independent evaluation of software products or processes to ascertain compliance to standards, guidelines, specifications, and/or procedures based on …

The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage.

The response of a component or system to a set of input values and preconditions.

A collaborative approach to development in which the team is focusing on delivering expected behavior of a component or system for the customer, which forms the …

Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers, to determine whether or not a …

Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without …

A black-box test design technique in which test cases are designed based on boundary values.

A logical expression that can be evaluated as True or False.

A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g., an incorrect statement or data …

A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function.

A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.

A set of automated tests which validates the integrity of each new build and verifies its key/core functionality, stability and testability.

The degree to which the maximum limits of a component or system parameter meet requirements.

An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of …

(1) A structured approach to transitioning individuals and organizations from a current state to a desired future state. (2) Controlled way to effect a change, …

A statement of test objectives, and possibly test ideas about how to test. Test charters are used in exploratory testing.

Testing based on an analysis of the internal structure of the component or system.

An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g., …

A standard that describes the characteristics of a design or a design description of data or program components.

The degree to which a component or system can exchange information with other components or systems, and/or perform its required functions while sharing the …

The set of generic and specific conditions, agreed upon with the stakeholders for permitting a process to be officially completed. The purpose of exit criteria …

The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.

A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.

An aggregation of hardware, software or both, that is designated for configuration management and treated as a single entity in the configuration management …

A discipline applying technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a …

Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.

A software development procedure merging, integrating and testing all changes as soon as they are committed within an automated process.

An approach that involves a process of testing early, testing often, test everywhere, and automate to obtain feedback on the business risks associated with a …

A sequence of consecutive edges in a directed graph.

The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test suite.

A representation of dynamic measurements of operational performance for some organization or activity, using metrics represented via metaphors such as visual …

The process of finding, analyzing and removing the causes of failures in software.

A program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches.

The percentage of decision outcomes that have been exercised by a test suite. 100% decision coverage implies both 100% branch coverage and 100% statement …

The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g., …

The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact.

A procedure to derive and/or select test cases targeted at one or more defect types, with tests being developed from what is known about the specific defect …

The set of generic and specific conditions for permitting a process to go forward with a defined task, e.g., test phase. The purpose of entry criteria is to …

Testing that involves the execution of the software of a component or system.

The capability of producing an intended result.

(1) The capability of the software product to provide appropriate performance, relative to the amount of resources used, under stated conditions. (2) The …

A large user story that cannot be delivered as defined within a single iteration or is large enough that it can be split into smaller user stories.

A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle, test cases are …

A human action that produces an incorrect result.

A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a …

The behavior predicted by the specification, or another source, of the component or system under specified conditions.

Testing based on the tester's experience, knowledge and intuition.

An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while …

A software engineering methodology used within Agile software development whereby core practices are programming in pairs, doing extensive code review, unit …

A test is deemed to fail if its actual result does not match its expected result.

Deviation of the component or system from its expected delivery, service or result.

An iterative and incremental software development process driven from a client-valued functionality (feature) perspective. Feature-driven development is mostly …

A result of an evaluation that identifies some important issue, problem, or opportunity.

A black-box test design technique in which test cases are designed to execute valid and invalid state transitions.

A review characterized by documented procedures and requirements, e.g., inspection.

The degree to which the functions facilitate the accomplishment of specified tasks and objectives.

The degree to which a component or system provides functions that meet stated and implied needs when used under specified conditions.

Testing based on an analysis of the specification of the functionality of a component or system.

A generally recognized rule of thumb that helps to achieve a goal.

A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation, …

A development lifecycle where a project is broken into a series of increments, each of which delivers a portion of the functionality in the overall project …

A review not based on a formal (documented) procedure.

Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data.

A variable (whether stored within a component or outside) that is read by a component.

Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.

The capability of the software product to interact with one or more specified components or systems.

A type of software development lifecycle model in which the component or system is developed through a series of repeated cycles.

The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or …

Modification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified …

(1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. (2) The capability of the software …

The number or category assigned to an attribute of an entity by making a measurement.

A measurement scale and the method used for measurement.

Testing based on or involving models.

Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.

A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark), …

A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects).

The consequence/outcome of the execution of a test.

A variable (whether stored within a component or outside) that is written by a component.

An approach in which two team members simultaneously collaborate on testing a work product.

A test is deemed to pass if its actual result matches its expected result.

The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate.

Testing to determine the performance of a software product.

A consensus-based estimation technique, mostly used to estimate effort or relative size of user stories in Agile software development. It is a variation of the …

A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.

Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.

The level of (business) importance assigned to an item, e.g., defect.

A risk directly related to the test object.

A risk related to management and control of the (test) project, e.g., lack of staffing, strict deadlines, changing requirements, etc.

The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.

Part of quality management focused on providing confidence that quality requirements will be fulfilled.

A feature or characteristic that affects an item's quality.

A set of activities designed to evaluate the quality of a component or system.

A product risk related to a quality attribute.

A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases: inception, elaboration, construction and …

Testing that dynamically responds to the behavior of the test object and to test results being obtained.

Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, …

The ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of …

A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in …

A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy …

An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements, e.g., tests that exercise …

An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, …

A factor that could result in future negative consequences.

The process of assessing identified project or product risks to determine their level of risk, typically by estimating their impact and probability of …

The importance of a risk as defined by its characteristics impact and likelihood. The level of risk can be used to determine the intensity of testing to be …

The process of identifying risks using techniques such as brainstorming, checklists and failure history.

The process through which decisions are reached and protective measures are implemented for reducing risks to, or maintaining risks within, specified levels.

An approach to testing to reduce the level of product risks and inform stakeholders of their status, starting in the initial stages of a project. It involves …

The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.

The degree to which a component or system can be adjusted for changing capacity.

An iterative incremental framework for managing projects commonly used with Agile software development.

A technique to enable virtual delivery of services which are deployed, accessed and managed remotely.

A method for measuring and managing session-based testing.

The degree of impact that a defect has on the development or operation of a component or system.

The period of time that begins when a software product is conceived and ends when the software is no longer available for use. The software lifecycle typically …

An entity in a programming language, which is typically the smallest indivisible unit of execution.

A development technique in which the specification is defined by examples.

Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of working or to provide guidelines (e.g., …

Analysis of software development artifacts, e.g., requirements or code, carried out without execution of these software development artifacts. Static analysis …

The analysis of source code carried out without execution of that software.

Testing of a software development artifact, e.g., requirements, design or code, without execution of these artifacts, e.g., reviews or static analysis.

A skeletal or special-purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it. It …

Testing the integration of systems and packages; testing interfaces to external organizations (e.g., Electronic Data Interchange, Internet).

Testing an integrated system to verify that it meets specified requirements.

See test object.

A set of one or more test cases.

The process of analyzing the test basis and defining test objectives.

The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) project's goal and the …

The use of software to perform or support test activities, e.g., test management, test design, test execution and results checking.

A high-level plan to achieve long-term objectives of test automation under given boundary conditions.

All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be …

An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.

A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as …

Procedure used to derive and/or select test cases.

An item or event of a component or system that could be verified by one or more test cases, e.g., a function, transaction, feature, quality attribute, or …

Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.

A type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.

The process of transforming general test objectives into tangible test conditions and test cases.

The calculated approximation of a result related to various aspects of testing (e.g., effort spent, completion date, costs involved, number of test cases, …

The process of running a test on the component or system under test, producing actual result(s).

The use of software, e.g., capture/playback tools, to control the execution of tests, the comparison of actual results to expected results, the setting up of …

A test tool that executes tests against a designated test item and evaluates the outcomes against expected results and postconditions.

A group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are …

A chronological record of relevant details about the execution of tests.

The planning, estimating, monitoring and control of test activities, typically carried out by a test manager.

A tool that provides support to the test management and control part of a test process. It often has several capabilities, such as testware management, …

A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be …

The activity of establishing or updating a test plan.

A sequence of test cases in execution order, and any associated actions that may be required to set up the initial preconditions and any wrap up activities post …

The fundamental test process comprises test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and …

A statement that echoes the Agile manifesto, and defines values for improving the testing process. The values are: flexibility over detailed processes, best …

Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders.

Commonly used to refer to a test procedure specification, especially an automated one.

An uninterrupted period of time spent in executing tests.

A document that consists of a test design specification, test case specification and/or test procedure specification.

A software product that supports one or more test activities, such as planning and control, specification, building initial files and data, test execution and …

A group of test activities aimed at testing a component or system focused on a specific test objective, i.e. functional test, usability test, regression test …

A way of developing software where the test cases are developed, and often automated, before the software is developed to run those test cases.

An approach to software development in which the test cases are designed and implemented before the associated component or system is developed.

The capability of the software product to enable modified software to be tested.

A skilled professional who is involved in the testing of a component or system.

The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and …

A classification model of test types/levels in four quadrants, relating them to two dimensions of test goals: supporting the team vs. critiquing the product, …

The ability to identify related items in documentation and software, such as requirements with associated tests.

A tool that provides an environment for unit or component testing in which a component can be tested in isolation or with suitable stubs and drivers. It also …

The capability of the software to be understood, learned, used and attractive to the user when used under specified conditions.

Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and attractive to the users under specified …

Acceptance testing carried out by future users in a (simulated) operational environment focusing on user requirements and needs.

A person's perceptions and responses resulting from the use or anticipated use of a software product.

All components of a system that provide information and controls for the user to accomplish specific tasks with the system.

A high-level user or business requirement commonly used in Agile software development, typically consisting of one sentence in the everyday or business language …

A black-box test design technique in which test cases are designed based on user stories to verify their correct implementation.

A framework to describe the software development lifecycle activities from requirements specification to maintenance. The V-model illustrates how testing …

Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.

Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.