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. The last executable statement within a component.
database integrity testing
exit point
configuration
test control
2. A document that consists of a test design specification - test case specification and/or test procedure specification.
Wide Band Delphi
postcondition
output domain
test specification
3. A distinct set of test activities collected into a manageable phase of a project - e.g. the execution activities of a test level. [After Gerrard]
negative testing
test phase
risk-based testing
Test Maturity Model Integrated (TMMi)
4. A black box test design technique where test cases are selected - possibly using a pseudo-random generation algorithm - to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performa
volume testing
random testing
defect
incremental testing
5. A white box test design technique in which test cases are designed to execute condition outcomes.
recoverability testing
elementary comparison testing
alpha testing
condition testing
6. An element of storage in a computer that is accessible by a software program by referring to it by a name.
variable
volume testing
test run
exit point
7. Directed and focused attempt to evaluate the quality - especially reliability - of a test object by attempting to force specific failures to occur.
acceptance testing
performance testing tool
risk identification
attack
8. An integration approach that combines the components or systems for the purpose of getting a basic functionality working early. See also integration testing. Testing performed to expose defects in the interfaces and in the interactions between integr
functional integration
equivalence partition
security testing
testware
9. 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]
test planning
testable requirements
risk type
monitor
10. The process of testing an integrated system to verify that it meets specified requirements. [Hetzel]
system testing
integration
pairwise testing
software
11. Operational testing in the acceptance test phase - typically performed in a simulated real-life operational environment by operator and/or administrator focusing on operational aspects - e.g. recoverability - resource-behavior - installability and te
buffer
production acceptance testing
iterative development model
volume testing
12. A set of test cases derived from the internal structure of a component or specification to ensure that 100% of a specified coverage criterion will be achieved.
basis test set
Capability Maturity Model (CMM)
cost of quality
LCSAJ testing
13. A questionnaire based usability test technique to evaluate the usability - e.g. user-satisfaction - of a component or system. [Veenendaal]
compound condition
Software Usability Measurement Inventory (SUMI)
exercised
exit point
14. The process of assigning a number or category to an entity to describe an attribute of that entity. [ISO 14598]
recoverability
measurement
unreachable code
test planning
15. A tool that carries out static analysis.
driver
static analyzer
LCSAJ testing
certification
16. The tracing of requirements for a test level through the layers of test documentation (e.g. test plan - test design specification - test case specification and test procedure specification or test script).
expected result
performance profiling
decision
horizontal traceability
17. The process of confirming that a component - system or person complies with its specified requirements - e.g. by passing an exam.
risk-based testing
certification
data flow coverage
installability testing
18. An extension of FMEA - as in addition to the basic FMEA - it includes a criticality analysis - which is used to chart the probability of failure modes against the severity of their consequences. The result highlights failure modes with relatively hig
release note
decision table testing
stress testing tool
Failure Mode - Effect and Criticality Analysis (FMECA)
19. A test whereby real-life users are involved to evaluate the usability of a component or system.
stub
risk level
path testing
user test
20. 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
risk control
maintainability testing
component integration testing
incident management tool
21. A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.
retrospective meeting
classification tree
release note
state transition testing
22. A set of input values - execution preconditions - expected results and execution postconditions - developed for a particular objective or test condition - such as to exercise a particular program path or to verify compliance with a specific requireme
non-functional test design techniques
test process
learnability
test case
23. An input for which the specification predicts a result.
beta testing
test specification technique
specified input
behavior
24. Testing conducted to evaluate a component or system in its operational environment. [IEEE 610]
test strategy
integration
volume testing
operational testing
25. The consequence/outcome of the execution of a test. It includes outputs to screens - changes to data - reports - and communication messages sent out.
interoperability
development testing
outcome
dynamic comparison
26. A document describing the scope - approach - resources and schedule of intended test activities. It identifies amongst others test items - the features to be tested - the testing tasks - who will do each task - degree of tester independence - the tes
keyword driven testing
test execution schedule
classification tree method
test plan
27. Measurement of achieved coverage to a specified coverage item during test execution referring to predetermined criteria to determine whether additional testing is required and if so - which test cases are needed.
coverage analysis
equivalence partition coverage
data flow
emulator
28. The person involved in the review that identifies and describes anomalies in the product or project under review. Reviewers can be chosen to represent different viewpoints and roles in the review process.
Failure Mode - Effect and Criticality Analysis (FMECA)
version control
reviewer
control flow
29. A list of activities - tasks or events of the test process - identifying their intended start and finish dates and/or times - and interdependencies.
incident
test schedule
exit point
mutation analysis
30. The percentage of executable statements that have been exercised by a test suite.
statement coverage
Fault Tree Analysis (FTA)
requirements management tool
tester
31. A type of test tool that enables data to be selected from existing databases or created - generated - manipulated and edited for use in testing.
test data preparation tool
compliance
defect management tool
test driven development
32. The total costs incurred on quality activities and issues and often split into prevention costs - appraisal costs - internal failure costs and external failure costs.
installation wizard
cost of quality
static analysis tool
test condition
33. A sequence of events (paths) in the execution through a component or system.
cause-effect graphing
control flow
module
data flow
34. Procedure used to derive and/or select test cases.
test specification technique
input value
measurement scale
incremental development model
35. The capability of the software product to co-exist with other independent software in a common environment sharing common resources. [ISO 9126] See also portability. The ease with which the software product can be transferred from one hardware or sof
stress testing tool
requirement
operational profile
co-existence
36. 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)
feasible path
error tolerance
statistical testing
testability
37. A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.
test management tool
keyword driven testing
capture/playback tool
component
38. The degree of uniformity - standardization - and freedom from contradiction among the documents or parts of a component or system. [IEEE 610]
verification
quality management
consistency
technical review
39. A requirement that does not relate to functionality - but to attributes such as reliability - efficiency - usability - maintainability and portability.
non-functional requirement
stress testing
decision outcome
defect management
40. 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.
test objective
classification tree
probe effect
test comparison
41. A specification of the activity which a component or system being tested may experience in production. A load profile consists of a designated number of virtual users who process a defined set of transactions in a specified time period and according
load profile
test design technique
incident report
system of systems
42. The ability of the software product to perform its required functions under stated conditions for a specified period of time - or for a specified number of operations. [ISO 9126]
condition coverage
validation
reliability
LCSAJ testing
43. A special instance of a smoke test to decide if the component or system is ready for detailed and further testing. An intake test is typically carried out at the start of the test execution phase. See also smoke test. A subset of all defined/planned
code-based testing
intake test
continuous representation
changeability
44. A high level document describing the principles - approach and major objectives of the organization regarding testing.
severity
defect report
entry point
test policy
45. Testing based on an analysis of the internal structure of the component or system.
code-based testing
audit
test procedure
variable
46. A test approach in which the test suite comprises all combinations of input values and preconditions.
concurrency testing
security testing
test performance indicator
exhaustive testing
47. Testing - either functional or non-functional - without reference to the internal structure of the component or system. Black-box test design technique Procedure to derive and/or select test cases based on an analysis of the specification - either fu
black-box testing
statement coverage
test process
test closure
48. 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]
integration testing
exhaustive testing
safety
maintenance
49. A group of people responsible for evaluating and approving or disapproving proposed changes to configuration items - and for ensuring implementation of approved changes. [IEEE 610]
installation wizard
path
metric
configuration control board (CCB)
50. The behavior produced/observed when a component or system is tested.
fault seeding tool
actual result
functionality testing
performance testing