ISTQB Foundation Sample Question Paper No. 2 assesses key competencies in software testing, covering topics like test failures, regression testing, and test plan standards. It is designed to prepare learners for ISTQB certification, enhancing their understanding of testing principles and practices.
Every week
After the software has changed
As often as possible
When the environment has changed
When the project manager says
Rate this question:
Test items
Test deliverables
Test tasks
Test environment
Test specification
Rate this question:
All the planned tests have been run
Time has run out
All faults have been fixed correctly
All the planned tests have been run and all faults have been fixed correctly
It depends on the risks for the system being tested
Rate this question:
1000, 5000, 99999
9999, 50000, 100000
10000, 50000, 99999
10000, 99999
9999, 10000, 50000, 99999, 10000
Rate this question:
I, iii & iv are true. Ii & v are false
Iii is true, I, ii, iv & v are false
Iii & iv are true. i, ii & v are false
I, iii, iv & v are true, ii us false
I & iii are true, ii, iv & v are false
Rate this question:
Testing to see where the system does not function properly
Testing quality attributes of the system including performance and usability
Testing a system feature using only the software required for that action
Testing a system feature using only the software required for that function
Testing for functions that should not exist
Rate this question:
Status accounting of configuration items
Auditing conformance to ISO9001
Identification of test versions
Record of changes to documentation over time
Controlled library access
Rate this question:
To ensure that all of the small modules are tested adequately
To ensure that the system interfaces to other systems and networks
To specify which modules to combine when and how many at once
To ensure that the integration testing can be performed by a small team
To specify how the software should be divided into modules
Rate this question:
To know when a specific test has finished its execution
To ensure that the test case specification is complete
To set the criteria used in generating test inputs
To know when test planning is complete
To plan when to stop testing
Rate this question:
Ii and v are true, I, iii and iv are false
I and v are true, ii, iii and iv are false
I, iv and v are true, ii and iii are false
I and ii are true, iii, iv and v are false
I is true, ii, iii, iv and v are false
Rate this question:
1 test for statement coverage, 3 for branch coverage
1 test for statement coverage, 2 for branch coverage
1 test for statement coverage, 1 for branch coverage
2 tests for statement coverage, 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
Rate this question:
1 test for statement coverage, 1 for branch coverage
1 test for statement coverage, 2 for branch coverage
1 test for statement coverage. 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
2 tests for statement coverage, 3 for branch coverage
Rate this question:
1 test for statement coverage, 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
2 tests for statement coverage. 3 for branch coverage
3 tests for statement coverage, 3 for branch coverage
3 tests for statement coverage, 2 for branch coverage
Rate this question:
SC = 1 and DC = 1
SC = 1 and DC = 2
SC = 1 and DC = 3
SC = 2 and DC = 2
SC = 2 and DC = 3
Rate this question:
Attend a tool exhibition
Invite a vendor to give a demo
Analyse your needs and requirements
Find out what your budget would be for the tool
Search the internet
Rate this question:
A small team to establish the best way to use the tool
Everyone who may eventually have some use for the tool
The independent testing team
The managers to see what projects it should be used in
The vendor contractor to write the initial scripts
Rate this question:
The use of a variable before it has been defined
Unreachable (“dead”) code
Whether the value stored in a variable is correct
The re-definition of a variable before it has been used
Array bound violations
Rate this question:
Equivalence partitioning
State transition testing
LCSAJ
Syntax testing
Boundary value analysis
Rate this question:
Performed by customers at their own site
Performed by customers at their software developer’s site
Performed by an independent test team
Useful to test bespoke software
Performed as early as possible in the lifecycle
Rate this question:
Developers would typically use i, iv and vi; test team ii, iii and v
Developers would typically use i and iv; test team ii, iii, v and vi
Developers would typically use i, ii, iii and iv; test team v and vi
Developers would typically use ii, iv and vi; test team I, ii and v
Developers would typically use i, iii, iv and v; test team ii and vi
Rate this question:
Finding faults in the system
Ensuring that the system is acceptable to all users
Testing the system with other systems
Testing for a business perspective
Testing by an independent test team
Rate this question:
Black box design techniques all have an associated measurement technique
White box design techniques all have an associated measurement technique
Cyclomatic complexity is not a test measurement technique
Black box measurement techniques all have an associated test design technique
White box measurement techniques all have an associated test design technique
Rate this question:
Inspection is the most formal review process
Inspections should be led by a trained leader
Managers can perform inspections on management documents
Inspection is appropriate even when there are no written documents
Inspection compares documents with predecessor (source) documents
Rate this question:
Generating expected outputs
Replaying inputs according to a programmed script
Comparison of expected outcomes with actual outcomes
Recording test inputs
Reading test values from a data file
Rate this question:
Re-testing is running a test again; regression testing looks for unexpected side effects
Re-testing looks for unexpected side effects; regression testing is repeating those tests
Re-testing is done after faults are fixed; regression testing is done earlier
Re-testing uses different environments, regression testing uses the same environment
Re-testing is done by developers, regression testing is done by independent testers
Rate this question:
Only important in system testing
Only used in component testing
Never specified in advance
Most useful when specified in advance
Derived from the code
Rate this question:
Report on deviations from the project plan
Sign the system off for release
Re-allocate resource to meet original plans
Raise incidents on faults that they have found
Provide information for risk analysis and quality improvement
Rate this question:
Code reviews
Code inspections
A coverage tool
A test management tool
A static analysis tool
Rate this question:
A dynamic analysis tool
A test execution tool
A debugging tool
A test management tool
A configuration management tool
Rate this question:
How to fix the fault
How to reproduce the fault
Test environment details
Severity, priority
The actual and expected outcomes
Rate this question:
S = 4, t = 3, u = 2 and 5, v = 1
S = 4 and 5, t = 3, u = 2, v = 1
S = 1 and 5, t = 3, u = 2, v = 4
S = 5, t = 4, u = 3, v = 1 and 2
S = 4 and 5, t = 1, u = 2, v = 3
Rate this question:
Business process-based testing
Performance, load and stress testing
Requirements-based testing
Usability testing
Top-down integration testing
Rate this question:
Expected outcomes are defined by the software’s behaviour
Expected outcomes are derived from a specification, not from the code
Expected outcomes include outputs to a screen and changes to files and databases
Expected outcomes should be predicted before a test is run
Expected outcomes may include timing constraints such as response times
Rate this question:
ISO/IEC 12207
BS7925-1
BS7925-2
ANSI/IEEE 829
ANSI/IEEE 729
Rate this question:
Is not important
Increases as we move the product towards live use
Decreases as we move the product towards live use
Is more expensive if found in requirements than functional design
Can never be determined
Rate this question:
Test items (i.e. software versions)
What is not to be tested
Test environments
Quality plans
Schedules and deadlines
Rate this question:
No, because they apply to development documentation
No, because they are normally applied before testing
No, because they do not apply to the test documentation
Yes, because both help detect faults and improve quality
Yes, because testing includes all non-constructive activities
Rate this question:
Measuring response time
Measuring transaction rates
Recovery testing
Simulating many users
Generating many transactions
Rate this question:
As the first approach to deriving test cases
After more formal techniques have been applied
By inexperienced testers
After the system has gone live
Only by end users
Rate this question:
Quiz Review Timeline (Updated): Mar 21, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.