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. 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
risk identification
pair testing
testware
measure
2. 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.
input domain
multiple condition testing
configuration control
software quality
3. A white box test design technique in which test cases are designed to execute decision outcomes.
decision testing
requirements management tool
decision
test management
4. The testing of individual software components. [After IEEE 610]
risk analysis
component testing
software
inspection
5. The process of recognizing - investigating - taking action and disposing of defects. It involves recording defects - classifying them and identifying the impact. [After IEEE 1044]
configuration
defect management
user acceptance testing
risk control
6. The last executable statement within a component.
audit
test infrastructure
exit point
business process-based testing
7. Separation of responsibilities - which encourages the accomplishment of objective testing. [After DO-178b]
audit trail
test phase
dynamic comparison
independence of testing
8. 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
system of systems
functional test design technique
fault tolerance
management review
9. The capability of the software product to be diagnosed for deficiencies or causes of failures in the software - or for the parts to be modified to be identified. [ISO 9126] See also maintainability. The ease with which a software product can be modif
system of systems
automated testware
analyzability
performance testing tool
10. The process of testing to determine the recoverability of a software product.
test progress report
changeability
development testing
recovery testing
11. Analysis of source code carried out without execution of that software.
dynamic analysis
static code analysis
black-box testing
pass/fail criteria
12. The physical or functional manifestation of a failure. For example - a system in failure mode may be characterized by slow operation - incorrect outputs - or complete termination of execution. [IEEE 610]
failure mode
decision table testing
security
Capability Maturity Model Integration (CMMI)
13. Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software - as a result of the changes made. It is performed when the software or its environment is c
white-box test design technique
simulator
path
regression testing
14. Hardware and software products installed at users' or customers' sites where the component or system under test will be used. The software may include operating systems - database management systems - and other applications.
acceptance testing
system
non-conformity
operational environment
15. Test execution carried out by following a previously documented sequence of tests.
test target
accessibility testing
scripted testing
Failure Mode and Effect Analysis (FMEA)
16. 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
test summary report
white-box test design technique
hazard analysis
static code analysis
17. The degree of impact that a defect has on the development or operation of a component or system. [After IEEE 610]
severity
buffer overflow
classification tree method
efficiency testing
18. An integration test type that is concerned with testing the interfaces between components or systems.
data flow coverage
isolation testing
traceability
interface testing
19. A white box test design technique in which test cases are designed to execute condition outcomes.
N-switch testing
test management
memory leak
condition testing
20. A review of a software work product by colleagues of the producer of the product for the purpose of identifying defects and improvements. Examples are inspection - technical review and walkthrough.
tester
peer review
pointer
configuration identification
21. The level of (business) importance assigned to an item - e.g. defect.
condition determination coverage
risk
priority
white-box testing
22. A memory access defect due to the attempt by a process to store data beyond the boundaries of a fixed length buffer - resulting in overwriting of adjacent memory areas or the raising of an overflow exception. See also buffer. A device or storage area
CAST
buffer overflow
coverage
interoperability
23. A tool that carries out static code analysis. The tool checks source code - for certain properties such as conformance to coding standards - quality metrics or data flow anomalies.
requirements-based testing
static code analyzer
test strategy
operability
24. The set from which valid input and/or output values can be selected.
domain
intake test
efficiency testing
site acceptance testing
25. The planning - estimating - monitoring and control of test activities - typically carried out by a test manager.
test management
intake test
requirements phase
stability
26. 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).
debugging tool
acceptance testing
Failure Mode and Effect Analysis (FMEA)
quality
27. An executable statement where a variable is assigned a value.
defect management tool
condition determination coverage
data definition
modelling tool
28. A data item that specifies the location of another data item; for example - a data item that specifies the address of the next employee record to be processed. [IEEE 610]
pointer
risk
statistical testing
technical review
29. A five level staged framework for test process improvement - related to the Capability Maturity Model (CMM) - that describes the key elements of an effective test process.
Test Maturity Model (TMM)
partition testing
business process-based testing
safety testing
30. 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 phase
equivalence partitioning
off-the-shelf software
scripted testing
31. All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure - then the test basis is called a frozen t
expected result
entry criteria
documentation testing
test basis
32. The capability of the software product to enable the user to understand whether the software is suitable - and how it can be used for particular tasks and conditions of use. [ISO 9126] See also usability. The capability of the software to be understo
severity
component testing
understandability
test tool
33. A source of a defect such that if it is removed - the occurance of the defect type is decreased or removed. [CMMI]
quality attribute
fault seeding
root cause
dynamic analysis tool
34. The percentage of definition-use pairs that have been exercised by a test suite.
behavior
interoperability testing
stability
data flow coverage
35. A program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches.
stress testing tool
decision
output value
beta testing
36. A document identifying test items - their configuration - current status and other delivery information delivered by development to testing - and possibly other stakeholders - at the start of a test execution phase. [After IEEE 829]
test
release note
use case
component
37. A logical expression that can be evaluated as True or False - e.g. A>B. See also test condition. An item or event of a component or system that could be verified by one or more test cases - e.g. a function - transaction - feature - quality attribute
branch testing
load profile
condition
non-functional requirement
38. A form of static analysis based on the definition and usage of variables.
thread testing
monitor
simulation
data flow analysis
39. A document produced at the end of the test process summarizing all testing activities and results. It also contains an evaluation of the test process and lessons learned.
baseline
decision
test evaluation report
modelling tool
40. 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
COTS
security testing tool
project risk
test summary report
41. A test plan that typically addresses one test level. 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
level test plan
dynamic testing
static testing
scripting language
42. The process of running a test on the component or system under test - producing actual result(s).
test execution
configuration auditing
efficiency
probe effect
43. The set of generic and specific conditions for permitting a process to go forward with a defined task - e.g. test phase. The purpose of entry criteria is to prevent a task from starting which would entail more (wasted) effort compared to the effort n
debugging tool
input
error
entry criteria
44. 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.
boundary value
changeability
mutation analysis
metric
45. An abstract representation of all possible sequences of events (paths) in the execution through a component or system.
concurrency testing
decision condition testing
verification
control flow graph
46. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO 9126]
decision table
changeability
usability
buffer overflow
47. Formal testing with respect to user needs - requirements - and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user - customers or other authorized entity to determine whether or n
formal review
documentation testing
user acceptance testing
instrumenter
48. A version of component integration testing where the progressive integration of components follows the implementation of subsets of the requirements - as opposed to the integration of components by levels of a hierarchy.
scalability testing
emulator
Failure Mode - Effect and Criticality Analysis (FMECA)
thread testing
49. Supplied instructions on any suitable media - which guides the installer through the installation process. This may be a manual guide - step-by-step procedure - installation wizard - or any other similar process description.
migration testing
installation guide
control flow analysis
load profile
50. 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]
version control
black-box testing
basic block
deliverable