Terms related to Advanced Agile Technical Tester 2019

A collaborative approach to development in which the team and customers are using the customers own domain language to understand their requirements, which forms the basis for testing a component or system.
A statement on the values that underpin Agile software development. The values are: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan.
Testing practice for a project using Agile software development methodologies, incorporating techniques and methods, such as extreme programming (XP), treating development as the customer of testing and emphasizing the test-first design paradigm.
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 basis for testing.
A logical expression that can be evaluated as True or False.
The degree to which the maximum limits of a component or system parameter meet requirements.
Acronym for Computer Aided Software Engineering.
(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, or a proposed change, to a product or service.
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 has a design and/or internal structure that is difficult to understand, maintain and verify.
A logical expression that can be evaluated as True or False.
A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.
The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.
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 software release candidate as rapidly as possible.
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
A software development activity in which a system is compiled and linked daily so that it is consistently available at any time including all the latest changes.
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 human action that produces an incorrect result.
Testing based on the tester's experience, knowledge and intuition.
A test is deemed to fail if its actual result does not match its expected result.
A distinguishing characteristic of a component or system.
A result of an evaluation that identifies some important issue, problem, or opportunity.
A generally recognized rule of thumb that helps to achieve a goal.
An organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions. The IDEAL model is named for the five phases it describes: initiating, diagnosing, establishing, acting, and learning.
A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.
The process of combining components or systems into larger assemblies.
A measurement scale and the method used for measurement.
A diagram arranged around a general theme that represents ideas, tasks, words or other items.
A human action that produces an incorrect result.
Testing based on or involving models.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
A test is deemed to pass if its actual result matches its expected result.
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
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.
The level of (business) importance assigned to an item, e.g., defect.
An unknown underlying cause of one or more incidents.
A set of interrelated activities, which transform inputs into outputs.
A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources.
A set of conventions that govern the interaction of processes, devices, and other components within a system.
Testing that dynamically responds to the system under test and test results being obtained. Typically reactive testing has a reduced planning cycle and the design and implementation test phases are not carried out until the test object is received.
A degradation in the quality of a component or system due to a change.
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.
A factor that could result in future negative consequences.
The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.
A system whose failure or malfunction may result in death or serious injury to people, or loss or severe damage to equipment, or environmental harm.
A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.
The capability of the software product to be upgraded to accommodate increased loads.
A technique to enable virtual delivery of services which are deployed, accessed and managed remotely.
A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.
Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.
A distinguishing characteristic of a component or system.
Documentation that provides a detailed description of a component or system for the purpose of developing and testing it.
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., ISO/IEC standards, IEEE standards, and organizational standards).
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to another.
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances that cause and/or result from a change from one state to another.
The analysis of source code carried out without execution of that software.
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 replaces a called component.
A set of one or more test cases.
A high-level plan to achieve long-term objectives of test automation under given boundary conditions.
An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
A test tool that executes tests against a designated test item and evaluates the outcomes against expected results and postconditions.
A chronological record of relevant details about the execution of tests.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
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 execution.
A chronological record of relevant details about the execution of tests.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
A chronological record of relevant details about the execution of tests.
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 execution.
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 provides other support for the developer, such as debugging capabilities.
All components of a system that provide information and controls for the user to accomplish specific tasks with the system.
Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.
An element of storage in a computer that is accessible by a software program by referring to it by a name.
Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.