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 document produced at the end of the test process summarizing all testing activities and results. It also contains an evaluation of the test process and lessons learned.
test evaluation report
hyperlink tool
deliverable
simulation
2. The ease with which a software product can be modified to correct defects - modified to meet new requirements - modified to make future maintenance easier - or adapted to a changed environment. [ISO 9126]
finite state machine
exit criteria
maintainability
project risk
3. Testing the quality of the documentation - e.g. user guide or installation guide.
requirements phase
state transition
documentation testing
configuration management
4. The capability of the software product to enable the user to operate and control it. [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
path sensitizing
pseudo-random
operability
decision table
5. A scripting technique that uses data files to contain not only test data and expected results - but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control scrip
test phase
actual outcome
measurement
keyword driven testing
6. The process of transforming general testing objectives into tangible test conditions and test cases.
load profile
cause-effect graph
system of systems
test design
7. A test whereby real-life users are involved to evaluate the usability of a component or system.
retrospective meeting
acceptance criteria
maturity
user test
8. 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
frozen test basis
defect
acceptance criteria
classification tree
9. 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
co-existence
test design
test case specification
state diagram
10. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes.
data flow coverage
business process-based testing
orthogonal array testing
deliverable
11. The process of demonstrating the ability to fulfill specified requirements. Note the term 'qualified' is used to designate the corresponding status. [ISO 9000]
test input
qualification
basis test set
review tool
12. The process through which decisions are reached and protective measures are implemented for reducing risks to - or maintaining risks within - specified levels.
expected result
defect report
risk control
testability
13. Procedure to derive and/or select test cases based on the tester's experience - knowledge and intuition.
path
experienced-based test design technique
understandability
quality assurance
14. Testing that runs test cases that failed the last time they were run - in order to verify the success of corrective actions.
bespoke software
re-testing
condition determination coverage
definition-use pair
15. Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled. [ISO 9000]
verification
Wide Band Delphi
decision table
test implementation
16. A test plan that typically addresses one test level. See also test plan. 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 testin
level test plan
dynamic testing
continuous representation
configuration management
17. A logical expression that can be evaluated as True or False - e.g. A>B. See also test condition. An item or event of a component or system that could be verified by one or more test cases - e.g. a function - transaction - feature - quality attribute
condition
review
postcondition
integration testing
18. A tool that provides support to the review process. Typical features include review planning and tracking support - communication support - collaborative reviews and a repository for collecting and reporting of metrics.
review tool
white-box test design technique
incident report
finite state machine
19. A white box test design technique in which test cases are designed to execute definition and use pairs of variables.
resource utilization testing
data flow testing
exploratory testing
test data
20. 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.
condition coverage
syntax testing
LCSAJ coverage
product risk
21. A reason or purpose for designing and executing a test.
test objective
basis test set
input
security
22. An entity or property used as a basis for test coverage - e.g. equivalence partitions or code statements.
coverage item
instrumenter
iterative development model
volume testing
23. The use of software to perform or support test activities - e.g. test management - test design - test execution and results checking.
test management tool
feature
code coverage
test automation
24. The process of testing to determine the interoperability of a software product. See also functionality testing. The process of testing to determine the functionality of a software product.
definition-use pair
interoperability testing
test design tool
mutation analysis
25. A form of static analysis based on the definition and usage of variables.
defect
data flow analysis
configuration auditing
exception handling
26. The degree to which a component - system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610]
test design specification
cyclomatic complexity
system testing
quality
27. 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.
modelling tool
daily build
black-box test design technique
top-down testing
28. The capability of the software product to interact with one or more specified components or systems. [After ISO 9126] See also functionality. The capability of the software product to provide functions which meet stated and implied needs when the sof
interoperability
condition determination coverage
configuration management tool
configuration auditing
29. A sequence of one or more consecutive executable statements containing no branches. Note: A node in a control flow graph represents a basic block.
cause-effect graphing
basic block
risk type
variable
30. 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.
condition testing
master test plan
volume testing
scribe
31. Computer instructions and data definitions expressed in a programming language or in a form output by an assembler - compiler or other translator. [IEEE 610]
path testing
partition testing
code
horizontal traceability
32. Statistical testing using a model of system operations (short duration tasks) and their probability of typical use. [Musa]
hyperlink
modelling tool
operational profile testing
compliance testing
33. The function to check on the contents of libraries of configuration items - e.g. for standards compliance. [IEEE 610]
exhaustive testing
test infrastructure
configuration auditing
smoke test
34. A method to determine test suite thoroughness by measuring the extent to which a test suite can discriminate the program from slight variants (mutants) of the program.
decision outcome
mutation analysis
test summary report
installability
35. The process of evaluating behavior - e.g. memory performance - CPU usage - of a system or component during execution. [After IEEE 610]
dynamic analysis
operability
condition testing
maintenance testing
36. 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
deliverable
functional testing
fail
test case suite
37. 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
security testing
component integration testing
test plan
exit criteria
38. A high level metric of effectiveness and/or efficiency used to guide and control progressive test development - e.g. Defect Detection Percentage (DDP).
deliverable
test execution technique
test performance indicator
test design
39. An element of configuration management - consisting of selecting the configuration items for a system and recording their functional and physical characteristics in technical documentation. [IEEE 610]
configuration identification
input domain
test approach
basis test set
40. A variable (whether stored within a component or outside) that is read by a component.
technical review
test process
input
test specification
41. Testing practice for a project using agile methodologies - such as extreme programming (XP) - treating development as the customer of testing and emphasizing the test first design paradigm. See also test driven development. A way of developing softwa
path
agile testing
quality
Defect Detection Percentage (DDP)
42. 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].
CASE
back-to-back testing
invalid testing
capture/playback tool
43. 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.
test execution automation
static code analyzer
acceptance testing
test type
44. 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
usability testing
functional integration
boundary value analysis
performance profiling
45. 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]
ttractiveness
configuration control
test object
exit criteria
46. The insertion of additional code into the program in order to collect information about program behavior during execution - e.g. for measuring code coverage.
actual outcome
black-box testing
control flow graph
instrumentation
47. The percentage of all single condition outcomes that independently affect a decision outcome that have been exercised by a test case suite. 100% condition determination coverage implies 100% decision condition coverage.
test cycle
testable requirements
specification
condition determination coverage
48. 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
retrospective meeting
incident
impact analysis
intake test
49. An attribute of a test indicating whether the same results are produced each time the test is executed.
measurement
test reproduceability
resource utilization
oracle
50. 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
requirements management tool
operational profile testing
procedure testing
process