Terms related to Foundation Extension - Mobile Application Testing 2019

The unintended termination of the execution of a component or system prior to completion.
The unintended termination of the execution of a component or system prior to completion.
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.
Testing to determine the ease by which users with disabilities can use a component or system.
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.
An approach to testing in which gamification and awards for defects found are used as a motivator.
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 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).
The capability of the software product to enable specified modifications to be implemented.
A type of security attack performed by inserting malicious code at an interface into an application to exploit poor handling of untrusted data.
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.
A test approach in which the test suite comprises all combinations of input values and preconditions.
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 logical expression that can be evaluated as True or False.
The degree to which a component or system can connect to other components or systems.
The degree to which a website or web application can function across different browsers and degrade gracefully when browser features are absent or lacking.
An approach to testing in which testing is distributed to a large group of testers.
A type of testing in which test suites are executed on physical or virtual devices.
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.
A test approach in which the test suite comprises all combinations of input values and preconditions.
A 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.
A test is deemed to fail if its actual result does not match its expected result.
A distinguishing characteristic of a component or system.
A type of testing conducted to evaluate the system behavior under productive connectivity conditions in the field.
A result of an evaluation that identifies some important issue, problem, or opportunity.
A generally recognized rule of thumb that helps to achieve a goal.
An instance of an input.
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.
The number or category assigned to an attribute of an entity by making a measurement.
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.
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 type of testing to ensure that the release is performed correctly and the application can be deployed.
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 type of testing to confirm that sensors can detect nearby objects without physical contact.
The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.
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 facility that provides remote access to a test environment.
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 capability of the software product to be upgraded to accommodate increased loads.
Testing to determine the security of the software product.
A method for measuring and managing session-based testing.
An approach in which test activities are planned as test sessions.
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.
A distinguishing characteristic of a component or system.
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 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.
The capability of the software product to provide an appropriate set of functions for specified tasks and user objectives.
Testing an integrated system to verify that it meets specified requirements.
A set of one or more test cases.
The use of software to perform or support test activities, e.g., test management, test design, test execution and results checking.
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.
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.
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 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 graphical model representing the relationship of the amount of testing per level, with more at the bottom than at the top.
Documentation summarizing test activities and results.
Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders.
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 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.
A set of exploratory tests organized around a special focus.
A test facility in which unintrusive observation of participant reactions and responses to software takes place.
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 type of testing in which a test client is used to switch the user agent string and identify itself as a different client while executing test suites.
Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.