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 program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches.
decision
testware
test case
stub
2. The process of evaluating behavior - e.g. memory performance - CPU usage - of a system or component during execution. [After IEEE 610]
dynamic analysis
frozen test basis
blocked test case
software quality
3. The ability to identify related items in documentation and software - such as requirements with associated tests. See also horizontal traceability - vertical traceability. The tracing of requirements for a test level through the layers of test docume
traceability
scalability testing
automated testware
availability
4. 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]
false-fail result
concurrency testing
defect report
test object
5. The percentage of definition-use pairs that have been exercised by a test suite.
executable statement
data flow coverage
pseudo-random
Wide Band Delphi
6. The process of running a test on the component or system under test - producing actual result(s).
high level test case
walkthrough
test execution
learnability
7. A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.
pass/fail criteria
domain
co-existence
defect taxonomy
8. A list of activities - tasks or events of the test process - identifying their intended start and finish dates and/or times - and interdependencies.
test schedule
risk management
efficiency testing
test logging
9. The component or system to be tested. See also test item. 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.
test object
intake test
classification tree method
procedure testing
10. The percentage of decision outcomes that have been exercised by a test suite. 100% decision coverage implies both 100% branch coverage and 100% statement coverage.
decision coverage
scribe
fault seeding
buffer overflow
11. 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).
changeability
basic block
component specification
re-testing
12. A black box test design technique in which test cases are designed to execute business procedures and processes. [TMap] See also procedure testing. Testing aimed at ensuring that the component or system can operate in conjunction with new or existing
N-switch coverage
test control
process cycle test
milestone
13. Environmental and state conditions that must be fulfilled after the execution of a test or test procedure.
code-based testing
testware
postcondition
stress testing
14. 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 Maturity Model Integrated (TMMi)
load testing
orthogonal array testing
probe effect
15. Analysis of source code carried out without execution of that software.
static code analysis
configuration identification
Wide Band Delphi
phase test plan
16. A framework that describes the key elements of an effective product development and maintenance process. The Capability Maturity Model Integration covers best-practices for planning - engineering and managing product development and maintenance. CMMI
Capability Maturity Model Integration (CMMI)
configuration control
documentation testing
adaptability
17. The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.
buffer overflow
test run
control flow
branch coverage
18. The capability of the software product to be installed in a specified environment [ISO 9126]. See also portability. The ease with which the software product can be transferred from one hardware or software environment to another. [ISO 9126]
risk
configuration control board (CCB)
root cause analysis
installability
19. Testing that involves the execution of the software of a component or system.
back-to-back testing
defect density
dynamic testing
pair testing
20. A tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE tool repository - e.g. requirements management tool - from specified test conditions held in the tool itself - or from code.
test design tool
accessibility testing
state transition testing
test planning
21. The process of testing to determine the functionality of a software product.
software quality
functionality testing
coverage
defect management
22. 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.
condition determination coverage
co-existence
installability
defect tracking tool
23. Acronym for Computer Aided Software Engineering.
condition
CASE
coverage item
functional integration
24. A formula based test estimation method based on function point analysis. [TMap]
Test Point Analysis (TPA)
fault tolerance
test target
test estimation
25. The percentage of sequences of N+1 transitions that have been exercised by a test suite. [Chow]
certification
infeasible path
N-switch coverage
regression testing
26. The ease with which the software product can be transferred from one hardware or software environment to another. [ISO 9126]
configuration control
requirements management tool
portability
domain
27. 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]
data flow testing
procedure testing
condition determination coverage
failure mode
28. A white box test design technique in which test cases are designed to execute definition and use pairs of variables.
quality assurance
incident management tool
data flow testing
system integration testing
29. The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified interface. [ISO 9126] See also reliability - robustness. The ability of the software product
expected result
decision outcome
fault tolerance
project risk
30. A sequence of one or more consecutive executable statements containing no branches. Note: A node in a control flow graph represents a basic block.
basic block
state table
test data preparation tool
test case suite
31. Testing the integration of systems and packages; testing interfaces to external organizations (e.g. Electronic Data Interchange - Internet).
system integration testing
test schedule
control flow graph
learnability
32. The degree to which a requirement is stated in terms that permit establishment of test designs (and subsequently test cases) and execution of tests to determine whether the requirements have been met. [After IEEE 610]
testable requirements
requirements phase
test case
simulator
33. 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.
master test plan
procedure testing
installability testing
probe effect
34. A specification or software product that has been formally reviewed or agreed upon - that thereafter serves as the basis for further development - and that can be changed only through a formal change control process. [After IEEE 610]
fault tolerance
configuration management
baseline
interoperability
35. A development life cycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or external) of an executable product - a subset of the final product under dev
portability testing
status accounting
hazard analysis
iterative development model
36. An entity in a programming language - which is typically the smallest indivisible unit of execution.
test scenario
accessibility testing
test data
statement
37. The process of recognizing - investigating - taking action and disposing of incidents. It involves logging incidents - classifying them and identifying the impact. [After IEEE 1044]
test objective
suspension criteria
incident management
output value
38. 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 - or structural element.
defect
system testing
bespoke software
test condition
39. The capability of the software product to adhere to standards - conventions or regulations in laws and similar prescriptions. [ISO 9126]
incident
defect
compliance
quality management
40. A test tool to perform automated test comparison of actual results with expected results.
static analysis tool
test design specification
test comparator
back-to-back testing
41. An attribute of a component or system specified or implied by requirements documentation (for example reliability - usability or design constraints). [After IEEE 1008]
feature
error guessing
test reproduceability
scripting language
42. An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes - it is hoped that the likelihood of defect recurrence will be minimized.
robustness
root cause analysis
configuration management tool
non-functional test design techniques
43. A test is deemed to fail if its actual result does not match its expected result.
defect density
test execution technique
metric
fail
44. A development life cycle where a project is broken into a series of increments - each of which delivers a portion of the functionality in the overall project requirements. The requirements are prioritized and delivered in priority order in the approp
level test plan
incremental development model
project risk
black-box test design technique
45. 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.
attack
non-functional test design techniques
metric
Test Maturity Model (TMM)
46. 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
code
measurement
module
47. A white box test design technique in which test cases are designed to execute branches.
V-model
branch testing
site acceptance testing
system integration testing
48. 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.
test suite
compatibility testing
COTS
path sensitizing
49. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes.
business process-based testing
migration testing
usability
result
50. The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions. [IEEE 610] See also error-tolerance - fault-tolerance. The ability of a system or component to continue normal o
test cycle
coverage
robustness
requirements phase