This quiz consists of questions from previous question papers and sample question papers.
The quiz has 20 questions and the time allocated is 30 minutes. (In ISTQB exam you need to answer 40 question in 60 min)
Each correctly answered question is worth one point.
No Negative marking.
ALL THE BEST!
Defect
Error
Incident
Mistake
Rate this question:
Identifying the cause of a defect, repairing the code and checking the fix is correct.
Checking that a previously reported defect has been corrected.
Testing/checking whether the software performs correctly.
Checking that no unintended consequences have occurred as a result of a fix.
Rate this question:
Exhaustive testing is impossible
Pesticide paradox
Defect clustering
Absence-of-errors fallacy
Rate this question:
To build confidence in the application.
To detect bugs in the application
To gather evidence for a lawsuit
To train the users
Rate this question:
Negative consequences that could occur.
Negative consequences that will occur.
Negative consequences for the test object.
Negative consequences that have occurred.
Rate this question:
I,ii are true and iii,iv are false
I,,iv are true and ii is false
I,ii,iii are true and iv is false
Ii,iii,iv are true and i is false
Rate this question:
Supportability
Maintainability
Usability
Functionality
Rate this question:
As soon as possible in the development life cycle.
When the requirements have been formally documented .
During the design stage
During the stakeholder meeting
Rate this question:
Tests designed by someone from a different company; tests designed by someone from a different department within the company; tests designed by another member of the development team.
Tests designed by the author; tests designed by another member of the development team; tests designed by someone from a different company.
Tests designed by someone from a different department within the company; tests designed by the author; tests designed by someone from a different company.
Tests designed by someone from a different department within the company; tests designed by someone from a different company; tests designed by the author.
Rate this question:
(i), (iii) and (iv) aid, (ii) and (v) hinder.
(i), (ii) and (iii) aid, (iv) and (v) hinder.
(iii), (iv) and (v) aid, (i) and (ii) hinder.
(ii), (iii) and (iv) aid, (i) and (v) hinder.
Rate this question:
Types of test cases
Hardware and software
Entry and exit criteria
Schedules and deliverables
Rate this question:
Defect clustering
Component testing
Pesticide Paradox
Early testing
Rate this question:
(i) and (iii) are part of analysis and design, (ii), (iv) and (v) are part of test implementation and execution.
(i) and (ii) are part of analysis and design, (iii), (iv) and (v) are part of test implementation and execution.
(i) and (v) are part of analysis and design, (ii), (iii) and (iv) are part of test implementation and execution.
(i) and (iv) are part of analysis and design, (ii), (iii) and (v) are part of test implementation and execution.
Rate this question:
Test Analysis and Design
Test Planning and control
Test Implementation and execution
Evaluating exit criteria and reporting
Rate this question:
Gaining confidence about the level of quality and providing information
Clear test objectives determine testers effectiveness
Blindness to one's own errors
Courteous communication and feedback on defects
Rate this question:
When there is enough information for sponsors to make an informed decision about release.
When time and budget are exhausted.
When there are no remaining high priority defects outstanding.
When every data combination has been exercised successfully.
Rate this question:
Test Implementation and Execution
Test Planning and design
Evaluating Entry criteria and reporting
Test design and Implementation
Rate this question:
The root cause
The error
The defect
The Failure
Rate this question:
An item or event of a component or system that could be verified by one or more test cases
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 formally imposed document
An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements.
A set of input values, execution preconditions, expected results and execution post conditions.
Rate this question:
Ed Kit principle
Bill hetzel principle
IEEE 829
IEEE 8295
Rate this question:
Quiz Review Timeline (Updated): Oct 6, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.