.
Use case testing
Decision table testing
State transition testing
Boundary value analysis
A response of system to users interacting with other, integrated systems.
An description of an environment in which a system needs to operate.
A sequence of transaction between a user and a system to achieve a certain goal.
An operation on a system by a user, with no regards to the systems response.
25, 26, 35, 36, 45, 46, 55, 56
0, 1, 10, 11, 50, 51, 75, 76, 100, 101
10, 50, 75, 100, 250, 1000
0, 9, 19, 49, 50, 74, 75, 99, 100
Structure-based and experienced-based techniques
Sturcture-based technique and exhaustive testing
Specification-based and structure-based techniques
Black-box and specification-based techniques
White box technique
Black box technique
Grey box technique
Test design technique
Component testing should be black box, system testing should be white box.
The fewer bugs you find, the better your testing was
if u find a lot of bugs in testing, you should not be very confident about the quality of software
The more tests you run, the more bugs you will find.
White-box technique
Data driven testing technique
Structure-based technique
Experience-based technique
Equivalence partition
Decision table
Boundary value
State transition
Boundary value analysis
Decision table
Equivalence partitioning
State transition
Component testing
Defect Density Techniques
Data driven testing
Specification based technique
Less than 1, 1 through 11, and above
Less than 1, 1 through 11, larger than 12
Less than 0, 1 through 12, larger than 12
Less than 1, 1 through 12, larger than 12
Error guessing
Decision table testing
Use case testing
Exploratory testing
4
1
2
3
2, 26, 27, 29 and 30
1, 27, 28, 30 and 31
0, 1, 16, 31 and 100
-1, 0, 15, 32 and 99
Use case based testing is used only for object oriented projects where as other techniques can be used for all types of projects.
Use case based testing is more efficient than other techniques.
Use case testing provides end to end scenario based tests.
Use case based testing cannot be used in agile projects but other techniques can be used for other models.
Test scope
Test objective
Test environment
None of the above
Psychology of tester
How mature the development and testing process
End user
Performance of system
Ii & iii are True; i, iv & v are False
Ii is True; i, iii, iv & v are False
i & v are True; ii, iii & iv are False
Ii, iii & iv are True; i & v are False
6
3
4
5
2 tests for statement coverage, 2 for branch coverage
1 test for statement coverage, 2 for branch coverage
1 test for statement coverage, 1 for branch coverage
2 test for statement coverage, 1 for branch coverage
2
3
1
4
Desk checking
A mutation error
Debugging a program
Introducing mutation
O'Brien, Zeta-Jones, and Young Pow
Go, Stephanopoulous, and Venkatsewaran
Smith, Smyth, and Smithsonian
Johnson, de la Cruz, and Morgan
There are as many test cases as there are valid station names.
There are two equivalence classes, One valid name and one invalid station name.
There are three equivalence classes two valid names upper and lower case.one invalid name.
This specification is not solvable by equivalence partitioning.
Tests are derived based on the skills and experience of the tester
Tests are derived from information about how the software is constructed
Tests are derived from the extent of the coverage of structural elements of the system or components
Tests are derived from models (formal or informal) that specify the problem to be solved by the software or its components
10, 15 and 19 years
13, 19 and 25 years
12, 13 and 20 years
13, 16 and 19 years
N
N
N200
n
It focuses on generating reports.
This technique is context driven.
Writing test cases is the starting point of this test sequence.
The general flow of this testing process is Requirements, Test Cases and Bugs
-40, 37.78 and 100
-1, 0, 89.6 and 212
-1, 0, 1 and 37.78
-40, 0, 32 and 100
1 and 3
1
2
3
The test cases are designed to be used by real users, not by professional testers.
The test cases are designed to find defects in the data flow.
The test cases are always designed by customers or end users.
The test cases are designed to find defects in the process flow.
I and III are true
I, II, III and IV are true
I, II and III are true
I, II and IV are true
I, II and IV are true
II and IV are true
I, II, III and IV are true
I, II and III are true
Focused Testing, Testing coverage, control flow
Data integrity, Internal boundaries, algorithm specific testing
Both Focused testing etc & Date Integrity etc
None of the options
Opaque testing
Compatibility testing
Structural testing
All of the options
The test specifications should be written very detailed to ensure that everyone understands the application.
The tests should be very detailed with step by step procedures, including button clicks, tabs and menu selections.
The tests can be written with less details because of the testers expertise.
The test specification should follow IEEE standard template.
Boundary Value Analysis
Error Guessing
Decision Table testing
Equivalence partitioning
Hybrid analysis
Boundary value analysis
Equivalence partitioning
Decision table
2,4
1,3,4,5
1,2,3,5
1,3,4
Quiz Review Timeline (Updated): Apr 13, 2021 +
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:
6290 |
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:
625 |
Last updated:
Mar 20, 2023
|
Wait!
Here's an interesting quiz for you.