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 document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]
coverage tool
instrumentation
Wide Band Delphi
defect report
2. 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 level
process improvement
monitor
acceptance testing
3. Execution of a test on a specific version of the test object.
beta testing
performance testing
test run
module
4. The process of recognizing - investigating - taking action and disposing of incidents. It involves logging incidents - classifying them and identifying the impact. [After IEEE 1044]
defect taxonomy
test design technique
efficiency testing
incident management
5. A scale that constrains the type of data analysis that can be performed on it. [ISO 14598]
measurement scale
feasible path
interface testing
test basis
6. A procedure to derive and/or select test cases targeted at one or more defect categories - with tests being developed from what is known about the specific defect category. See also defect taxonomy. A system of (hierarchical) categories designed to b
feature
module
defect based test design technique
actual result
7. Testing the integration of systems and packages; testing interfaces to external organizations (e.g. Electronic Data Interchange - Internet).
system integration testing
data flow coverage
test level
design-based testing
8. A system whose failure or malfunction may result in death or serious injury to people - or loss or severe damage to equipment - or environmental harm.
actual outcome
high level test case
safety critical system
cost of quality
9. An entity or property used as a basis for test coverage - e.g. equivalence partitions or code statements.
coverage item
certification
LCSAJ
risk
10. 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
Failure Mode - Effect and Criticality Analysis (FMECA)
peer review
Capability Maturity Model (CMM)
test phase
11. 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]
performance indicator
pair programming
back-to-back testing
level test plan
12. The period of time that begins when a software product is conceived and ends when the software is no longer available for use. The software life cycle typically includes a concept phase - requirements phase - design phase - implementation phase - tes
software life cycle
recovery testing
isolation testing
capture/replay tool
13. Artifacts produced during the test process required to plan - design - and execute tests - such as documentation - scripts - inputs - expected results - set-up and clear-up procedures - files - databases - environment - and any additional software or
decision condition coverage
testware
false-pass result
non-functional testing
14. 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]
resource utilization
elementary comparison testing
inspection
configuration identification
15. 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]
LCSAJ
coverage item
test type
security testing tool
16. Software developed specifically for a set of users or customers. The opposite is off-the-shelf software.
defect masking
coverage analysis
beta testing
bespoke software
17. A type of test tool that is able to execute other software using an automated test script - e.g. capture/playback. [Fewster and Graham]
exhaustive testing
test procedure
test execution tool
isolation testing
18. The number or category assigned to an attribute of an entity by making a measurement. [ISO 14598]
accessibility testing
safety testing
measure
error guessing
19. A tool that supports stress testing.
stress testing tool
white-box test design technique
unit test framework
feature
20. The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. [After IEEE 829]
white-box test design technique
suspension criteria
input value
exit point
21. 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.
code-based testing
interoperability testing
exercised
risk type
22. A tool that provides support to the test management and control part of a test process. It often has several capabilities - such as testware management - scheduling of tests - the logging of results - progress tracking - incident management and test
Capability Maturity Model (CMM)
LCSAJ coverage
test management tool
test control
23. The behavior produced/observed when a component or system is tested.
component integration testing
modelling tool
actual outcome
feature
24. Procedure to derive and/or select test cases based on the tester's experience - knowledge and intuition.
maintenance
changeability
experienced-based test design technique
orthogonal array
25. The process of testing to determine the maintainability of a software product.
buffer
attack
maintainability testing
off-the-shelf software
26. Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.
test logging
pair programming
output
precondition
27. The process of testing to determine the portability of a software product.
installation wizard
path sensitizing
portability testing
pair testing
28. Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers - to determine whether or not a component or system satisfies the user/customer needs and fits within the business process
beta testing
invalid testing
qualification
experienced-based test design technique
29. The total costs incurred on quality activities and issues and often split into prevention costs - appraisal costs - internal failure costs and external failure costs.
cost of quality
test target
reviewer
review tool
30. A high level document describing the principles - approach and major objectives of the organization regarding testing.
component specification
impact analysis
test policy
regression testing
31. A tool that provides run-time information on the state of the software code. These tools are most commonly used to identify unassigned pointers - check pointer arithmetic and to monitor the allocation - use and de-allocation of memory and to flag mem
pairwise testing
ad hoc testing
dynamic analysis tool
test estimation
32. A test approach in which the test suite comprises all combinations of input values and preconditions.
Test Maturity Model Integrated (TMMi)
structural coverage
exhaustive testing
code coverage
33. A chronological record of relevant details about the execution of tests. [IEEE 829]
random testing
test log
syntax testing
testware
34. The percentage of all condition outcomes and decision outcomes that have been exercised by a test suite. 100% decision condition coverage implies both 100% condition coverage and 100% decision coverage.
exhaustive testing
condition coverage
test phase
decision condition coverage
35. 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 acceptance testing
V-model
path testing
memory leak
36. 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
retrospective meeting
test design tool
stress testing tool
37. A feature or characteristic that affects an item's quality. [IEEE 610]
quality attribute
serviceability testing
output value
test harness
38. A set of exit criteria.
coverage
tester
pair testing
test target
39. The function to check on the contents of libraries of configuration items - e.g. for standards compliance. [IEEE 610]
safety testing
software life cycle
path coverage
configuration auditing
40. The capability of the software product to enable specified modifications to be implemented. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements - modified
changeability
component integration testing
test harness
domain
41. Acronym for Computer Aided Software Engineering.
CASE
stub
exception handling
exit point
42. A scripting technique that uses data files to contain not only test data and expected results - but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control scrip
keyword driven testing
reviewer
maturity
test input
43. A black box test design technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table. [Veenendaal] See also decision table. A table showing combinations of inputs and/or stimuli (c
false-fail result
Function Point Analysis (FPA)
stress testing
decision table testing
44. The process of testing to determine the functionality of a software product.
reliability growth model
functionality testing
accuracy
tester
45. 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
condition determination testing
incremental testing
non-functional test design techniques
decision condition coverage
46. Multiple heterogeneous - distributed systems that are embedded in networks at multiple levels and in multiple domains interconnected addressing large-scale inter-disciplinary common problems and purposes.
quality assurance
system of systems
stress testing tool
continuous representation
47. A method to determine test suite thoroughness by measuring the extent to which a test suite can discriminate the program from slight variants (mutants) of the program.
incident management
mutation analysis
smoke test
COTS
48. An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed - e.g. statement coverage - decision coverage or condition coverage.
cause-effect graphing
code coverage
incident management tool
development testing
49. An instance of an input. See also input. A variable (whether stored within a component or outside) that is read by a component.
pairwise testing
pair programming
coverage analysis
input value
50. Attributes of software products that bear on its ability to prevent unauthorized access - whether accidental or deliberate - to programs and data. [ISO 9126] See also functionality. The capability of the software product to provide functions which me
test management tool
branch testing
test design technique
security