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. Testing to determine the scalability of the software product.
input value
suitability
test log
scalability testing
2. The assessment of change to the layers of development documentation - test documentation and components - in order to implement a given change to specified requirements.
output
impact analysis
Fault Tree Analysis (FTA)
bottom-up testing
3. 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]
risk management
pairwise testing
interoperability
maintainability
4. The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. [After IEEE 829]
defect
stress testing
entry point
suspension criteria
5. A human action that produces an incorrect result. [After IEEE 610]
decision table testing
test progress report
error
usability
6. Software developed specifically for a set of users or customers. The opposite is off-the-shelf software.
bespoke software
dynamic testing
test log
test design tool
7. 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.
equivalence partitioning
acceptance criteria
fault seeding
intake test
8. A type of performance testing conducted to evaluate the behavior of a component or system with increasing load - e.g. numbers of parallel users and/or numbers of transactions - to determine what load can be handled by the component or system. See als
test monitoring
condition testing
usability
load testing
9. A set of one or more test cases. [IEEE 829]
Failure Mode - Effect and Criticality Analysis (FMECA)
test
complexity
moderator
10. The capability of the software product to enable the user to learn its application. [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
test session
unreachable code
reliability
learnability
11. A group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are component test - integration test - system test and acceptance test. [After TMap]
test
decision condition coverage
statistical testing
test level
12. A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.
defect taxonomy
performance profiling
path sensitizing
result
13. The leader and main person responsible for an inspection or other review process.
staged representation
test monitoring
moderator
test basis
14. A 2-dimensional array constructed with special mathematical properties - such that choosing any two columns in the array provides every pair combination of each number in the array.
decision testing
specification
orthogonal array
defect density
15. The importance of a risk as defined by its characteristics impact and likelihood. The level of risk can be used to determine the intensity of testing to be performed. A risk level can be expressed either qualitatively (e.g. high - medium - low) or qu
V-model
quality management
risk level
verification
16. A statement which - when compiled - is translated into object code - and which will be executed procedurally when the program is running and may perform an action on data.
scribe
executable statement
load testing
path testing
17. 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.
risk
elementary comparison testing
Fault Tree Analysis (FTA)
data definition
18. The capability of the software product to avoid unexpected effects from modifications in the software. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements
stability
functionality testing
test planning
availability
19. 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
buffer
post-execution comparison
big-bang testing
operability
20. A test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned. See also test management. The planning - estimating - monitoring and co
severity
security testing
test control
accuracy
21. 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
regression testing
hazard analysis
resumption criteria
buffer overflow
22. 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).
structural coverage
test infrastructure
definition-use pair
priority
23. A test approach in which the test suite comprises all combinations of input values and preconditions.
exhaustive testing
interoperability
consistency
test specification technique
24. Testware used in automated testing - such as tool scripts.
black-box test design technique
test policy
maturity
automated testware
25. The process of recognizing - investigating - taking action and disposing of defects. It involves recording defects - classifying them and identifying the impact. [After IEEE 1044]
efficiency
defect management
operational profile
installability
26. Comparison of actual and expected results - performed while the software is being executed - for example by a test execution tool.
configuration
dynamic comparison
simulator
test case
27. The process of confirming that a component - system or person complies with its specified requirements - e.g. by passing an exam.
certification
audit
maturity
unit test framework
28. A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]
test summary report
decision table
cause-effect graph
scalability testing
29. 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).
negative testing
invalid testing
state transition
component specification
30. An approach to testing to reduce the level of product risks and inform stakeholders on their status - starting in the initial stages of a project. It involves the identification of product risks and their use in guiding the test process.
risk-based testing
quality management
testing
quality assurance
31. A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script. [After IEEE 829]
recovery testing
dynamic comparison
test scenario
ad hoc testing
32. A Linear Code Sequence And Jump - consisting of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of executable statements - the end of the linear sequence - and the targe
test object
LCSAJ
test condition
usability testing
33. A development activity where a complete system is compiled and linked every day (usually overnight) - so that a consistent system is available at any time including all latest changes.
test execution
baseline
defect tracking tool
daily build
34. 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 testing tasks - who will do each task - degree of tester independence - the tes
test level
operational profile
test plan
code coverage
35. A specific category of risk related to the type of testing that can mitigate (control) that category. For example the risk of user-interactions being misunderstood can be mitigated by usability testing.
review
test execution tool
risk level
risk type
36. 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.
test progress report
multiple condition coverage
configuration control
installation guide
37. Testing to determine the robustness of the software product.
resource utilization testing
robustness testing
hazard analysis
reviewer
38. The number or category assigned to an attribute of an entity by making a measurement. [ISO 14598]
coverage analysis
testability review
measure
independence of testing
39. 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]
defect density
quality assurance
state diagram
operational profile
40. (1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. See also Capability Maturity Model - Test Maturity Model. (2) The capability of the software product to avoid failure as a res
business process-based testing
maturity
statistical testing
black-box test design technique
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.
probe effect
test case suite
data flow testing
reliability growth model
42. A test tool to perform automated test comparison of actual results with expected results.
experienced-based test design technique
test comparator
data driven testing
result
43. A tool that provides support for testing security characteristics and vulnerabilities.
beta testing
white-box test design technique
security testing tool
elementary comparison testing
44. Testing practice for a project using agile methodologies - such as extreme programming (XP) - treating development as the customer of testing and emphasizing the test first design paradigm. See also test driven development. A way of developing softwa
technical review
agile testing
configuration item
performance indicator
45. A capability maturity model structure wherein capability levels provide a recommended order for approaching process improvement within specified process areas. [CMMI]
incident logging
continuous representation
back-to-back testing
testing
46. The degree - expressed as a percentage - to which a specified coverage item has been exercised by a test suite.
coverage
error guessing
risk identification
test performance indicator
47. Testing - either functional or non-functional - without reference to the internal structure of the component or system. Black-box test design technique Procedure to derive and/or select test cases based on an analysis of the specification - either fu
black-box testing
user acceptance testing
dynamic comparison
decision condition coverage
48. A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and Graham - IEEE 1028] See also peer review. A review of a software work product by colleagues of the producer of the product for the p
Test Maturity Model Integrated (TMMi)
behavior
process
technical review
49. 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.
cause-effect graph
compatibility testing
incremental testing
functional requirement
50. A set of interrelated activities - which transform inputs into outputs. [ISO 12207]
suitability
process
installation wizard
CAST