Testing 101 Crossword

Simulated or actual operational testing conducted at an external site, by roles outside the development organization
Testing, either functional or non-functional, without reference to the internal structure of the component or system.
An imperfection or deficiency in a work product where it does not meet its requirements or specifications.
The set of conditions for officially completing a defined task.
An event in which a component or system does not perform a required function within specified limits
An attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints).
Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.
Testing by means of a random selection from a large range of inputs and by randomly pushing buttons, ignorant of how the product is being used.
A person's perceptions and responses resulting from the use or anticipated use of a software product.
A person's perceptions and responses resulting from the use or anticipated use of a software product.
captures all requirements proposed by the client or development team and their traceability in a single document delivered at the conclusion of the life-cycle. In other words, it is a document that maps and traces user requirement with test cases.
captures all requirements proposed by the client or development team and their traceability in a single document delivered at the conclusion of the life-cycle. In other words, it is a document that maps and traces user requirement with test cases.
Documentation describing the test objectives to be achieved and the means and the schedule for achieving them, organized to coordinate testing activities.
Documentation describing the test objectives to be achieved and the means and the schedule for achieving them, organized to coordinate testing activities.
The degree of impact that a defect has on the development or operation of a component or system.
also known as “Build Verification Testing”, is a type of software testing that comprises of a non-exhaustive set of tests that aim at ensuring that the most important functions work. The result of this testing is used to decide if a build is stable enough to proceed with further testing.
Testing of a previously tested component or system following modification to ensure that defects have not been introduced or have been uncovered in unchanged areas of the software, as a result of the changes made.