Terms related to Foundation Extension - Performance Testing 2018

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 capability of the software product to provide the right or agreed results or effects with the needed degree of precision.
The behavior produced/observed when a component or system is tested.
The behavior produced/observed when a component or system is tested.
A type of interface in which the components or systems involved exchange information in a defined formal structure.
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.
Acronym for Computer Aided Software Engineering.
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.
CLI
Acronym for Command-Line Interface.
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 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 capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions.
Testing performed to expose defects in the interfaces and interactions between integrated components.
The simultaneous execution of multiple independent threads by a component or system.
A logical expression that can be evaluated as True or False.
The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.
A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
An approach to testing in which testing is distributed to a large group of testers.
A representation of dynamic measurements of operational performance for some organization or activity, using metrics represented via metaphors such as visual dials, counters, and other devices resembling those on the dashboard of an automobile, so that the effects of events or activities can be easily understood and related to operational goals.
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 security attack that is intended to overload the system with requests such that legitimate requests cannot be serviced.
Testing that involves the execution of the software of a component or system.
Testing to determine the stability of a system under a significant load over a significant period of time within the system's operational context.
A human action that produces an incorrect result.
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 distinguishing characteristic of a component or system.
A result of an evaluation that identifies some important issue, problem, or opportunity.
A component or set of components that controls incoming and outgoing network traffic based on predetermined security rules.
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.
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.
The process of combining components or systems into larger assemblies.
A test plan that typically addresses one test level.
Testing performed to expose defects in the interfaces and interactions between integrated components.
The process of simulating a defined set of activities at a specified load to be submitted to a component or system.
The control and execution of load generation, and performance monitoring and reporting of the 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.
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 memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing the program and/or other concurrent processes to fail due to lack of memory.
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.
Multiple heterogeneous, distributed systems that are embedded in networks at multiple levels and in multiple interconnected domains, addressing large-scale inter-disciplinary common problems and purposes, usually without a common management structure.
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.
Hardware and software products installed at users' or customers' sites where the component or system under test will be used. The software may include operating systems, database management systems, and other applications.
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.
Testing to determine the performance of a software product.
A test tool that generates load for a designated test item and that measures and records its performance during test execution.
An unknown underlying cause of one or more incidents.
A set of interrelated activities, which transform inputs into outputs.
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.
The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.
Part of quality management focused on providing confidence that quality requirements will be fulfilled.
A set of activities designed to evaluate the quality of a component or system.
A degradation in the quality of a component or system due to a change.
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 factor that could result in future negative consequences.
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.
The capability of the software product to be upgraded to accommodate increased loads.
Testing to determine the scalability of the software product.
A type of development lifecycle model in which a complete system is developed in a linear way of several discrete and successive phases with no overlap between them.
A technique to enable virtual delivery of services which are deployed, accessed and managed remotely.
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.
Testing to determine the ability of a system to recover from sudden bursts of peak loads and return to a steady state.
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.
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 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.
The capability of the software product to provide an appropriate set of functions for specified tasks and user objectives.
Multiple heterogeneous, distributed systems that are embedded in networks at multiple levels and in multiple interconnected domains, addressing large-scale inter-disciplinary common problems and purposes, usually without a common management structure.
Testing an integrated system to verify that it meets specified requirements.
The amount of data passing through a component or system in a given time period.
A set of one or more test cases.
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.
The activity that makes test assets available for later use, leaves test environments in a satisfactory condition and communicates the results of testing to relevant stakeholders.
Execution of the test process against a single identifiable release of the test object.
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).
A test tool that executes tests against a designated test item and evaluates the outcomes against expected results and postconditions.
A test environment comprised of stubs and drivers needed to execute a test.
A chronological record of relevant details about the execution of tests.
The component or system to be tested.
A reason or purpose for designing and executing a test.
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 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.
Execution of a test on a specific version of the test object.
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 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 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.
The amount of time required by a user to determine and execute the next action in a sequence of actions.
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 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.
All components of a system that provide information and controls for the user to accomplish specific tasks with the system.
A high-level user or business requirement commonly used in Agile software development, typically consisting of one sentence in the everyday or business language capturing what functionality a user needs and the reason behind this, any non-functional criteria, and also includes acceptance criteria.
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.