Chapter 1 & 2 Flashcards
(21 cards)
Debugging
The process of finding, analyzing and removing the causes of failures in software.
Defect/Fault
A flaw in a component or system that can cause the component or system to fail to perform it’s 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.
Error/Mistake
A human action that produces an incorrect result.
Exhaustive testing
A test approach in which the test suite comprises all combinations of input values and preconditions
Exit criteria
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 for being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against him and to plan when to stop testing.
Failure
Deviation of the component or system from its expected delivery service or result.
Fault/Defect
A flaw in a component or system that can cause the component or system to fail to perform it’s 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.
Independence of testing
Separation of responsibilities, which encourages the accomplishment of objective testing. Kelly note: Basically this is saying that a programmer should not test their own code. They need someone else that can actually test it that’s not so close to it.
Mistake/Error
A human action that produces an incorrect result.
Product risk
A risk directly related to the test object. See also: risk
Project risk
A risk related to management and control of the test project, e.g. lack of staffing, strict deadlines, changing requirements, etc.
Quality
The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.
Requirement
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 formerly imposed document.
Risk
A factor that could result in future negative consequences; usually expressed as impact and likelihood.
Risk based testing
And 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 in the use of risk levels to guide the test process.
Test basis
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.
Test execution
The process of running a test on the component or system under test, producing actual results
Test log
A chronological record of relevant details about the execution of tests
Test objective
A reason or purpose for designing and executing a test
Testing
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.
Bug
Same as defect. A flaw in a component or system that can cause the component or system do you failed to perform it’s required function e.g. incorrect statement or data definition a defect if encounter during execution. May cause a failure of the component or system
