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 minimal software item that can be tested in isolation.
top-down testing
test approach
component
instrumentation
2. Definition of user profiles in performance - load and/or stress testing. Profiles should reflect anticipated or actual usage based on an operational profile of a component or system - and hence the expected workload. See also load profile - operation
test case specification
performance profiling
emulator
database integrity testing
3. 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.
testability review
COTS
oracle
multiple condition coverage
4. 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.
coverage item
scribe
boundary value coverage
Fault Tree Analysis (FTA)
5. A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]
Capability Maturity Model Integration (CMMI)
test summary report
security testing tool
security
6. The degree of impact that a defect has on the development or operation of a component or system. [After IEEE 610]
configuration auditing
severity
N-switch testing
impact analysis
7. The process of testing to determine the recoverability of a software product.
recovery testing
statement
management review
white-box testing
8. The insertion of additional code into the program in order to collect information about program behavior during execution - e.g. for measuring code coverage.
instrumentation
output
control flow graph
Fault Tree Analysis (FTA)
9. Testing to determine the extent to which the software product is understood - easy to learn - easy to operate and attractive to the users under specified conditions. [After ISO 9126]
test design specification
recoverability testing
usability testing
branch testing
10. 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
buffer overflow
re-testing
stress testing tool
test estimation
11. The percentage of equivalence partitions that have been exercised by a test suite.
root cause
boundary value coverage
dynamic analysis tool
equivalence partition coverage
12. The process of testing to determine the reliability of a software product.
result
hyperlink tool
maintainability
reliability testing
13. The use of software - e.g. capture/playback tools - to control the execution of tests - the comparison of actual results to expected results - the setting up of test preconditions - and other test control and reporting functions.
test target
multiple condition coverage
test execution automation
Failure Mode - Effect and Criticality Analysis (FMECA)
14. An independent evaluation of software products or processes to ascertain compliance to standards - guidelines - specifications - and/or procedures based on objective criteria - including documents that specify: (1) the form or content of the products
functional requirement
test manager
audit
installability testing
15. The method used to perform the actual test execution - either manual or automated.
negative testing
test execution technique
database integrity testing
classification tree method
16. A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation - correction and re-testing of incidents and provide reporting facilities. See also defect manage
incident management tool
specified input
state diagram
severity
17. 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
reliability testing
exception handling
incident logging
process cycle test
18. The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate. [After IEEE 610] See also efficiency. The capability of the software product to provide appropriat
test manager
performance
test design specification
pass/fail criteria
19. 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
decision outcome
fault tolerance
risk type
continuous representation
20. The planning - estimating - monitoring and control of test activities - typically carried out by a test manager.
test control
test management
test environment
test item
21. An integration test type that is concerned with testing the interfaces between components or systems.
risk level
security testing tool
interface testing
process cycle test
22. The calculated approximation of a result (e.g. effort spent - completion date - costs involved - number of test cases - etc.) which is usable even if input data may be incomplete - uncertain - or noisy.
load profile
entry point
test estimation
instrumenter
23. 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
walkthrough
daily build
project risk
instrumenter
24. A black box test design technique in which test cases are designed to execute all possbile discrete combinations of each pair of input parameters. See also orthogonal array testing. A systematic way of testing all-pair combinations of variables using
statistical testing
compliance testing
pairwise testing
test reproduceability
25. A black box test design technique in which test cases are designed to execute valid and invalid state transitions. See also N-switch testing. A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 tr
availability
test procedure
usability
state transition testing
26. An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests. [After Bach]
test specification
integration
Test Maturity Model (TMM)
exploratory testing
27. Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled. [ISO 9000]
postcondition
invalid testing
verification
test object
28. Testing of software or specification by manual simulation of its execution. See also static analysis. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.
desk checking
interface testing
safety testing
daily build
29. A collection of components organized to accomplish a specific function or set of functions. [IEEE 610]
data flow analysis
system
performance profiling
test comparison
30. 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
moderator
requirements management tool
coverage item
negative testing
31. A device or storage area used to store data temporarily for differences in rates of data flow - time or occurrence of events - or amounts of data that can be handeld by the devices or processes involved in the transfer or use of the data. [IEEE 610]
process
N-switch coverage
benchmark test
buffer
32. A source of a defect such that if it is removed - the occurance of the defect type is decreased or removed. [CMMI]
buffer
root cause
dynamic testing
maintenance
33. The capability of the software product to provide appropriate performance - relative to the amount of resources used under stated conditions. [ISO 9126]
invalid testing
black-box testing
efficiency
test monitoring
34. The process of testing to determine the maintainability of a software product.
cause-effect graph
maintainability testing
test item
equivalence partition
35. An executable statement where a variable is assigned a value.
capture/playback tool
scripting language
measurement
data definition
36. A sequence of one or more consecutive executable statements containing no branches. Note: A node in a control flow graph represents a basic block.
pointer
root cause analysis
basic block
quality assurance
37. The percentage of LCSAJs of a component that have been exercised by a test suite. 100% LCSAJ coverage implies 100% decision coverage.
Test Process Improvement (TPI)
actual result
LCSAJ coverage
static testing
38. 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.
safety critical system
dynamic testing
testability review
test evaluation report
39. A five level staged framework for test process improvement - related to the Capability Maturity Model Integration (CMMI) - that describes the key elements of an effective test process.
conversion testing
Test Maturity Model Integrated (TMMi)
error tolerance
attack
40. A test result which fails to identify the presence of a defect that is actually present in the test object.
finite state machine
accuracy
instrumenter
false-pass result
41. The behavior predicted by the specification - or another source - of the component or system under specified conditions.
dynamic analysis tool
load testing
expected result
load profile
42. 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
installation wizard
management review
recoverability testing
testware
43. 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 planning
test environment
security testing
test level
44. 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.
random testing
daily build
outcome
buffer overflow
45. Procedure used to derive and/or select test cases.
resource utilization testing
migration testing
test design technique
domain
46. The percentage of definition-use pairs that have been exercised by a test suite.
dynamic testing
data flow coverage
component testing
blocked test case
47. A path that cannot be exercised by any set of possible input values.
project risk
agile testing
version control
infeasible path
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.
intake test
test objective
black-box testing
code coverage
49. The capability of the software product to be attractive to the user. [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 9126]
changeability
ttractiveness
boundary value
desk checking
50. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program paths is available - e.g. case - jump - go to - if-then-else.
compatibility testing
use case testing
branch
reliability growth model