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 combinations of inputs using the concept of condition determination coverage. [TMap]
elementary comparison testing
documentation testing
recovery testing
feature
2. A minimal software item that can be tested in isolation.
decision outcome
unit
review tool
test procedure specification
3. A type of test tool that is able to execute other software using an automated test script - e.g. capture/playback. [Fewster and Graham]
alpha testing
test execution tool
hazard analysis
test execution phase
4. A program of activities designed to improve the performance and maturity of the organization's processes - and the result of such a program. [CMMI]
process improvement
scalability
anomaly
statement coverage
5. 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).
data flow
intake test
elementary comparison testing
defect density
6. A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. See also Failure Mode - Effect and Criticality Analysis (FMECA).
functionality testing
installability testing
component testing
Failure Mode and Effect Analysis (FMEA)
7. An instance of an input. See also input. A variable (whether stored within a component or outside) that is read by a component.
data flow testing
input value
test design specification
cause-effect graphing
8. The process of testing to determine the compliance of the component or system.
functional testing
compliance testing
failure rate
release note
9. The process of finding - analyzing and removing the causes of failures in software.
ttractiveness
debugging
code coverage
master test plan
10. The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. [After IEEE 829]
test progress report
security testing tool
suspension criteria
reliability testing
11. The assessment of change to the layers of development documentation - test documentation and components - in order to implement a given change to specified requirements.
failure
impact analysis
phase test plan
test comparison
12. An element of configuration management - consisting of selecting the configuration items for a system and recording their functional and physical characteristics in technical documentation. [IEEE 610]
Test Maturity Model Integrated (TMMi)
configuration identification
test control
process
13. A risk related to management and control of the (test) project - e.g. lack of staffing - strict deadlines - changing requirements - etc. See also risk. A factor that could result in future negative consequences; usually expressed as impact and likeli
negative testing
dynamic analysis tool
stability
project risk
14. A black box test design technique in which test cases are designed to execute user scenarios.
use case testing
unit test framework
fault seeding tool
scripted testing
15. A variable (whether stored within a component or outside) that is written by a component.
CASE
Function Point Analysis (FPA)
status accounting
output
16. A test environment comprised of stubs and drivers needed to execute a test.
replaceability
coverage analysis
path
test harness
17. Acronym for Commercial Off-The-Shelf software. See off-the-shelf software. A software product that is developed for the general market - i.e. for a large number of customers - and that is delivered to many customers in identical format.
testability
COTS
code coverage
test run
18. The capability of the software product to be upgraded to accommodate increased loads. [After Gerrard]
performance
defect density
low level test case
scalability
19. The evaluation of a condition to True or False.
incremental testing
risk
installation guide
condition outcome
20. The process of assessing identified risks to estimate their impact and probability of occurrence (likelihood).
error tolerance
risk analysis
complexity
functional requirement
21. The process of transforming general testing objectives into tangible test conditions and test cases.
high level test case
project
capture/replay tool
test design
22. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared - and analyzed in cases of discrepancies. [IEEE 610]
CAST
test execution schedule
back-to-back testing
volume testing
23. A tool that provides an environment for unit or component testing in which a component can be tested in isolation or with suitable stubs and drivers. It also provides other support for the developer - such as debugging capabilities. [Graham]
feature
unit test framework
black-box test design technique
load profile
24. Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.
static code analyzer
test script
classification tree method
precondition
25. A systematic evaluation of software acquisition - supply - development - operation - or maintenance process - performed by or on behalf of management that monitors progress - determines the status of plans and schedules - confirms requirements and th
efficiency testing
pair programming
actual result
management review
26. The capability of the software product to be attractive to the user. [ISO 9126] See also usability. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO 9126]
ttractiveness
output
condition determination coverage
compliance
27. Formal or informal testing conducted during the implementation of a component or system - usually in the development environment by developers. [After IEEE 610]
code coverage
requirement
development testing
test execution schedule
28. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes.
agile testing
business process-based testing
emulator
input domain
29. A black box test design technique in which test cases are designed to execute all possbile discrete combinations of each pair of input parameters. See also orthogonal array testing. A systematic way of testing all-pair combinations of variables using
pairwise testing
orthogonal array
test plan
project
30. A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation - correction and re-testing of defects and provide reporting facilities. See also incid
vertical traceability
black-box testing
defect management tool
ttractiveness
31. The capability of the software product to provide an appropriate set of functions for specified tasks and user objectives. [ISO 9126] See also functionality. The capability of the software product to provide functions which meet stated and implied ne
suitability
root cause analysis
test oracle
security testing
32. The set from which valid input and/or output values can be selected.
code
domain
state diagram
Function Point Analysis (FPA)
33. A white box test design technique in which test cases are designed to execute single condition outcomes that independently affect a decision outcome.
structural coverage
functional requirement
condition determination testing
measurement
34. Procedure to derive and/or select test cases for nonfunctional testing based on an analysis of the specification of a component or system without reference to its internal structure. See also black box test design technique. Procedure to derive and/o
non-functional test design techniques
error
impact analysis
static testing
35. A black box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle test cases are designed to cover each partition at least once.
test procedure
equivalence partitioning
measurement scale
compiler
36. Any event occurring that requires investigation. [After IEEE 1008]
incident
multiple condition coverage
test specification technique
cost of quality
37. A minimal software item that can be tested in isolation.
component
attack
component testing
cyclomatic complexity
38. Two or more single conditions joined by means of a logical operator (AND - OR or XOR) - e.g. 'A>B AND C>1000'.
condition
compound condition
interoperability testing
metric
39. The process of identifying risks using techniques such as brainstorming - checklists and failure history.
data flow testing
risk identification
decision
test design
40. Testing the methods and processes used to access and manage the data(base) - to ensure access methods - processes and data rules function as expected and that during access to the database - data is not corrupted or unexpectedly deleted - updated or
simulation
exception handling
database integrity testing
test session
41. The process of testing the installability of a software product. See also portability testing. The process of testing to determine the portability of a software product.
installability testing
defect management
exit criteria
static code analysis
42. A black box test design technique where test cases are selected - possibly using a pseudo-random generation algorithm - to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performa
defect management tool
definition-use pair
random testing
test
43. A test tool to perform automated test comparison of actual results with expected results.
test comparator
risk level
decision condition coverage
reliability growth model
44. 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
actual result
cyclomatic complexity
usability
component specification
45. Testing carried out informally; no formal test preparation takes place - no recognized test design technique is used - there are no expectations for results and arbitrariness guides the test execution activity.
attack
test tool
pass/fail criteria
ad hoc testing
46. The process of testing an integrated system to verify that it meets specified requirements. [Hetzel]
system testing
test plan
test specification technique
validation
47. A statement of test objectives - and possibly test ideas about how to test. Test charters are used in exploratory testing. See also exploratory testing. An informal test design technique where the tester actively controls the design of the tests as t
requirement
test charter
Test Point Analysis (TPA)
test type
48. The capability of the software product to enable the user to operate and control it. [ISO 9126] See also usability. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO
defect based test design technique
resource utilization
operability
desk checking
49. The percentage of sequences of N+1 transitions that have been exercised by a test suite. [Chow]
orthogonal array testing
ttractiveness
test infrastructure
N-switch coverage
50. The process of recording information about tests executed into a test log.
coverage
test logging
risk management
pass