The ISTQB exams are just around the corner and if you pass them all you get your certificate and freedom to practice your new-found knowledge. Looking for revision material for it? The quiz below is perfect for testing your understanding so far. Give it a try and all the best!
Take this ISTQB Foundation Level Quiz! or create online exam.
Schedules and deliverables
Hardware and software
Entry and exit criteria
Types of test case
Introducing mutations
Performance testing
A mutation error
Debugging a program
You have discovered every bug in the program
You have tested every statement, branch, and combination of branches in the program
You have reached the scheduled ship date
You have completed every test in the test plan
Compliance testing
Disaster testing
Verifying compliance to rules
Functional testing
Ease of operations
Use automation tool for testing
Use risk-based analysis to find out which areas need to be tested
Both a and b
None of the above
That you have tested every statement in the program
That you have tested every statement and every branch in the program
That you have tested every IF statement in the program
That you have tested every combination of values of IF statements in the program
Security failures were the result of untested parts of code
The development team achieved complete statement and branch coverage but missed a serious bug in the MASPAR operating system
An error in the code was so obscure that you had to test the function with almost every input value to find its two special-case failures
All the above
Assess development plan and status
Develop the test plan
Test software design
Test software requirement
We can never be certain that the program is bug free
We have no definite stopping point for testing, which makes it easier for some managers to argue for very little testing
We have no easy answer for what testing tasks should always be required because every task takes the time that could be spent on other high importance tasks
All of the above
Functional automation tools
Performance testing tools
Configuration management tools
None of the above
No, the problem is not with testers
No, the software is not ready for production
Both a & b
None of the above
Requires knowledge on the bug fixes and how it affect the system
Includes the area of frequent defects
Includes the area which has undergone many/recent code changes
All of the above
Interaction between html pages
Performance on the client side
Security aspects
All of the above
Use risk based analysis to find out which areas need to be tested
Use automation tool for testing
Both a and b
None of the above
Project Manager
Test Engineer
Test Manager
None of the above
Poor quality software
Poor software and poor testing
Bad luck
Insufficient time for testing
White box
Glass box
Structural
Functional
An error
A fault
A failure
A defect
A mistake
Status accounting of configuration items
Auditing conformance to ISO9001
Identification of test versions
Record of changes to documentation over time
Controlled library access
A dynamic analysis tool
A test execution tool
A debugging tool
A test management tool
A configuration management tool
Wait!
Here's an interesting quiz for you.