Terms related to Advanced Test Analyst 2019

Testing to determine the ease by which users with disabilities can use a component or system.
The degree to which the actions of an entity can be traced uniquely to that entity.
User or any other person or system that interacts with the test object in a specific way.
The behavior produced/observed when a component or system is tested.
The behavior produced/observed when a component or system is tested.
Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc., or from someone's perception or experience. Anomalies may be found during, but not limited to, reviewing, testing, analysis, compilation, or use of software products or applicable documentation.
Testing performed by submitting commands to the software under test using programming interfaces of the application directly.
The degree to which users can recognize whether a component or system is appropriate for their needs.
The degree to which the identity of a subject or resource can be proved to be the one claimed.
The response of a component or system to a set of input values and preconditions.
A logical expression that can be evaluated as True or False.
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.
Acronym for Computer Aided Software Engineering.
A graphical representation of inputs and/or stimuli (causes) with their associated outputs (effects), which can be used to design test cases.
(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 review technique guided by a list of questions or required attributes.
The coverage of valid sequences of N+1 transitions that have been exercised by a test suite.
A black-box test technique in which test cases are designed using a classification tree.
A decision table in which combinations of inputs that are impossible or lead to the same outputs are merged into one column (rule), by setting the conditions that do not influence the outputs to don't care.
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 same hardware or software environment.
The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.
Two or more single conditions joined by means of a logical operator.
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 degree to which a component or system ensures that data are accessible only to those authorized to have access.
The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.
Testing to determine the portability of a software product.
The degree to which a component or system can connect to other components or systems.
Users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a software product is used.
A software development procedure merging, integrating and testing all changes as soon as they are committed within an automated process.
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal failure costs and external failure costs.
The protection of personally identifiable information or otherwise sensitive information from undesired disclosure.
A test technique in which test cases are developed from what is known about a specific defect type.
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.
The physical or functional manifestation of a failure.
A test result in which a defect is reported although no such defect actually exists in the test object.
A test result which fails to identify the presence of a defect that is actually present in the test object.
A test result which fails to identify the presence of a defect that is actually present in the test object.
A test result in which a defect is reported although no such defect actually exists in the test object.
A distinguishing characteristic of a component or system.
A result of an evaluation that identifies some important issue, problem, or opportunity.
The degree to which the functions facilitate the accomplishment of specified tasks and objectives.
The degree to which the set of functions covers all the specified tasks and user objectives.
The degree to which a component or system provides the correct results with the needed degree of precision.
An integration approach that combines the components or systems for the purpose of getting a basic functionality working early.
The degree to which a component or system provides functions that meet stated and implied needs when used under specified conditions.
A type of interface that allows users to interact with a component or system through graphical icons and visual indicators.
A generally recognized rule of thumb that helps to achieve a goal.
An approach to design that aims to make software products more usable by focusing on the use of the software products and applying human factors, ergonomics, and usability knowledge and techniques.
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.
Testing performed by people who are co-located with the project team but are not fellow employees.
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.
The degree to which a component or system allows only authorized access and modification to a component, a system or data.
A test plan that typically addresses one test level.
Testing the changes to an operational system or the impact of a changed environment to an operational system.
The number or category assigned to an attribute of an entity by making a measurement.
The process of assigning a number or category to an entity to describe an attribute of that entity.
A measurement scale and the method used for measurement.
A human action that produces an incorrect result.
The degree to which a component or system can be changed without introducing defects or degrading existing product quality.
The degree to which a system is composed of discrete components such that a change to one component has minimal impact on other components.
Two or more single conditions joined by means of a logical operator.
The coverage of valid sequences of N+1 transitions that have been exercised by a test suite.
The degree to which actions or events can be proven to have taken place, so that the actions or events cannot be repudiated later.
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.
Decision rules used to determine whether a test item has passed or failed.
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
The degree to which a component or system uses time, resources and capacity when accomplishing its designated functions.
Testing to determine the portability of a software product.
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.
A systematic approach to risk-based testing that employs product risk identification and analysis to create a product risk matrix based on likelihood and impact. Term is derived from Product RISk MAnagement.
An unknown underlying cause of one or more incidents.
A set of interrelated activities, which transform inputs into outputs.
A program of activities designed to improve the performance and maturity of the organization's processes, and the result of such a program.
A framework in which processes of the same nature are classified into an overall model.
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.
A black-box test technique in which test cases are designed by generating random independent inputs to match an operational profile.
A degradation in the quality of a component or system due to a change.
A tool that supports the recording of requirements, requirements attributes (e.g., priority, knowledge responsible) and annotation, and facilitates traceability through layers of requirements and requirements change management. Some requirements management tools also provide facilities for static analysis, such as consistency checking and violations to pre-defined requirements rules.
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 degree to which a work product can be used in more than one system, or in building other work products.
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 source of a defect such that if it is removed, the occurrence of the defect type is decreased or removed.
A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.
Testing (manual or automated) that follows a test script.
An iterative incremental framework for managing projects commonly used with Agile software development.
The degree of impact that a defect has on the development or operation of a component or system.
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.
The activities performed at each stage in software development, and how they relate to one another logically and chronologically.
A distinguishing characteristic of a component or system.
An entity in a programming language, which is typically the smallest indivisible unit of execution.
Documentation that provides a detailed description of a component or system for the purpose of developing and testing it.
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 grid showing the resulting transitions for each state combined with each possible event, showing both valid and invalid transitions.
A transition between two states of a component or system.
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.
An entity in a programming language, which is typically the smallest indivisible unit of execution.
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 person who is responsible for the design, implementation and maintenance of a test automation architecture as well as the technical evolution of the resulting test automation solution.
A realization/implementation of a test automation architecture, i.e., a combination of components implementing a specific test automation assignment. The components may include commercial off-the-shelf test tools, test automation frameworks, as well as test hardware.
An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
During the test closure phase of a test process data is collected from completed activities to consolidate experience, testware, facts and numbers. The test closure phase consists of finalizing and archiving the testware and evaluating the test process, including preparation of a test evaluation report.
Execution of the test process against a single identifiable release of the test object.
The activity to select data from existing databases or create, generate, manipulate and edit data for testing.
A type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.
A tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE tool repository, e.g., requirements management tool, from specified test conditions held in the tool itself, or from code.
An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
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 test preconditions, and other test control and reporting functions.
A test tool that executes tests against a designated test item and evaluates the outcomes against expected results and postconditions.
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 organizational artifacts needed to perform testing, consisting of test environments, test tools, office environment and procedures.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
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 execution.
A program of activities designed to improve the performance and maturity of the organization's test processes and the results of such a program.
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 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.
The degree to which a component or system can perform its required functions within required response times, processing times and throughput rates.
A process through which information about the usability of a system is gathered in order to improve the system (known as formative evaluation) or to assess the merit or worth of a system (known as summative evaluation).
A test facility in which unintrusive observation of participant reactions and responses to software takes place.
A requirement on the usability of a component or system.
The degree to which a component or system protects users against making errors.
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.
The degree to which a user interface enables pleasing and satisfying interaction for the user.
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.
A simulation of activities performed according to a user operational profile.
A part of a series of web accessibility guidelines published by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C), the main international standards organization for the internet. They consist of a set of guidelines for making content accessible, primarily for people with disabilities.