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. An integration test type that is concerned with testing the interfaces between components or systems.
interface testing
defect taxonomy
retrospective meeting
decision condition coverage
2. A minimal software item that can be tested in isolation.
acceptance criteria
module
test implementation
risk management
3. 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
reliability testing
functional test design technique
test phase
test oracle
4. (1) A standard against which measurements or comparisons can be made. (2) A test that is be used to compare components or systems to each other or to a standard as in (1). [After IEEE 610]
test data preparation tool
incident management tool
benchmark test
resource utilization
5. The first executable statement within a component.
buffer overflow
feature
safety
entry point
6. A scheme for the execution of test procedures. The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed.
state transition
smoke test
test execution schedule
statement coverage
7. A programming language in which executable test scripts are written - used by a test execution tool (e.g. a capture/playback tool).
defect masking
decision condition testing
input domain
scripting language
8. 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.
Failure Mode and Effect Analysis (FMEA)
driver
resource utilization testing
incident logging
9. A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing. Statistical testing using a model of system operations (short duration tasks)
code coverage
reviewer
statistical testing
changeability
10. Testing of software used to convert data from existing systems for use in replacement systems.
migration testing
alpha testing
structural coverage
functional requirement
11. A factor that could result in future negative consequences; usually expressed as impact and likelihood.
risk
CASE
changeability
test scenario
12. A tool that supports the recording of requirements - requirements attributes (e.g. priority - knowledge responsible) and annotation - and facilitates traceability through layers of requirements and requirements change management. Some requirements ma
procedure testing
static analyzer
requirements management tool
LCSAJ
13. A scripting technique that stores test input and expected results in a table or spreadsheet - so that a single control script can execute all of the tests in the table. Data driven testing is often used to support the application of test execution to
LCSAJ coverage
coverage tool
test performance indicator
data driven testing
14. Deviation of the component or system from its expected delivery - service or result. [After Fenton]
failure
code coverage
risk-based testing
stub
15. 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
boundary value analysis
project risk
actual outcome
false-pass result
16. The process of recognizing - investigating - taking action and disposing of defects. It involves recording defects - classifying them and identifying the impact. [After IEEE 1044]
test manager
adaptability
defect management
test phase
17. Non fulfillment of a specified requirement. [ISO 9000]
pass
non-conformity
software
path
18. 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
test control
test object
measurement
defect based test design technique
19. The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs. [After ISO 9126]
interoperability
software quality
functionality testing
monkey testing
20. Decision rules used to determine whether a test item (function) or feature has passed or failed a test. [IEEE 829]
control flow analysis
error tolerance
pass/fail criteria
software
21. 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
defect report
maturity
test basis
resource utilization testing
22. An abstract representation of all possible sequences of events (paths) in the execution through a component or system.
suspension criteria
pair programming
component specification
control flow graph
23. 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.
orthogonal array
measure
informal review
test control
24. The tracing of requirements through the layers of development documentation to components.
off-the-shelf software
test type
vertical traceability
replaceability
25. Coverage measures based on the internal structure of a component or system.
formal review
operational testing
walkthrough
structural coverage
26. The percentage of executable statements that have been exercised by a test suite.
requirement
instrumenter
statement coverage
functionality testing
27. A static usability test technique to determine the compliance of a user interface with recognized usability principles (the so-called "heuristics").
heuristic evaluation
expected result
component
incremental testing
28. A tree showing equivalence parititions hierarchically ordered - which is used to design test cases in the classification tree method. See also classification tree method. A black box test design technique in which test cases - described by means of a
classification tree
test management
master test plan
iterative development model
29. Procedure used to derive and/or select test cases.
qualification
test design technique
test case suite
software life cycle
30. A set of exit criteria.
stability
test target
test data preparation tool
security testing
31. The effect on the component or system by the measurement instrument when the component or system is being measured - e.g. by a performance testing tool or monitor. For example performance may be slightly worse when performance testing tools are being
instrumentation
probe effect
use case
traceability
32. 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]
test procedure specification
V-model
test case specification
defect management
33. An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements - e.g. tests that exercise specific functions or probe non-functional attributes such as reliability or usability.
black-box test design technique
requirements-based testing
exit criteria
interoperability testing
34. The process of intentionally adding known defects to those already in the component or system for the purpose of monitoring the rate of detection and removal - and estimating the number of remaining defects. [IEEE 610]
safety
postcondition
fault seeding
fault tolerance
35. The process of assessing identified risks to estimate their impact and probability of occurrence (likelihood).
risk analysis
test charter
integration testing
requirements-based testing
36. Recording the details of any incident that occurred - e.g. during testing.
security tool
condition coverage
incident logging
maintainability testing
37. A tool used to check that no brtoken hyperlinks are present on a web site.
test evaluation report
test tool
structural coverage
hyperlink tool
38. The process of testing to determine the compliance of the component or system.
capture/playback tool
tester
compliance testing
condition outcome
39. A requirement that does not relate to functionality - but to attributes such as reliability - efficiency - usability - maintainability and portability.
maintenance testing
non-functional requirement
probe effect
defect tracking tool
40. Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. [ISO 9000]
test comparison
changeability
validation
test case specification
41. The process of evaluating behavior - e.g. memory performance - CPU usage - of a system or component during execution. [After IEEE 610]
dynamic analysis
test design specification
functional integration
load profile
42. Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled. [ISO 9000]
verification
output
dynamic testing
scalability testing
43. A minimal software item that can be tested in isolation.
compound condition
bottom-up testing
component
ad hoc testing
44. The behavior predicted by the specification - or another source - of the component or system under specified conditions.
production acceptance testing
decision condition testing
expected result
configuration auditing
45. 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]
installability
traceability
feasible path
buffer
46. The capability of the software product to adhere to standards - conventions or regulations in laws and similar prescriptions. [ISO 9126]
accessibility testing
compliance
qualification
robustness testing
47. Testing based on an analysis of the specification of the functionality of a component or system. See also black box testing. Testing - either functional or non-functional - without reference to the internal structure of the component or system. Black
functional testing
mutation analysis
thread testing
test execution
48. A tool that carries out static analysis.
static analyzer
false-pass result
test closure
test reproduceability
49. The activity of establishing or updating a test plan.
test planning
installability
test process
static code analysis
50. The process through which decisions are reached and protective measures are implemented for reducing risks to - or maintaining risks within - specified levels.
use case testing
risk control
system testing
decision table