Terms related to Advanced Technical Test Analyst 2019

The degree to which the actions of an entity can be traced uniquely to that entity.
Testing based on a systematic analysis of e.g., product risks or requirements.
A tool that carries out static analysis.
Repeated action, process, structure or reusable solution that initially appears to be beneficial and is commonly used but is ineffective and/or counterproductive in practice.
Testing performed by submitting commands to the software under test using programming interfaces of the application directly.
A type of interface in which the components or systems involved exchange information in a defined formal structure.
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.
Permission given to a user or process to access resources.
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.
The coverage of combinations of all single condition outcomes within one statement that have been exercised by a test suite.
The coverage of condition outcomes that have been exercised by a test suite.
An abstract representation of calling relationships between subroutines in a program.
The degree to which the maximum limits of a component or system parameter meet requirements.
Acronym for Computer Aided Software Engineering.
The process of confirming that a component, system or person complies with its specified requirements.
A type of security attack performed by inserting malicious code at an interface into an application to exploit poor handling of untrusted data.
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 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.
The simultaneous execution of multiple independent threads by a component or system.
A logical expression that can be evaluated as True or False.
The coverage of combinations of all single condition outcomes within one statement that have been exercised by a test suite.
The coverage of condition outcomes that have been exercised by a test suite.
A white-box test technique in which test cases are designed to exercise single condition outcomes that independently affect a decision outcome.
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.
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.
A vulnerability that allows attackers to inject malicious code into an otherwise benign website.
An abstract representation of the sequence and possible changes of the state of data objects, where the state of an object is any of creation, usage, or destruction.
A white-box test technique in which test cases are designed to execute definition-use pairs of variables.
A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables.
A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables.
A security attack that is intended to overload the system with requests such that legitimate requests cannot be serviced.
Tests aimed at showing that a component or system does not work. Negative testing is related to the tester's attitude rather than a specific test approach or test design technique, e.g., testing with invalid input values or exceptions.
A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.
The process of encoding information so that only authorized parties can retrieve the original information, usually by means of a specific decryption key or process.
An executable statement or process step which defines a point at which a given process is intended to begin.
A human action that produces an incorrect result.
A tool for seeding (i.e., intentionally inserting) faults in a component or system.
The degree to which a component or system can continue normal operation despite the presence of erroneous inputs.
A statement which, when compiled, is translated into object code, and which will be executed procedurally when the program is running and may perform an action on data.
A test is deemed to fail if its actual result does not match its expected result.
Testing by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or corrupted and that any agreed service levels are maintained (e.g., function availability or response times).
The physical or functional manifestation of a failure.
The process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect. Fault injection is intended to mimic failures that might occur in the field.
A tool for seeding (i.e., intentionally inserting) faults in a 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 computational model consisting of a finite number of states and transitions between those states, possibly with accompanying actions.
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 absence of unreasonable risk due to hazards caused by malfunctioning behavior of Electric/Electronic(E/E) - Systems.
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 pointer within a web page that leads to other web pages.
A tool used to check that no broken hyperlinks are present on a web site.
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.
An instance of an input.
Supplied software on any suitable media which leads the installer through the installation procedure.
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.
The process of simulating a defined set of activities at a specified load to be submitted to a component or system.
Documentation defining a designated number of virtual users who process a defined set of transactions in a specified time period that a component or system being tested may experience in production.
Testing to determine the maintainability of a software product.
Testing the changes to an operational system or the impact of a changed environment to an operational system.
Any model used in model-based testing.
The average time between failures of a component or system.
The average time a component or system will take to recover from a failure.
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.
Testing based on or involving models.
The degree to which a component or system can be changed without introducing defects or degrading existing product quality.
A white-box test technique in which test cases are designed to exercise single condition outcomes that independently affect a decision outcome.
A white-box test technique in which test cases are designed to exercise single condition outcomes that independently affect a decision outcome.
The degree to which a system is composed of discrete components such that a change to one component has minimal impact on other components.
The coverage of combinations of all single condition outcomes within one statement that have been exercised by a test suite.
Tests aimed at showing that a component or system does not work. Negative testing is related to the tester's attitude rather than a specific test approach or test design technique, e.g., testing with invalid input values or exceptions.
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.
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
The maximum operating capacity of a component or system.
The degree to which a component or system uses time, resources and capacity when accomplishing its designated functions.
A test tool that generates load for a designated test item and that measures and records its performance during test execution.
A data item that specifies the location of another data item.
Testing to determine the portability of a software product.
A logical expression which evaluates to true or false to direct the execution path.
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.
A series which appears to be random but is in fact generated according to some prearranged sequence.
Testing to determine the recoverability of a software product.
Testing to determine the recoverability of a software product.
A degradation in the quality of a component or system due to a change.
Testing to determine the reliability of a software product.
The process of testing to determine the resource-utilization of a software product.
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.
The absence of unreasonable risk due to hazards caused by malfunctioning behavior of Electric/Electronic(E/E) - Systems.
The capability of the software product to be upgraded to accommodate increased loads.
Testing to determine the scalability of the software product.
An attempt to gain unauthorized access to a component or system, resources, information, or an attempt to compromise system integrity.
A high-level document describing the principles, approach and major objectives of the organization regarding security.
A quality risk related to security.
Testing to determine the security of the software product.
A tool that supports operational security.
Testing to determine the maintainability of a software product.
The degree of impact that a defect has on the development or operation of a component or system.
A programming language/interpreter technique for evaluating compound conditions in which a condition on one side of a logical operator may not be evaluated if the condition on the other side is sufficient to determine the final outcome.
The representation of selected behavioral characteristics of one physical or abstract system by another system.
A device, computer program or system used during testing, which behaves or operates like a given system when provided with a set of controlled inputs.
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).
An entity in a programming language, which is typically the smallest indivisible unit of execution.
A tool that carries out static analysis.
A tool that carries out static analysis.
The process of testing to determine the resource-utilization of a software product.
A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified workloads, or with reduced availability of resources such as access to memory or servers.
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 tool that provides an environment for test automation. It usually includes a test harness and test libraries.
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.
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.
The organizational artifacts needed to perform testing, consisting of test environments, test tools, office environment and procedures.
The data received from an external source by the test object during test execution. The external source can be hardware, software or human.
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.
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.
An uninterrupted period of time spent in executing tests. In exploratory testing, each test session is focused on a charter, but testers can also explore new opportunities or issues during a session. The tester creates and executes on the fly and records their progress.
The degree to which a component or system can perform its required functions within required response times, processing times and throughput rates.
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 pointer that references a location that is out of scope for that pointer or that does not exist.