Terms related to Advanced Test Analyst 2012

A test case without concrete (implementation level) values for input data and expected results. Logical operators are used: instances of the actual values are not yet defined and/or available.
The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity.
Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.
The degree to which a product or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use.
Testing to determine the ease by which users with disabilities can use a component or system.
The capability of the software product to provide the right or agreed results or effects with the needed degree of precision.
Testing to determine the accuracy of a software product.
A scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control script for the test.
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.
The capability of the software product to be adapted for different specified environments without applying actions or means other than those provided for this purpose for the software considered.
The capability of the software product to be diagnosed for deficiencies or causes of failures in the software, or for the parts to be modified to be identified.
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.
The capability of the software product to be attractive to the user.
An independent evaluation of software products or processes to ascertain compliance to standards, guidelines, specifications, and/or procedures based on objective criteria, including documents that specify: the form or content of the products to be produced, the process by which the products shall be produced, and how compliance to standards or guidelines shall be measured.
The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage.
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 reference to its internal structure.
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 reference to its internal structure.
An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge, for example the minimum or maximum value of a range.
A black-box test design technique in which test cases are designed based on boundary values.
The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.
Bug
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 definition. A defect, if encountered during execution, may cause a failure of the component or system.
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.
A test automation approach, where inputs to the test object are recorded during manual testing in order to generate automated test scripts that could be executed later (i.e. replayed).
A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.
A test automation approach, where inputs to the test object are recorded during manual testing in order to generate automated test scripts that could be executed later (i.e. replayed).
A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.
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 defect recurrence will be minimized.
A black-box test design technique in which test cases are designed from cause-effect graphs.
A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects), which can be used to design test cases.
A graphical representation of inputs and/or stimuli (causes) with their associated outputs (effects), which can be used to design test cases.
A black-box test design technique in which test cases are designed from cause-effect graphs.
(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.
The capability of the software product to enable specified modifications to be implemented.
A statement of test objectives, and possibly test ideas about how to test. Test charters are used in exploratory testing.
An experience-based test design technique whereby the experienced tester uses a high-level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.
The coverage of valid sequences of N+1 transitions that have been exercised by a test suite.
A tree showing equivalence partitions hierarchically ordered, which is used to design test cases in the classification tree method.
A black-box test design technique in which test cases, described by means of a classification tree, are designed to execute combinations of representatives of input and/or output domains.
Testing based on an analysis of the internal structure of the component or system.
The capability of the software product to co-exist with other independent software in a common environment sharing common resources.
Testing based on an analysis of the internal structure of the component or system.
A black-box test design technique in which test cases are designed to execute specific combinations of values of several parameters.
A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.
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 is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing.
The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.
The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions.
A minimal software item that can be tested in isolation.
Testing performed to expose defects in the interfaces and interactions between integrated components.
The testing of individual software components.
Two or more single conditions joined by means of a logical operator.
A test case with concrete (implementation level) values for input data and expected results. Logical operators from high-level test cases are replaced by actual values that correspond to the objectives of the logical operators.
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 discipline applying technical and administrative direction and surveillance to identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements.
Testing to determine the portability of a software product.
Users, tasks, equipment (hardware, software and materials), and the physical and social environments in which a software product is used.
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 degree, expressed as a percentage, to which a specified coverage item has been exercised by a test suite.
A program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches.
A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects), which can be used to design test cases.
A black-box test design technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table.
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 definition. A defect, if encountered during execution, may cause a failure of the component or system.
The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact.
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 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 type.
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 type.
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 is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing.
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 prevent a task from starting which would entail more (wasted) effort compared to the effort needed to remove the failed entry criteria.
Any event occurring that requires investigation.
A black-box test design technique that is used to identify efficient and effective test cases when multiple variables can or should be tested together. It builds on and generalizes equivalence partitioning and boundary values analysis.
A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.
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 capability of a process to produce the intended outcome, relative to the amount of resources used.
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 prevent a task from starting which would entail more (wasted) effort compared to the effort needed to remove the failed entry criteria.
A portion of an input or output domain for which the behavior of a component or system is assumed to be the same, based on the specification.
A portion of an input or output domain for which the behavior of a component or system is assumed to be the same, based on the specification.
A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle, test cases are designed to cover each partition at least once.
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 result of errors made, and to design tests specifically to expose them.
The degree to which a component or system can continue normal operation despite the presence of erroneous inputs.
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 is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing.
The behavior predicted by the specification, or another source, of the component or system under specified conditions.
The behavior predicted by the specification, or another source, of the component or system under specified conditions.
Procedure to derive and/or select test cases based on the tester's experience, knowledge and intuition.
Procedure to derive and/or select test cases based on the tester's experience, knowledge and intuition.
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 testing to design new and better tests.
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.
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 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 definition. A defect, if encountered during execution, may cause a failure of the component or system.
A distinguishing characteristic of a component or system.
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.
Testing based on an analysis of the specification of the functionality of a component or system.
The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions.
Testing based on an analysis of the internal structure of the component or system.
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.
A usability review technique that targets usability problems in the user interface or user interface design. With this technique, the reviewers examine the interface and judge its compliance with recognized usability principles (the "heuristics").
A test case without concrete (implementation level) values for input data and expected results. Logical operators are used: instances of the actual values are not yet defined and/or available.
Any event occurring that requires investigation.
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 requirements. The requirements are prioritized and delivered in priority order in the appropriate increment. In some (but not all) versions of this lifecycle model, each subproject follows a mini V-model with its own design, coding and testing phases.
A measure that can be used to estimate or predict another measure.
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 by people who are co-located with the project team but are not fellow employees.
A type of peer review that relies on visual examination of documents to detect defects, e.g., violations of development standards and non-conformance to higher level documentation. The most formal review technique and therefore always based on a documented procedure.
The capability of the software product to be installed in a specified environment.
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.
Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.
A type of integration testing performed to verify integration between components or systems.
The capability of the software product to interact with one or more specified components or systems.
Testing to determine the interoperability of a software product.
A scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control script for the test.
The capability of the software product to enable the user to learn its application.
A test plan that typically addresses one test level.
A partitioning of the life of a product or project into phases.
Testing performed to expose defects in the interfaces and interactions between integrated components.
Testing based on an analysis of the internal structure of the component or system.
Testing based on an analysis of the internal structure of the component or system.
A test case without concrete (implementation level) values for input data and expected results. Logical operators are used: instances of the actual values are not yet defined and/or available.
A test case with concrete (implementation level) values for input data and expected results. Logical operators from high-level test cases are replaced by actual values that correspond to the objectives of the logical operators.
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 adapted to a changed environment.
Modification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment.
Testing the changes to an operational system or the impact of a changed environment to an operational system.
(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 product to avoid failure as a result of defects in the software.
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 point in time in a project at which defined (intermediate) deliverables and results should be ready.
A human action that produces an incorrect result.
A minimal software item that can be tested in isolation.
The testing of individual software 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.
Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.
A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.
The capability of the software product to enable the user to operate and control it.
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), other software, a user manual, or an individual's specialized knowledge, but should not be the code.
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).
A 2-dimensional array constructed with special mathematical properties, such that choosing any two columns in the array provides every pair combination of each number in the array.
A systematic way of testing all-pair combinations of variables using orthogonal arrays. It significantly reduces the number of all combinations of variables to test all pair combinations.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
A variable (whether stored within a component or outside) that is written by a component.
A black-box test design technique in which test cases are designed to execute all possible discrete combinations of each pair of input parameters.
A black-box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle, test cases are designed to cover each partition at least once.
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 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.
The percentage of defects that are removed in the same phase of the software lifecycle in which they were introduced.
The ease with which the software product can be transferred from one hardware or software environment to another.
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.
Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.
The behavior predicted by the specification, or another source, of the component or system under specified conditions.
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.
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 risk directly related to the test object.
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 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.
A feature or characteristic that affects an item's quality.
A black-box test technique in which test cases are designed by generating random independent inputs to match an operational profile.
A test automation approach, where inputs to the test object are recorded during manual testing in order to generate automated test scripts that could be executed later (i.e. replayed).
A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.
The capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure.
Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of the changes made. It is performed when the software or its environment is changed.
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 operations.
The capability of the software product to be used in place of another specified software product for the same purpose in the same environment.
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 a contract, standard, specification, or other formally imposed document.
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.
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 specific functions or probe non-functional attributes such as reliability or usability.
The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions.
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.
An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, informal review, technical review, inspection, and walkthrough.
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 occurrence (likelihood).
The process of identifying and subsequently analyzing the identified project or product risk to determine its level of risk, typically by assigning likelihood and impact ratings.
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 performed. A risk level can be expressed either qualitatively (e.g., high, medium, low) or quantitatively.
The process of identifying risks using techniques such as brainstorming, checklists and failure history.
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 performed. A risk level can be expressed either qualitatively (e.g., high, medium, low) or quantitatively.
Systematic application of procedures and practices to the tasks of identifying, analyzing, prioritizing, and controlling risk.
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 identification of product risks and the use of risk levels to guide the test process.
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.
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 defect recurrence will be minimized.
A test suite that covers the main functionality of a component or system to determine whether it works properly before planned testing begins.
A black-box test design technique in which test cases are designed to execute scenarios of use cases.
Testing (manual or automated) that follows a test script.
An iterative incremental framework for managing projects commonly used with Agile software development.
Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data.
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.
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 includes a concept phase, requirements phase, design phase, implementation phase, test phase, installation and checkout phase, operation and maintenance phase, and sometimes, retirement phase. Note these phases may overlap or be performed iteratively.
A feature or characteristic that affects an item's quality.
A feature or characteristic that affects an item's quality.
Any event occurring that requires investigation.
A questionnaire-based usability test technique for measuring software quality from the end user's point of view.
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.
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 reference to its internal structure.
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 reference to its internal structure.
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 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 black-box test design technique in which test cases are designed to execute valid and invalid state transitions.
An entity in a programming language, which is typically the smallest indivisible unit of execution.
Analysis of software development artifacts, e.g., requirements or code, carried out without execution of these software development artifacts. Static analysis is usually carried out by means of a supporting tool.
Testing of a software development artifact, e.g., requirements, design or code, without execution of these artifacts, e.g., reviews or static analysis.
The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions.
Testing based on an analysis of the internal structure of the component or system.
Testing based on an analysis of the internal structure of the component or system.
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.
The capability of the software product to provide an appropriate set of functions for specified tasks and user objectives.
Testing to determine the suitability of a software product.
A collection of components organized to accomplish a specific function or set of functions.
Testing an integrated system to verify that it meets specified requirements.
See test object.
A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken.
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 risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed.
The use of software to perform or support test activities, e.g., test management, test design, test execution and results checking.
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 amended only by way of formal amendment procedure, then the test basis is called a frozen test basis.
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 to exercise a particular program path or to verify compliance with a specific requirement.
Procedure used to derive and/or select test cases.
A document specifying a set of test cases (objective, inputs, test actions, expected results, and execution preconditions) for a test item.
A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one.
A statement of test objectives, and possibly test ideas about how to test. Test charters are used in exploratory testing.
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.
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 is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing.
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 structural element.
A test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned.
The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test suite.
Execution of the test process against a single identifiable release of the test object.
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.
Procedure used to derive and/or select test cases.
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.
A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.
An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
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 test preconditions, and other test control and reporting functions.
A scheme for the execution of test procedures. Note: The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed.
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 process of developing and prioritizing test procedures, creating test data and, optionally, preparing test harnesses and writing automated test scripts.
Any event occurring that requires investigation.
The organizational artifacts needed to perform testing, consisting of test environments, test tools, office environment and procedures.
The individual element to be tested. There usually is one test object and many test items.
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 component test, integration test, system test and acceptance test.
The process of recording information about tests executed into a test log.
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, scheduling of tests, the logging of results, progress tracking, incident management and test reporting.
The person responsible for project management of testing activities and resources, and evaluation of a test object. The individual who directs, controls, administers, plans and regulates the evaluation of a test object.
A model describing testware that is used for testing a component or a system under test.
A test management task that deals with the activities related to periodically checking the status of a test project. Reports are prepared that compare the actuals to that which was planned.
The component or system to be tested.
A reason or purpose for designing and executing a test.
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), other software, a user manual, or an individual's specialized knowledge, but should not be the code.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process.
The activity of establishing or updating a test plan.
A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script.
The fundamental test process comprises test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and reporting, and test closure activities.
A document summarizing testing activities and results, produced at regular intervals, to report progress of testing activities against a baseline (such as the original test plan) and to communicate risks and alternatives requiring a decision to management.
The process of recording information about tests executed into a test log.
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 structural element.
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 document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script.
A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one.
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 structural element.
A document that consists of a test design specification, test case specification and/or test procedure specification.
Procedure used to derive and/or select test cases.
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 component test, integration test, system test and acceptance test.
A document summarizing testing activities and results, produced at regular intervals, to report progress of testing activities against a baseline (such as the original test plan) and to communicate risks and alternatives requiring a decision to management.
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).
A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one.
A software product that supports one or more test activities, such as planning and control, specification, building initial files and data, test execution and test analysis.
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 etc. A test type may take place on one or more test levels or test phases.
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 related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set-up and clear-up procedures, files, databases, environment, and any additional software or utilities used in testing.
The ability to identify related items in documentation and software, such as requirements with associated tests.
The capability of the software product to enable the user to understand whether the software is suitable, and how it can be used for particular tasks and conditions of use.
A minimal software item that can be tested in isolation.
The testing of individual software components.
The capability of the software to be understood, learned, used and attractive to the user when used under specified conditions.
A requirement on the usability of a component or system.
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 conditions.
A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an actor can be a user or anything that can exchange information with the system.
A black-box test design technique in which test cases are designed to execute scenarios of use cases.
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 black-box test design technique in which test cases are designed to execute scenarios of use cases.
A high-level user or business requirement commonly used in Agile software development, typically consisting of one sentence in the everyday or business language capturing what functionality a user needs and the reason behind this, any non-functional criteria, and also includes acceptance criteria.
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 activities can be integrated into each phase of the software development lifecycle.
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 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.
A questionnaire-based usability test technique for measuring web site software quality from the end user's point of view.
Testing based on an analysis of the internal structure of the component or system.