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. A black box test design technique in which test cases are designed to execute business procedures and processes. [TMap] See also procedure testing. Testing aimed at ensuring that the component or system can operate in conjunction with new or existing
Function Point Analysis (FPA)
site acceptance testing
process cycle test
quality
2. A document that specifies - ideally in a complete - precise and verifiable manner - the requirements - design - behavior - or other characteristics of a component or system - and - often - the procedures for determining whether these provisions have
specification
non-functional testing
data flow testing
functional testing
3. A factor that could result in future negative consequences; usually expressed as impact and likelihood.
wild pointer
performance profiling
risk
acceptance testing
4. An element of configuration management - consisting of the evaluation - co-ordination - approval or disapproval - and implementation of changes to configuration items after formal establishment of their configuration identification. [IEEE 610]
desk checking
horizontal traceability
configuration control
expected result
5. The capability of the software product to be used in place of another specified software product for the same purpose in the same environment. [ISO 9126] See also portability. The ease with which the software product can be transferred from one hardw
co-existence
exploratory testing
test execution technique
replaceability
6. 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]
release note
test level
maintainability
vertical traceability
7. The process of testing to determine the functionality of a software product.
volume testing
heuristic evaluation
functionality testing
operational profile
8. A portion of an input or output domain for which the behavior of a component or system is assumed to be the same - based on the specification.
equivalence partition
finite state machine
test automation
domain
9. A framework that describes the key elements of an effective product development and maintenance process. The Capability Maturity Model Integration covers best-practices for planning - engineering and managing product development and maintenance. CMMI
Capability Maturity Model Integration (CMMI)
dynamic testing
Test Maturity Model (TMM)
test policy
10. The process of testing to determine the resource-utilization of a software product. See also efficiency testing. The process of testing to determine the efficiency of a software product.
path sensitizing
resource utilization testing
reliability
compliance
11. An uninterrupted period of time spent in executing tests. In exploratory testing - each test session is focused on a charter - but testers can also explore new opportunities or issues during a session. The tester creates and executes test cases on th
hazard analysis
test session
user test
recoverability testing
12. A path for which a set of input values and preconditions exists which causes it to be executed.
feasible path
path coverage
random testing
operational acceptance testing
13. The period of time in the software life cycle during which the requirements for a software product are defined and documented. [IEEE 610]
exhaustive testing
severity
requirements phase
condition determination coverage
14. The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate. [After IEEE 610] See also efficiency. The capability of the software product to provide appropriat
pseudo-random
exploratory testing
acceptance testing
performance
15. A reason or purpose for designing and executing a test.
expected result
test objective
code
buffer
16. A variable (whether stored within a component or outside) that is written by a component.
control flow graph
test design
output
operational profile testing
17. Decision rules used to determine whether a test item (function) or feature has passed or failed a test. [IEEE 829]
defect masking
false-fail result
pass/fail criteria
incremental development model
18. 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.
stability
testing
testability
multiple condition coverage
19. A high level metric of effectiveness and/or efficiency used to guide and control progressive development - e.g. lead-time slip for software development. [CMMI]
condition
test environment
alpha testing
performance indicator
20. A tool for seeding (i.e. intentionally inserting) faults in a component or system.
fault seeding tool
basis test set
result
defect
21. A test tool to perform automated test comparison of actual results with expected results.
test comparator
cyclomatic complexity
test management tool
structural coverage
22. A software tool used to carry out instrumentation.
audit
recovery testing
quality assurance
instrumenter
23. A tool that provides support for testing security characteristics and vulnerabilities.
fail
risk level
security testing tool
measure
24. An incremental approach to integration testing where the component at the top of the component hierarchy is tested first - with lower level components being simulated by stubs. Tested components are then used to test lower level components. The proce
monitor
exercised
top-down testing
performance profiling
25. Testing to determine how the occurrence of two or more activities within the same interval of time - achieved either by interleaving the activities or by simultaneous execution - is handled by the component or system. [After IEEE 610]
expected result
exercised
volume testing
concurrency testing
26. The process of assigning a number or category to an entity to describe an attribute of that entity. [ISO 14598]
CAST
design-based testing
statement testing
measurement
27. Testing performed to expose defects in the interfaces and interaction between integrated components.
risk-based testing
driver
component integration testing
scripting language
28. A requirement that specifies a function that a component or system must perform. [IEEE 610]
functional requirement
test control
LCSAJ
availability
29. The first executable statement within a component.
test specification
oracle
failure mode
entry point
30. A tool that supports operational security.
defect tracking tool
security tool
coverage
test objective
31. A five level staged framework that describes the key elements of an effective software process. The Capability Maturity Model covers best-practices for planning - engineering and managing software development and maintenance. [CMM] See also Capabilit
test strategy
load profile
Capability Maturity Model (CMM)
procedure testing
32. An independent evaluation of software products or processes to ascertain compliance to standards - guidelines - specifications - and/or procedures based on objective criteria - including documents that specify: (1) the form or content of the products
condition determination coverage
traceability
non-functional testing
audit
33. The percentage of definition-use pairs that have been exercised by a test suite.
regression testing
operational profile testing
test approach
data flow coverage
34. Testing to determine the security of the software product. See also functionality testing. The process of testing to determine the functionality of a software product.
security testing
acceptance criteria
coverage
postcondition
35. An entity in a programming language - which is typically the smallest indivisible unit of execution.
use case
statement
Test Maturity Model Integrated (TMMi)
system of systems
36. Testing of a component or system at specification or implementation level without execution of that software - e.g. reviews or static code analysis.
peer review
static testing
operability
agile testing
37. Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.
precondition
multiple condition coverage
specified input
scripted testing
38. An aggregation of hardware - software or both - that is designated for configuration management and treated as a single entity in the configuration management process. [IEEE 610]
design-based testing
configuration item
operational profile
test harness
39. The representation of a distinct set of tasks performed by the component or system - possibly based on user behavior when interacting with the component or system - and their probabilities of occurance. A task is logical rather that physical and can
operational profile
bespoke software
incident management tool
vertical traceability
40. A test whereby real-life users are involved to evaluate the usability of a component or system.
use case testing
hazard analysis
configuration auditing
user test
41. A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item - control changes to those characteristics - record and report change processi
test strategy
configuration management
test execution
performance testing tool
42. A document specifying the test conditions (coverage items) for a test item - the detailed test approach and identifying the associated high level test cases. [After IEEE 829]
process cycle test
functionality testing
test design specification
non-functional test design techniques
43. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge - for example the minimum or maximum value of a range.
portability
requirements-based testing
capture/playback tool
boundary value
44. The process of identifying risks using techniques such as brainstorming - checklists and failure history.
Fault Tree Analysis (FTA)
decision table testing
risk identification
test design technique
45. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program paths is available - e.g. case - jump - go to - if-then-else.
branch
dynamic analysis
behavior
exhaustive testing
46. The testing activities that must be repeated when testing is re-started after a suspension. [After IEEE 829]
test reproduceability
Test Point Analysis (TPA)
test oracle
resumption criteria
47. The process of testing to determine the interoperability of a software product. See also functionality testing. The process of testing to determine the functionality of a software product.
defect based test design technique
interoperability testing
process improvement
defect density
48. A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.
security
traceability
understandability
defect taxonomy
49. Definition of user profiles in performance - load and/or stress testing. Profiles should reflect anticipated or actual usage based on an operational profile of a component or system - and hence the expected workload. See also load profile - operation
configuration identification
performance profiling
system of systems
statement coverage
50. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-of-code - number of classes or function points).
phase test plan
defect density
path testing
failure mode