1) An external company or individual providing services without being directly involved in the software development process. a) Fault detection b) Third-party c) Failure d) Error 2) Identifying and locating errors in the software that could potentially cause issues during operation. a) Third-party b) Error c) Fault detection d) Test criteria 3) Proactively implementing measures to avoid errors from being introduced into the software in the first place. a) Fault prevention b) Third-party c) Fault d) Evaluation model 4) In software testing, they represent the "expected" behaviour of the software under specific conditions. They can be formal specifications, expert judgment, or historical data. a) Oracles b) Prevention model c) Demonstration model d) Test criteria 5) An anticipated outcome or behavior of the software generated based on the oracle and the software's current state. a) Prevention model b) Destruction model c) Third-party d) Projection 6) A mistake or flaw in the software code that can potentially lead to problems. a) Failure b) Error c) Fault prevention d) Destruction model 7) A defect in the software that causes an unexpected or incorrect behavior when the code is executed. a) Fault b) Prevention model c) Test criteria d) Projection 8) The observable malfunctioning of the software, resulting from a fault. This is the external manifestation of an error or fault. a) Demonstration model b) Fault prevention c) Destruction model d) Failure 9) Specific guidelines or conditions used to design and evaluate software tests, ensuring they cover all desired functionalities and aspects. a) Test criteria b) Fault prevention c) Fault detection d) Evaluation model 10) A fault prevention approach that focuses on avoiding errors by employing techniques like code reviews, static analysis, and coding standards. a) Fault prevention b) Prevention model c) Projection d) Failure 11) A testing approach that evaluates the software across various aspects, including design, implementation, and requirements, to identify potential faults. a) Evaluation model b) Fault c) Test criteria d) Error 12) A testing approach that verifies if the software fulfills its intended purpose and satisfies the specified requirements. a) Projection b) Demonstration model c) Fault d) Error 13) A testing approach that aims at deliberately "breaking" the software by introducing extreme or unexpected inputs to uncover potential weaknesses and ensure it can handle various conditions. It's typically used later in the development stages. a) Test criteria b) Destruction model c) Third-party d) Projection

Software Testing Objectives

Skriv ut
Bädda in

Rankningslista

Visuell stil

Alternativ

Växla mall

Återställ sparas automatiskt: ?