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. Modification of a software product after delivery to correct defects - to improve performance or other attributes - or to adapt the product to a modified environment. [IEEE 1219]
test cycle
Capability Maturity Model Integration (CMMI)
maintenance
efficiency
2. 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)
quality assurance
path coverage
site acceptance testing
3. 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
user acceptance testing
serviceability testing
Defect Detection Percentage (DDP)
management review
4. A black box test design technique in which test cases are designed to execute combinations of inputs using the concept of condition determination coverage. [TMap]
elementary comparison testing
interoperability testing
debugging
false-pass result
5. 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.
Test Maturity Model Integrated (TMMi)
test execution phase
unit testing
pairwise testing
6. The level of (business) importance assigned to an item - e.g. defect.
test reproduceability
priority
multiple condition testing
testing
7. 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. See also incid
risk analysis
priority
pair testing
defect management tool
8. 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.
resumption criteria
Capability Maturity Model (CMM)
decision coverage
master test plan
9. A program of activities designed to improve the performance and maturity of the organization's processes - and the result of such a program. [CMMI]
configuration management tool
process improvement
multiple condition testing
software life cycle
10. A framework to describe the software development life cycle activities from requirements specification to maintenance. The V-model illustrates how testing activities can be integrated into each phase of the software development life cycle.
V-model
state transition
configuration management
behavior
11. A five level staged framework that describes the key elements of an effective software process. The Capability Maturity Model covers best-practices for planning - engineering and managing software development and maintenance. [CMM] See also Capabilit
Capability Maturity Model (CMM)
finite state machine
reliability growth model
isolation testing
12. Analysis of source code carried out without execution of that software.
infeasible path
static code analysis
defect density
severity
13. The process of identifying differences between the actual results produced by the component or system under test and the expected results for a test. Test comparison can be performed during test execution (dynamic comparison) or after test execution.
input value
project risk
dynamic testing
test comparison
14. The percentage of boundary values that have been exercised by a test suite.
false-fail result
executable statement
boundary value coverage
structural coverage
15. A requirement that does not relate to functionality - but to attributes such as reliability - efficiency - usability - maintainability and portability.
usability
quality assurance
CASE
non-functional requirement
16. An integration test type that is concerned with testing the interfaces between components or systems.
branch
configuration management tool
incident management tool
interface testing
17. 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.
performance testing tool
requirements-based testing
risk identification
project
18. The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires each single condition in every decision statement to be tested as True and False.
unit
condition coverage
condition testing
ttractiveness
19. The first executable statement within a component.
output
cause-effect graphing
entry point
recoverability testing
20. 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.
desk checking
test run
intake test
installability testing
21. A factor that could result in future negative consequences; usually expressed as impact and likelihood.
behavior
risk
LCSAJ
load testing
22. A diagram that depicts the states that a component or system can assume - and shows the events or circumstances that cause and/or result from a change from one state to another. [IEEE 610]
configuration control board (CCB)
bottom-up testing
buffer
state diagram
23. A test basis document that can only be amended by a formal change control process. See also baseline. A specification or software product that has been formally reviewed or agreed upon - that thereafter serves as the basis for further development - a
maintenance testing
frozen test basis
output value
mutation analysis
24. The representation of a distinct set of tasks performed by the component or system - possibly based on user behavior when interacting with the component or system - and their probabilities of occurance. A task is logical rather that physical and can
emulator
operational profile
coverage analysis
testable requirements
25. 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)
subpath
statistical testing
compliance testing
test input
26. 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
failure mode
load testing
exploratory testing
risk analysis
27. 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.
static code analyzer
error guessing
audit trail
decision coverage
28. An instance of an output. See also output.A variable (whether stored within a component or outside) that is written by a component.
risk control
test performance indicator
replaceability
output value
29. 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]
big-bang testing
release note
boundary value analysis
unit testing
30. An abstract representation of the sequence and possible changes of the state of data objects - where the state of an object is any of: creation - usage - or destruction. [Beizer]
data flow
orthogonal array
production acceptance testing
risk analysis
31. Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers - to determine whether or not a component or system satisfies the user/customer needs and fits within the business process
defect management tool
path sensitizing
Defect Detection Percentage (DDP)
beta testing
32. An approach to testing in which test cases are designed based on the architecture and/or detailed design of a component or system (e.g. tests of interfaces between components or systems).
design-based testing
intake test
CASE
test basis
33. 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.
buffer
robustness testing
N-switch testing
test suite
34. An aggregation of hardware - software or both - that is designated for configuration management and treated as a single entity in the configuration management process. [IEEE 610]
test suite
configuration item
efficiency testing
review tool
35. Procedure used to derive and/or select test cases.
test design technique
test implementation
risk analysis
compliance testing
36. The percentage of paths that have been exercised by a test suite. 100% path coverage implies 100% LCSAJ coverage.
independence of testing
project risk
path coverage
simulation
37. A reason or purpose for designing and executing a test.
efficiency
test objective
high level test case
subpath
38. A black box test design technique in which test cases are designed to execute user scenarios.
regression testing
requirements-based testing
test monitoring
use case testing
39. A test is deemed to fail if its actual result does not match its expected result.
attack
release note
fail
exercised
40. A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content. [Freedman and Weinberg - IEEE 1028] See also peer review. A review of a software work product by colleagues
infeasible path
capture/replay tool
walkthrough
test input
41. Testing using input values that should be rejected by the component or system. See also error tolerance. The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After IEEE 610].
configuration management tool
state transition testing
invalid testing
safety testing
42. The response of a component or system to a set of input values and preconditions.
behavior
probe effect
exhaustive testing
coverage
43. A test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned. See also test management. The planning - estimating - monitoring and co
security
horizontal traceability
suitability
test control
44. A tool for seeding (i.e. intentionally inserting) faults in a component or system.
fault seeding tool
decision condition testing
LCSAJ
decision coverage
45. The tracing of requirements through the layers of development documentation to components.
vertical traceability
path testing
maturity
performance
46. The exit criteria that a component or system must satisfy in order to be accepted by a user - customer - or other authorized entity. [IEEE 610]
data driven testing
exit criteria
test harness
acceptance criteria
47. Testing where the system is subjected to large volumes of data. See also resource-utilization testing. The process of testing to determine the resource-utilization of a software product.
changeability
volume testing
compliance testing
test execution automation
48. 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.
operational environment
input value
security testing tool
error tolerance
49. Comparison of actual and expected results - performed while the software is being executed - for example by a test execution tool.
state diagram
dynamic comparison
exhaustive testing
adaptability
50. The process of testing to determine the recoverability of a software product. See also reliability testing. The process of testing to determine the reliability of a software product.
entry point
test
recoverability testing
N-switch coverage