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 condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract - standard - specification - or other formally imposed document. [After IEEE 610
qualification
requirement
co-existence
Function Point Analysis (FPA)
2. The process of testing to determine the resource-utilization of a software product. See also efficiency testing. The process of testing to determine the efficiency of a software product.
accessibility testing
scalability
user acceptance testing
resource utilization testing
3. 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 case suite
exhaustive testing
stability
performance indicator
4. Procedure to derive and/or select test cases based on the tester's experience - knowledge and intuition.
path sensitizing
experienced-based test design technique
process
testing
5. Computer instructions and data definitions expressed in a programming language or in a form output by an assembler - compiler or other translator. [IEEE 610]
use case testing
test scenario
integration testing
code
6. A set of interrelated activities - which transform inputs into outputs. [ISO 12207]
interoperability testing
software life cycle
equivalence partition coverage
process
7. 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
production acceptance testing
capture/replay tool
Capability Maturity Model (CMM)
condition testing
8. A path for which a set of input values and preconditions exists which causes it to be executed.
process cycle test
recovery testing
feasible path
exit criteria
9. 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
user test
procedure testing
risk analysis
testware
10. The percentage of paths that have been exercised by a test suite. 100% path coverage implies 100% LCSAJ coverage.
exploratory testing
condition outcome
path coverage
test policy
11. 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
orthogonal array testing
static testing
severity
defect
12. Testing based on an analysis of the internal structure of the component or system.
white-box testing
test logging
unit
memory leak
13. A tool that supports operational security.
multiple condition coverage
pairwise testing
informal review
security tool
14. The percentage of boundary values that have been exercised by a test suite.
data driven testing
wild pointer
boundary value coverage
static code analyzer
15. A questionnaire based usability test technique to evaluate the usability - e.g. user-satisfaction - of a component or system. [Veenendaal]
Software Usability Measurement Inventory (SUMI)
test execution tool
test data preparation tool
measure
16. A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified work loads - or with reduced availability of resources such as access to memory or servers. [After IEEE 610] See also pe
compound condition
N-switch testing
unit test framework
stress testing
17. The number or category assigned to an attribute of an entity by making a measurement. [ISO 14598]
measure
review
independence of testing
integration
18. A white box test design technique in which test cases are designed to execute single condition outcomes that independently affect a decision outcome.
test oracle
specification
state transition
condition determination testing
19. The testing of individual software components. [After IEEE 610]
learnability
component testing
test approach
testability review
20. A requirement that does not relate to functionality - but to attributes such as reliability - efficiency - usability - maintainability and portability.
feasible path
non-functional requirement
configuration
availability
21. 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
incident logging
test evaluation report
anomaly
incident management tool
22. A software tool used to carry out instrumentation.
incremental testing
error guessing
instrumenter
defect management
23. A form of static analysis based on a representation of sequences of events (paths) in the execution through a component or system.
test tool
control flow analysis
defect taxonomy
CASE
24. A black box test design technique in which test cases are designed from cause-effect graphs. [BS 7925/2]
test item
component testing
cause-effect graphing
Software Usability Measurement Inventory (SUMI)
25. 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
equivalence partition coverage
condition determination coverage
robustness
functional integration
26. 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]
defect management tool
incident management
configuration control
maintainability testing
27. A software product that supports one or more test activities - such as planning and control - specification - building initial files and data - test execution and test analysis. [TMap] See also CAST. Acronym for Computer Aided Software Testing.
output domain
fault seeding
test tool
control flow graph
28. The activity of establishing or updating a test plan.
test phase
benchmark test
test planning
requirement
29. Acronym for Computer Aided Software Engineering.
CASE
code
false-fail result
pair programming
30. 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]
subpath
software quality
state diagram
integration testing
31. 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
equivalence partitioning
high level test case
recoverability
big-bang testing
32. A software development approach whereby lines of code (production and/or test) of a component are written by two programmers sitting at a single computer. This implicitly means ongoing real-tim code reviews are performed.
classification tree method
pair programming
horizontal traceability
installation wizard
33. 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
availability
incident management tool
performance profiling
consistency
34. A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item - control changes to those characteristics - record and report change processi
review tool
configuration management
Failure Mode - Effect and Criticality Analysis (FMECA)
testability
35. Testing of software used to convert data from existing systems for use in replacement systems.
software life cycle
interoperability
specification
migration testing
36. An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members.
reliability testing
orthogonal array
Failure Mode - Effect and Criticality Analysis (FMECA)
Wide Band Delphi
37. 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.
COTS
probe effect
classification tree
security testing
38. 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
technical review
data driven testing
test objective
39. The percentage of all condition outcomes and decision outcomes that have been exercised by a test suite. 100% decision condition coverage implies both 100% condition coverage and 100% decision coverage.
compliance testing
decision condition coverage
process cycle test
state diagram
40. The process of testing to determine the interoperability of a software product.
compatibility testing
hazard analysis
test condition
quality assurance
41. The percentage of definition-use pairs that have been exercised by a test suite.
unit test framework
data flow coverage
horizontal traceability
path testing
42. A sequence of events - e.g. executable statements - of a component or system from an entry point to an exit point.
path
understandability
acceptance criteria
orthogonal array testing
43. Procedure used to derive and/or select test cases.
decision condition testing
testable requirements
resumption criteria
test specification technique
44. 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
frozen test basis
defect based test design technique
business process-based testing
efficiency
45. 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]
system
performance
interoperability
driver
46. 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
severity
defect report
audit
pairwise testing
47. A version of component integration testing where the progressive integration of components follows the implementation of subsets of the requirements - as opposed to the integration of components by levels of a hierarchy.
thread testing
co-existence
test infrastructure
wild pointer
48. Testing to determine the scalability of the software product.
scalability testing
exploratory testing
component
usability
49. Supplied instructions on any suitable media - which guides the installer through the installation process. This may be a manual guide - step-by-step procedure - installation wizard - or any other similar process description.
N-switch testing
benchmark test
certification
installation guide
50. 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.
white-box test design technique
test
Test Maturity Model Integrated (TMMi)
test data preparation tool