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 systematic way of testing all-pair combinations of variables using orthogonal arrays. It significantly reduces the number of all combinations of variables to test all pair combinations. See also pairwise testing. A black box test design technique i
impact analysis
result
equivalence partition coverage
orthogonal array testing
2. The level of (business) importance assigned to an item - e.g. defect.
priority
acceptance testing
performance indicator
cause-effect graph
3. The association of the definition of a variable with the use of that variable. Variable uses include computational (e.g. multiplication) or to direct the execution of a path ("predicate" use).
basis test set
definition-use pair
data driven testing
control flow
4. 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.
resource utilization testing
test closure
safety testing
memory leak
5. A white box test design technique in which test cases are designed to execute definition and use pairs of variables.
instrumentation
test performance indicator
boundary value analysis
data flow testing
6. An approach to testing in which test cases are designed based on the architecture and/or detailed design of a component or system (e.g. tests of interfaces between components or systems).
behavior
design-based testing
test level
false-fail result
7. A test tool to perform automated test comparison of actual results with expected results.
interoperability
documentation testing
test comparator
static analysis tool
8. Testing to determine the scalability of the software product.
scalability testing
precondition
test procedure specification
risk level
9. Method aiming to measure the size of the functionality of an information system. The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity - the estimation of the needed resources -
isolation testing
CASE
project
Function Point Analysis (FPA)
10. A test plan that typically addresses one test phase. See also test plan. A document describing the scope - approach - resources and schedule of intended test activities. It identifies amongst others test items - the features to be tested - the testin
project
phase test plan
specification
actual result
11. A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation - correction and re-testing of incidents and provide reporting facilities. See also defect manage
unit testing
user test
incident management tool
learnability
12. 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]
test case suite
input
version control
decision condition coverage
13. Testing the attributes of a component or system that do not relate to functionality - e.g. reliability - efficiency - usability - maintainability and portability.
test suite
pseudo-random
decision testing
non-functional testing
14. The degree to which a component - system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610]
back-to-back testing
wild pointer
quality
operational acceptance testing
15. An abstract representation of the sequence and possible changes of the state of data objects - where the state of an object is any of: creation - usage - or destruction. [Beizer]
static analyzer
migration testing
decision table testing
data flow
16. 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.
qualification
memory leak
functional integration
branch
17. The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires each single condition in every decision statement to be tested as True and False.
condition coverage
test execution technique
Test Point Analysis (TPA)
project
18. 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.
user test
module
incremental testing
non-conformity
19. The set from which valid input values can be selected. See also domain. The set from which valid input and/or output values can be selected.
accessibility testing
deliverable
pair programming
input domain
20. The process of testing to determine the maintainability of a software product.
test closure
dynamic comparison
serviceability testing
test execution phase
21. Code that cannot be reached and therefore is impossible to execute.
scalability testing
measurement
unreachable code
pair testing
22. 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.
condition coverage
cause-effect graphing
test tool
data flow testing
23. A description of a component's function in terms of its output values for specified input values under specified conditions - and required non-functional behavior (e.g. resource utilization).
component specification
pass/fail criteria
priority
validation
24. A scale that constrains the type of data analysis that can be performed on it. [ISO 14598]
business process-based testing
instrumentation
measurement scale
operational profile
25. The total costs incurred on quality activities and issues and often split into prevention costs - appraisal costs - internal failure costs and external failure costs.
design-based testing
test case suite
cost of quality
hyperlink
26. A test case with concrete (implementation level) values for input data and expected results. Logical operators from high level test cases are replaced by actual values that correspond to the objectives of the logical operators. See also high level te
test planning
low level test case
data flow
test basis
27. The number or category assigned to an attribute of an entity by making a measurement. [ISO 14598]
driver
measure
stress testing
suspension criteria
28. 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.
code coverage
best practice
interoperability testing
cyclomatic complexity
29. 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
defect masking
equivalence partitioning
experienced-based test design technique
30. Testing that involves the execution of the software of a component or system.
dynamic testing
capture/replay tool
priority
scripting language
31. Directed and focused attempt to evaluate the quality - especially reliability - of a test object by attempting to force specific failures to occur.
scripting language
stress testing
attack
condition determination testing
32. The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After IEEE 610].
system
multiple condition coverage
error tolerance
production acceptance testing
33. A framework to describe the software development life cycle activities from requirements specification to maintenance. The V-model illustrates how testing activities can be integrated into each phase of the software development life cycle.
operational profile testing
failure mode
output domain
V-model
34. An occurrence in which one defect prevents the detection of another. [After IEEE 610]
daily build
test performance indicator
defect masking
test monitoring
35. Procedure to derive and/or select test cases based on an analysis of the specification of the functionality of a component or system without reference to its internal structure. See also black box test design technique. Procedure to derive and/or sel
security testing
functional test design technique
security testing tool
static analyzer
36. The individual element to be tested. There usually is one test object and many test items. See also test object. A reason or purpose for designing and executing a test.
reviewer
performance testing tool
defect based test design technique
test item
37. A device or storage area used to store data temporarily for differences in rates of data flow - time or occurrence of events - or amounts of data that can be handeld by the devices or processes involved in the transfer or use of the data. [IEEE 610]
classification tree method
buffer
verification
syntax testing
38. A technique used to characterize the elements of risk. The result of a hazard analysis will drive the methods used for development and testing of a system. See also risk analysis. The process of assessing identified risks to estimate their impact and
hazard analysis
test script
scribe
instrumentation
39. Deviation of the component or system from its expected delivery - service or result. [After Fenton]
test execution
wild pointer
failure
procedure testing
40. A sequence of transactions in a dialogue between a user and the system with a tangible result.
user acceptance testing
smoke test
use case
big-bang testing
41. A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in reliability failures.
continuous representation
test input
test phase
reliability growth model
42. A tool that supports operational security.
test objective
component
COTS
security tool
43. The process of combining components or systems into larger assemblies.
failure rate
verification
integration
review tool
44. The process of testing to determine the recoverability of a software product. See also reliability testing. The process of testing to determine the reliability of a software product.
test strategy
compound condition
migration testing
recoverability testing
45. An extension of FMEA - as in addition to the basic FMEA - it includes a criticality analysis - which is used to chart the probability of failure modes against the severity of their consequences. The result highlights failure modes with relatively hig
unit
exercised
control flow analysis
Failure Mode - Effect and Criticality Analysis (FMECA)
46. 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]
version control
unit testing
output
test type
47. 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
LCSAJ
pass
top-down testing
bespoke software
48. A variable (whether stored within a component or outside) that is read by a component.
coverage tool
availability
path
input
49. A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 transitions. [Chow] See also state transition testing. A black box test design technique in which test cases are designed to execute valid and i
equivalence partition
N-switch testing
serviceability testing
fault seeding
50. Software developed specifically for a set of users or customers. The opposite is off-the-shelf software.
Software Usability Measurement Inventory (SUMI)
defect tracking tool
bespoke software
test planning