ISTQB- All Chapters Exam15 assesses knowledge across various testing protocols and standards, including the handling of test incidents and the importance of testing independence. It is designed for individuals aiming to certify their expertise in software testing.
Testers
Developers
Users
All of the above
Rate this question:
Inputs
The person who caused the incident The person who caused the incident - correct
Actual Results and expected results
Date and Time
Rate this question:
A. Impact - the actual or potential damage that could be caused by the incident
B. Who performed the tests
Neither a nor b
Both a and b
Rate this question:
The amount of time needed for testing decreases
Testers are friendlier with the developers
Testers are generally friendlier with the system's end users
None of the above
Rate this question:
Less independent
More independent
None of the above
Equally independent
Rate this question:
1, 2, and 5 are true; 3 and 4 are false
2, 3 and 4 are true; 1 and 5 are false
1, 2, and 4 are true; 3 and 5 are false
1, 2, and 3 are true; 4 and 5 are false
Rate this question:
Recommend project actions
Execute tests
Estimate time and cost
Recommend project actions
Rate this question:
Data for previous similar projects are not available
The development to test time ratio is unknown
Domain subject matter experts are not available to assist
Non-functional requirements often are not well documented
Rate this question:
A document specifying the test conditions for a test item, establishing the detailed test approach and identifying the associated high level test cases
A document specifying a set of test cases ( objective, inputs, test actions, expected results and execution preconditions) for a test team
A document reporting on any event that occurred during testing which requires further investigation
A document describing the scope, approach, resources, and schedule of intended test activities
Rate this question:
Risk-based test approach
Business risks of insufficient testing
Risks and contingencies
Has no section for risks
Rate this question:
No medium or high severity defects remain uncorrected
All planned test coverage goals have been met
All planned test cases have been written, executed, and passed
All of the above
Rate this question:
A group of people responsible for evaluating, approving or disapproving, and monitoring proposed changes items
A group of people responsible for preventing changes to items under configuration management control
A group of people who make approved changes to items under configuration management control
A visible board , posted in a public place, on which items under configuration management control are displayed and tracked
Rate this question:
It is unclear why code changes were made
Regression testing is required
Modifications to documents or code are overwritten
It is unclear what version of the software is being tested
Rate this question:
Test Plans
Test Environment
Test Scripts
All of the above
Rate this question:
Approvals
List of all defects found
Variances from the test plans
Comprehensiveness assessments
Rate this question:
Test Control
Test Leadership
Test monitoring
Test design
Rate this question:
Component or system ordered from highest to lowest risk
Component or system per developer
Component or system divided by the size of the component or system
Component or System
Rate this question:
Extend the schedule to allow more time to complete the planned tests
Automate some of the manual tests
Prioritize which tests to perform and which not to perform
Add additional testers who have experience on the system under test
Rate this question:
Can improve the parameters it is measuring
Has no effect on the parameters it is measuring
Can adversely affect the parameters it is measuring
Does not integrate well into the development and / or testing process
Rate this question:
Memory leaks
Ambiguous requirements statements
Designs that are too complex
Syntax errors in code
Rate this question:
Files and databases in test results
Tests designed and tests executed
Coverage planned and coverage achieved
Tests required and tests designed
Rate this question:
Trace test cases to requirements specifications
Code coverage
Interface to incident tracking tools
Support test planning and scheduling
Rate this question:
Are generalized sets of multiple test cases
Rarely require revision by the tester
By-pass the user interface and interact with the test object directly
May be invalidated by small changes in the system
Rate this question:
Represented in a table or spreadsheet describing actions
Scripts created automatically by capture/replay tools
Scripts created manually by testers
Represented in a table or spreadsheet containing decision tables Represented in a table or spreadsheet containing decision tables
Rate this question:
Let the tool dictate your processes rather than having your processes dictate your tool
Try a pilot or proof-of-concept use before widespread adoption
Make sure that your testers have a user manual for the tool
Have many projects begin using the tool simultaneously to maximize learning
Rate this question:
Pilot project with tool; Assess needs; evaluate tool supplier
Assess needs; evaluate tool options; implement tool
Assess needs; Obtain training; evaluate tool supplier
Assess needs; evaluate tool options; pilot project with tool
Rate this question:
Document the high-level test strategy and testing schedule
Describe the sequence of actions to execute one or more test cases within a suite of tests
Describe a test case and all of the conditions it tests
Document how the system will be tested, what features will be tested, and the pass/fail criteria for each feature
Rate this question:
Equally
More
Less
None of the above
Rate this question:
The program source code
An existing system
A user's knowledge
A user manual
Rate this question:
Less than 0; 1 through 10; greater than 10
1; 10
0; 5; 15
Less than 1; 1 through 10; greater than 10
Rate this question:
0.5, 5, 50
The specification is ambiguous and needs clarification before constructing test cases
-0.5, 0.5, 5, 50, 1500
-0.5, 0.5, 5, 50
-32,767; 500; 32,768; 2,000,000
50,000; 60,000; 243,000; 870,000; 1,500,000; 3,500,000
25,000; 75,000; 242,000; 600,000
0; 40,000; 60,000; 80,000; 120,000; 378,000
Rate this question:
Monday; Friday; Saturday
Monday; Saturday; Sunday
Monday; Saturday
Saturday; Sunday
Rate this question:
0, 15, 16, 18, 19, 20
15, 16, 17, 18, 19, 20
15, 16, 19, 20, 25
15, 16, 19, 20
Rate this question:
48
42
6
4
Rate this question:
In state-transition testing, test cases are constructed from state/event combinations.
State-transition testing is a static test technique
In state-transition testing, the requirements are in the form of a task-event matrix
State-transition testing is a technique which uses a graphical representation of combinations of code control points and expected outputs.
Rate this question:
Can be a person, another application , or an external system playing a role
Can pretend to do whatever it wants
Is different for each individual use case
Is a user or customer with in the system or application
Rate this question:
Integration test cases
System and acceptance test cases
Conformance test cases
Unit Test cases
Rate this question:
The sequential flow of messages from module (Unit) to module to implement a particular Use(Function)
A list of uses(functions) that the system provides
A screen diagram listing the functions that the system implements
Scenarios that describe the use of a system by an actor to accomplish a specific goal
Rate this question:
Quiz Review Timeline (Updated): Mar 20, 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.