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. Analysis of source code carried out without execution of that software.
test environment
static code analysis
re-testing
test policy
2. Testware used in automated testing - such as tool scripts.
white-box testing
automated testware
test level
cyclomatic complexity
3. A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects) - which can be used to design test cases.
decision condition testing
severity
decision table
analyzability
4. The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After IEEE 610].
error tolerance
quality
automated testware
test
5. The process of testing to determine the recoverability of a software product.
recovery testing
pointer
classification tree
exhaustive testing
6. 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
Defect Detection Percentage (DDP)
risk level
software life cycle
dynamic analysis
7. The testing of individual software components. [After IEEE 610]
monitor
priority
test execution technique
component testing
8. A series which appears to be random but is in fact generated according to some prearranged sequence.
maintenance
re-testing
pseudo-random
dynamic comparison
9. 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).
monitor
quality management
component specification
test evaluation report
10. A systematic way of testing all-pair combinations of variables using orthogonal arrays. It significantly reduces the number of all combinations of variables to test all pair combinations. See also pairwise testing. A black box test design technique i
component specification
metric
failure mode
orthogonal array testing
11. A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system. [After TMap]
experienced-based test design technique
driver
black-box test design technique
statement testing
12. The evaluation of a condition to True or False.
condition outcome
false-pass result
postcondition
compiler
13. Two or more single conditions joined by means of a logical operator (AND - OR or XOR) - e.g. 'A>B AND C>1000'.
compound condition
entry criteria
risk
migration testing
14. The percentage of equivalence partitions that have been exercised by a test suite.
verification
equivalence partition coverage
security testing tool
maintenance testing
15. Any (work) product that must be delivered to someone other than the (work) product's author.
deliverable
test session
complexity
test script
16. The person responsible for project management of testing activities and resources - and evaluation of a test object. The individual who directs - controls - administers - plans and regulates the evaluation of a test object.
definition-use pair
test execution phase
test case specification
test manager
17. 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]
path
configuration control
Test Maturity Model Integrated (TMMi)
cyclomatic complexity
18. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge - for example the minimum or maximum value of a range.
orthogonal array testing
peer review
boundary value
installability
19. The process of recording information about tests executed into a test log.
syntax testing
test logging
error
testable requirements
20. A sequence of executable statements within a component.
subpath
test cycle
risk analysis
partition testing
21. 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]
co-existence
decision
test infrastructure
test procedure
22. 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
volume testing
system integration testing
suitability
configuration control
23. 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
peer review
test script
test input
acceptance testing
24. 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.
structural coverage
test automation
decision coverage
defect taxonomy
25. Systematic application of procedures and practices to the tasks of identifying - analyzing - prioritizing - and controlling risk.
risk management
finite state machine
input
severity
26. A chronological record of relevant details about the execution of tests. [IEEE 829]
iterative development model
exploratory testing
test log
test
27. Any condition that deviates from expectation based on requirements specifications - design documents - user documents - standards - etc. or from someone's perception or experience. Anomalies may be found during - but not limited to - reviewing - test
availability
accuracy
frozen test basis
anomaly
28. A grid showing the resulting transitions for each state combined with each possible event - showing both valid and invalid transitions.
state table
test design specification
reliability testing
entry point
29. 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
robustness
acceptance criteria
test object
path testing
30. A black box test design technique in which test cases are designed based on boundary values. See also boundary value. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either si
classification tree
decision outcome
test summary report
boundary value analysis
31. Testing the integration of systems and packages; testing interfaces to external organizations (e.g. Electronic Data Interchange - Internet).
system integration testing
error guessing
project risk
use case
32. A skeletal or special-purpose implementation of a software component - used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component. [After IEEE 610]
test evaluation report
stress testing
stub
root cause
33. 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
understandability
coverage
test approach
installation wizard
34. The composition of a component or system as defined by the number - nature - and interconnections of its constituent parts.
interface testing
variable
configuration
intake test
35. 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.
resource utilization
Test Point Analysis (TPA)
test automation
desk checking
36. 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 monitoring
test object
state transition testing
measure
37. A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and Graham - IEEE 1028] See also peer review. A review of a software work product by colleagues of the producer of the product for the p
test strategy
basis test set
coverage
technical review
38. Separation of responsibilities - which encourages the accomplishment of objective testing. [After DO-178b]
independence of testing
serviceability testing
operational profile
software
39. The planning - estimating - monitoring and control of test activities - typically carried out by a test manager.
decision table testing
test specification
test basis
test management
40. 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.
coverage item
independence of testing
test policy
defect tracking tool
41. The behavior produced/observed when a component or system is tested.
non-functional test design techniques
actual result
statement coverage
reviewer
42. The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.
branch coverage
instrumentation
recoverability testing
static code analysis
43. Decision rules used to determine whether a test item (function) or feature has passed or failed a test. [IEEE 829]
acceptance testing
performance indicator
pass/fail criteria
test data
44. The capability of the software product to adhere to standards - conventions or regulations in laws and similar prescriptions. [ISO 9126]
compliance
coverage analysis
statement testing
Capability Maturity Model Integration (CMMI)
45. A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark) - a user-manual - or an individual's specialized knowledge - but should not be the code. [Afte
quality
testing
oracle
smoke test
46. 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
big-bang testing
test schedule
resource utilization
defect based test design technique
47. Coverage measures based on the internal structure of a component or system.
black-box testing
structural coverage
non-functional testing
metric
48. A set of several test cases for a component or system under test - where the post condition of one test is often used as the precondition for the next one.
test suite
portability
syntax testing
Defect Detection Percentage (DDP)
49. The capability of the software product to enable modified software to be tested. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements - modified to make fut
Test Maturity Model (TMM)
user acceptance testing
defect management
testability
50. A type of integration testing in which software elements - hardware elements - or both are combined all at once into a component or an overall system - rather than in stages. [After IEEE 610] See also integration testing. Testing performed to expose
functionality testing
test process
big-bang testing
simulation