This test is used to know your preparation level for ISTQB Foundation Exam
D, A, B, C.
A, B, C, D.
D, A, B.
A, B, C.
Open, Assigned, Fixed, Closed
Open, Fixed, Assigned, Closed
Assigned, Open, Closed, Fixed
Assigned, Open, Fixed, Closed
At system and acceptance testing levels only.
At all test levels.
At all levels above integration testing.
At the acceptance testing level only.
Both inspections and walkthroughs are led by the author.
An inspection is led by a moderator and a walkthrough is led by the author.
Both inspections and walkthroughs are led by a trained moderator.
A walkthrough is led by the author. The author is not present during inspections.
Ii, iv.
Ii, iii.
I, iii, iv.
Iii.
Login Browse Basket Checkout Basket Checkout Pay Logout.
Login Browse Basket Checkout Pay Logout.
Login Browse Basket Checkout Basket Logout.
Login Browse Basket Browse Basket Checkout Pay Logout.
23 year old in insurance class A Premium is 90 and excess is 2,500.
51 year old in insurance class C Premium is 70 and excess is 500.
31 year old in insurance class B Premium is 70 and excess is 2,500.
43 year old in insurance class C Premium is 70 and excess is 1,000.
Confirmation testing is testing fixes to a set of defects and Regression testing is testing to establish whether any defects have been introduced as a result of changes.
Confirmation testing is testing to establish whether any defects have been introduced as a result of changes and Regression testing is testing fixes to a set of defects.
Confirmation testing and Regression testing are both testing to establish whether any defects have been introduced as a result of changes.
Confirmation testing and Regression testing are both testing fixes to a set of defects.
The name and/or organisational position of the person raising the problem.
Version of the Software Under Test.
Suggestions as to how to fix the problem.
Actual and expected results.
Ii, iv and v.
Ii, iii and iv.i
I, ii and iv
I, iii and v
15, 19 and 25.
17, 18 and19.
18, 20 and22.
16, 26 and 32
Black Box Techniques.
White Box Techniques
Glass Box Techniques.
Experience Based Techniques.
Preventative tests and reactive tests are designed as early as possible.
Preventative tests are designed early; reactive tests are designed after the software has been produced.
Preventative testing is always analytical; reactive testing is always heuristic.
Preventative tests are designed after the software has been produced; reactive tests are designed early in response to review comments.
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
It is cheaper than designing tests during the test phases.
It helps prevent defects from being introduced into the code.
Tests designed early are more effective than tests designed later.
It saves time during the testing phases when testers are busy.
Impact analysis assesses the effect on the system of a defect found in regression testing.
Impact analysis assesses the effect of a new person joining the regression test team.
Impact analysis assesses whether or not a defect found in regression testing has been fixed correctly.
Impact analysis assesses the effect of a change to the system to determine how much regression testing to do.
5, 6, 20
4, 5, 80
4, 5, 99
1, 20, 100
Scheduling test analysis and design tasks.
Initiating corrective actions.
Monitoring progress and test coverage.
Measuring and analyzing results.
Test case specification.
Test design specification.
Test procedure specification.
Test results.
Supplier issues
Organization factors
Technical issues
Error-prone software delivered
I, ii & iv are true, iii & v are false.
Ii & iii are true, i, iv & v are false.
Iv & v are true, i, ii & iii are false.
I, ii & iii are true iv & v are false.
Requirements
Documentation
Test cases
Improvements suggested by users
Test planning.
Evaluating exit criteria and reporting.
Test closure.
Test control.
A
ABD
ABCD
ACD
I, iii. and iv. are more for developers.
Ii. and iv. are more for developers.
Ii, iii. and iv. are more for developers.
Ii. and iii. are more for developers.
The cost of dealing with an adverse event if it occurs.
The probability that an adverse event will occur.
The amount of testing planned before release of a system.
The likelihood of an adverse event and the impact of the event.
Tool support for performance and monitoring.
Tool support for static testing.
Tool support for test execution and logging.
Tool support for the management of testing and tests.
One more test case will be required for 100 % decision coverage.
Two more test cases will be required for 100 % statement coverage, one of which will be used to provide 100% decision coverage.
None, existing test cases can be used.
One more test case will be required for 100
To define when a test level is complete.
To determine when a test has completed.
To identify when a software system should be retired.
To determine whether a test has passed.
Ii and iv
Ii and iii
I and iv
I and iii
To identify potential application failures by use of a test specification.
To identify defects in any software work product.
To identify spelling mistakes in a requirements specification.
To identify standards inconsistencies in the code.
Measuring and analyzing results.
Reporting discrepancies as incidents.
Identifying test conditions or test requirements.
Assessing if more tests are needed.
Implementation and execution.
Planning and control.
Analysis and design.
Test closure.
3
4
2
1
During test planning.
During test analysis.
During test execution.
When evaluating exit criteria
I, ii, iii.
Ii, iii, iv
I, iii, iv.
I, ii, iv.
1Y, 2Z, 3X, 4W.
1X ,2W, 3Z, 4Y.
1Z, 2X, 3W, 4Y.
1Z, 2Y, 3X, 4W.
SC=1 BC= 2 CC=1 MCC=1
SC=1 BC= 2 CC=1 MCC=8
SC=1 BC= 2 CC=2 MCC=8
SC=1 BC= 1 CC=2 MCC=8
Supporting reviews.
Validating models of the software.
Testing code executed in a special test harness.
Enforcement of coding standards.
Quiz Review Timeline (Updated): Feb 23, 2012 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
ISTQB- All Chapters Exam 17
ISTQB- All Chapters Exam 17 assesses knowledge on maintenance testing triggers, regression testing, impact analysis, risk dimensions, and identification of product and project...
Questions:
40 |
Attempts:
2046 |
Last updated:
Jan 19, 2025
|
|
ISTQB- All Chapters Exam16
ISTQB- All Chapters Exam16 assesses knowledge across various testing techniques like experience-based, error guessing, and exploratory testing. It evaluates understanding of test...
Questions:
40 |
Attempts:
959 |
Last updated:
Mar 22, 2023
|
ISTQB- All Chapters Exam15
ISTQB- All Chapters Exam15 assesses knowledge across various testing protocols and standards, including the handling of test incidents and the importance of testing independence....
Questions:
40 |
Attempts:
868 |
Last updated:
Mar 20, 2023
|
ISTQB Foundation Level Extension - Agile Tester. CTFL-AT: Chapter 2
This quiz assesses knowledge on Agile testing methodologies compared to traditional approaches, focusing on integration, system testing, and development activities in agile...
Questions:
35 |
Attempts:
6289 |
Last updated:
Jan 08, 2025
|
|
ISTQB- All Chapters Exam13
ISTQB- All Chapters Exam13 tests comprehensive knowledge in software testing, covering functional system testing, non-functional testing types, beta testing, static analysis...
Questions:
40 |
Attempts:
1225 |
Last updated:
Jul 04, 2024
|
ISTQB- All Chapters Exam12
This ISTQB- All Chapters Exam12 assesses critical skills for software testers, covering topics like test-driven development, regression testing, and incident management. It...
Questions:
40 |
Attempts:
624 |
Last updated:
Mar 20, 2023
|
Wait!
Here's an interesting quiz for you.