SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
ISTQB
Start Test
Study First
Subjects
:
certifications
,
istqb
,
it-skills
Instructions:
Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. The process of confirming that a component - system or person complies with its specified requirements - e.g. by passing an exam.
certification
false-pass result
measurement scale
monkey testing
2. A group of test activities aimed at testing a component or system focused on a specific test objective - i.e. functional test - usability test - regression test etc. A test type may take place on one or more test levels or test phases. [After TMap]
test type
test monitoring
cost of quality
development testing
3. A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing. Statistical testing using a model of system operations (short duration tasks)
measurement scale
instrumentation
statistical testing
efficiency
4. A risk directly related to the test object. See also risk. A factor that could result in future negative consequences; usually expressed as impact and likelihood.
heuristic evaluation
product risk
test reproduceability
test comparator
5. The method used to perform the actual test execution - either manual or automated.
traceability
test execution technique
quality attribute
mutation analysis
6. A formula based test estimation method based on function point analysis. [TMap]
unreachable code
Test Point Analysis (TPA)
acceptance criteria
incident report
7. The behavior produced/observed when a component or system is tested.
bottom-up testing
actual outcome
incident management
level test plan
8. A test case without concrete (implementation level) values for input data and expected results. Logical operators are used; instances of the actual values are not yet defined and/or available. See also low level test case. A test case with concrete (
high level test case
test comparator
interoperability testing
recoverability
9. A path that cannot be exercised by any set of possible input values.
CASE
Function Point Analysis (FPA)
infeasible path
exploratory testing
10. The percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies 100% condition determination coverage.
interoperability testing
test design tool
test closure
multiple condition coverage
11. A tool that carries out static analysis.
static analysis tool
exploratory testing
portability
defect
12. The process of intentionally adding known defects to those already in the component or system for the purpose of monitoring the rate of detection and removal - and estimating the number of remaining defects. [IEEE 610]
system testing
operability
fault seeding
qualification
13. The degree of impact that a defect has on the development or operation of a component or system. [After IEEE 610]
maintenance
independence of testing
fault seeding tool
severity
14. Formal or informal testing conducted during the implementation of a component or system - usually in the development environment by developers. [After IEEE 610]
process cycle test
defect report
development testing
daily build
15. Behavior of a component or system in response to erroneous input - from either a human user or from another component or system - or to an internal failure.
exception handling
code-based testing
milestone
maintenance testing
16. A black box test design technique in which test cases are designed to execute user scenarios.
vertical traceability
use case testing
component
error
17. A diagram that depicts the states that a component or system can assume - and shows the events or circumstances that cause and/or result from a change from one state to another. [IEEE 610]
co-existence
equivalence partitioning
state diagram
test procedure
18. The response of a component or system to a set of input values and preconditions.
behavior
boundary value analysis
severity
system integration testing
19. A software product that supports one or more test activities - such as planning and control - specification - building initial files and data - test execution and test analysis. [TMap] See also CAST. Acronym for Computer Aided Software Testing.
test execution phase
test management tool
installability
test tool
20. Testing to determine the scalability of the software product.
defect tracking tool
scalability testing
hyperlink tool
safety
21. The calculated approximation of a result (e.g. effort spent - completion date - costs involved - number of test cases - etc.) which is usable even if input data may be incomplete - uncertain - or noisy.
test estimation
changeability
risk control
consistency
22. A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.
N-switch testing
Test Process Improvement (TPI)
configuration item
retrospective meeting
23. A black box test design technique in which test cases are designed to execute valid and invalid state transitions. See also N-switch testing. A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 tr
operational profile testing
defect based test design technique
state transition testing
control flow analysis
24. The ease with which a software product can be modified to correct defects - modified to meet new requirements - modified to make future maintenance easier - or adapted to a changed environment. [ISO 9126]
configuration
maintainability
failure rate
exercised
25. The period of time in the software life cycle during which the requirements for a software product are defined and documented. [IEEE 610]
version control
operational acceptance testing
requirements phase
usability testing
26. The process of developing and prioritizing test procedures - creating test data and - optionally - preparing test harnesses and writing automated test scripts.
defect density
condition determination coverage
component
test implementation
27. The process of testing to determine the reliability of a software product.
test target
reliability testing
risk control
keyword driven testing
28. A version of component integration testing where the progressive integration of components follows the implementation of subsets of the requirements - as opposed to the integration of components by levels of a hierarchy.
test specification technique
replaceability
software quality
thread testing
29. A distinct set of test activities collected into a manageable phase of a project - e.g. the execution activities of a test level. [After Gerrard]
test phase
infeasible path
learnability
coverage analysis
30. A test tool to perform automated test comparison of actual results with expected results.
test comparator
user test
horizontal traceability
performance testing tool
31. Operational testing in the acceptance test phase - typically performed in a simulated real-life operational environment by operator and/or administrator focusing on operational aspects - e.g. recoverability - resource-behavior - installability and te
accuracy
serviceability testing
data definition
operational acceptance testing
32. A type of integration testing in which software elements - hardware elements - or both are combined all at once into a component or an overall system - rather than in stages. [After IEEE 610] See also integration testing. Testing performed to expose
big-bang testing
deliverable
robustness
best practice
33. The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions. [IEEE 610] See also error-tolerance - fault-tolerance. The ability of a system or component to continue normal o
acceptance testing
invalid testing
robustness
Software Usability Measurement Inventory (SUMI)
34. A source of a defect such that if it is removed - the occurance of the defect type is decreased or removed. [CMMI]
scalability testing
black-box testing
unit
root cause
35. An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review - informal review - technical review - inspection - and walkthrough. [After IEEE 1028]
operational environment
test specification
requirements-based testing
review
36. Testing of software used to convert data from existing systems for use in replacement systems.
tester
conversion testing
security
test item
37. The activity of establishing or updating a test plan.
audit trail
test phase
acceptance criteria
test planning
38. A list of activities - tasks or events of the test process - identifying their intended start and finish dates and/or times - and interdependencies.
entry criteria
test schedule
test execution schedule
changeability
39. A specification or software product that has been formally reviewed or agreed upon - that thereafter serves as the basis for further development - and that can be changed only through a formal change control process. [After IEEE 610]
Capability Maturity Model Integration (CMMI)
user acceptance testing
baseline
test basis
40. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO 9126]
usability
statement coverage
test log
design-based testing
41. Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.
dynamic comparison
usability testing
white-box test design technique
operational profile testing
42. The effect on the component or system by the measurement instrument when the component or system is being measured - e.g. by a performance testing tool or monitor. For example performance may be slightly worse when performance testing tools are being
probe effect
compatibility testing
module
structural coverage
43. The number of independent paths through a program. Cyclomatic complexity is defined as: L - N + 2P - where - L = the number of edges/links in a graph - N = the number of nodes in a graph - P = the number of disconnected parts of the graph (e.g. a cal
incident report
accessibility testing
statement testing
cyclomatic complexity
44. An abstract representation of all possible sequences of events (paths) in the execution through a component or system.
control flow graph
path coverage
interoperability
quality assurance
45. A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures - human errors - and external events can combine to cause specific faults to disclose.
thread testing
Fault Tree Analysis (FTA)
negative testing
test execution
46. The process of transforming general testing objectives into tangible test conditions and test cases.
data flow coverage
test design
statistical testing
coverage tool
47. A black box test design technique in which test cases are designed based on boundary values. See also boundary value. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either si
test object
boundary value analysis
Test Maturity Model (TMM)
static testing
48. Testing where components or systems are integrated and tested one or some at a time - until all the components or systems are integrated and tested.
incremental testing
Capability Maturity Model (CMM)
test progress report
validation
49. The ability of the software product to perform its required functions under stated conditions for a specified period of time - or for a specified number of operations. [ISO 9126]
instrumenter
decision condition testing
reliability
incident logging
50. Testing aimed at ensuring that the component or system can operate in conjunction with new or existing users' business procedures or operational procedures.
continuous representation
procedure testing
suspension criteria
path
Sorry!:) No result found.
Can you answer 50 questions in 15 minutes?
Let me suggest you:
Browse all subjects
Browse all tests
Most popular tests
Major Subjects
Tests & Exams
AP
CLEP
DSST
GRE
SAT
GMAT
Certifications
CISSP go to https://www.isc2.org/
PMP
ITIL
RHCE
MCTS
More...
IT Skills
Android Programming
Data Modeling
Objective C Programming
Basic Python Programming
Adobe Illustrator
More...
Business Skills
Advertising Techniques
Business Accounting Basics
Business Strategy
Human Resource Management
Marketing Basics
More...
Soft Skills
Body Language
People Skills
Public Speaking
Persuasion
Job Hunting And Resumes
More...
Vocabulary
GRE Vocab
SAT Vocab
TOEFL Essential Vocab
Basic English Words For All
Global Words You Should Know
Business English
More...
Languages
AP German Vocab
AP Latin Vocab
SAT Subject Test: French
Italian Survival
Norwegian Survival
More...
Engineering
Audio Engineering
Computer Science Engineering
Aerospace Engineering
Chemical Engineering
Structural Engineering
More...
Health Sciences
Basic Nursing Skills
Health Science Language Fundamentals
Veterinary Technology Medical Language
Cardiology
Clinical Surgery
More...
English
Grammar Fundamentals
Literary And Rhetorical Vocab
Elements Of Style Vocab
Introduction To English Major
Complete Advanced Sentences
Literature
Homonyms
More...
Math
Algebra Formulas
Basic Arithmetic: Measurements
Metric Conversions
Geometric Properties
Important Math Facts
Number Sense Vocab
Business Math
More...
Other Major Subjects
Science
Economics
History
Law
Performing-arts
Cooking
Logic & Reasoning
Trivia
Browse all subjects
Browse all tests
Most popular tests