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. Separation of responsibilities - which encourages the accomplishment of objective testing. [After DO-178b]
functional testing
pseudo-random
independence of testing
efficiency testing
2. The process of testing to determine the interoperability of a software product.
input domain
equivalence partition
compatibility testing
state diagram
3. Procedure used to derive and/or select test cases.
false-fail result
test design technique
pass/fail criteria
functionality testing
4. A review not based on a formal (documented) procedure.
test design
informal review
quality
documentation testing
5. The data received from an external source by the test object during test execution. The external source can be hardware - software or human.
test basis
iterative development model
test input
status accounting
6. The percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies 100% condition determination coverage.
probe effect
test execution technique
multiple condition coverage
usability
7. The use of software - e.g. capture/playback tools - to control the execution of tests - the comparison of actual results to expected results - the setting up of test preconditions - and other test control and reporting functions.
test execution automation
operational profile testing
documentation testing
testability review
8. A pointer that references a location that is out of scope for that pointer or that does not exist. See also pointer. A data item that specifies the location of another data item; for example - a data item that specifies the address of the next employ
path testing
wild pointer
branch
review
9. A tool that provides support to the test management and control part of a test process. It often has several capabilities - such as testware management - scheduling of tests - the logging of results - progress tracking - incident management and test
Software Usability Measurement Inventory (SUMI)
test management tool
LCSAJ testing
Wide Band Delphi
10. 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
compliance
coverage
suitability
security testing
11. 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.
debugging tool
test suite
process improvement
negative testing
12. Testing carried out informally; no formal test preparation takes place - no recognized test design technique is used - there are no expectations for results and arbitrariness guides the test execution activity.
ad hoc testing
staged representation
variable
error
13. Acronym for Computer Aided Software Engineering.
CASE
test target
module
validation
14. A computational model consisting of a finite number of states and transitions between those states - possibly with accompanying actions. [IEEE 610]
Capability Maturity Model (CMM)
informal review
finite state machine
security testing tool
15. 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]
coverage analysis
component testing
partition testing
maintainability
16. 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.
safety critical system
decision condition coverage
output value
validation
17. The activity of establishing or updating a test plan.
operational acceptance testing
test planning
boundary value analysis
component integration testing
18. A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made - and to design tests specifically to expose them.
walkthrough
statement testing
pass
error guessing
19. 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.
component integration testing
equivalence partition coverage
boundary value
basis test set
20. A static usability test technique to determine the compliance of a user interface with recognized usability principles (the so-called "heuristics").
defect management tool
heuristic evaluation
volume testing
configuration management
21. 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.
classification tree method
system of systems
re-testing
mutation analysis
22. The representation of selected behavioral characteristics of one physical or abstract system by another system. [ISO 2382/1]
test execution
simulation
incremental development model
test monitoring
23. The percentage of paths that have been exercised by a test suite. 100% path coverage implies 100% LCSAJ coverage.
moderator
result
path coverage
security tool
24. 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
testability review
oracle
test tool
Software Usability Measurement Inventory (SUMI)
25. The capability of the software product to use appropriate amounts and types of resources - for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files - when the software performs its
resource utilization
daily build
state transition testing
compound condition
26. A test approach in which the test suite comprises all combinations of input values and preconditions.
expected result
exhaustive testing
hyperlink
control flow
27. A document that specifies - ideally in a complete - precise and verifiable manner - the requirements - design - behavior - or other characteristics of a component or system - and - often - the procedures for determining whether these provisions have
process
portability testing
specification
business process-based testing
28. Commonly used to refer to a test procedure specification - especially an automated one.
input domain
code coverage
test script
smoke test
29. 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]
state diagram
component specification
alpha testing
code coverage
30. 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
negative testing
result
certification
keyword driven testing
31. 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]
back-to-back testing
acceptance criteria
non-functional test design techniques
data definition
32. Non fulfillment of a specified requirement. [ISO 9000]
test item
condition outcome
iterative development model
non-conformity
33. A black box test design technique in which test cases are designed to execute valid and invalid state transitions. See also N-switch testing. A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 tr
state transition testing
interoperability testing
quality management
measurement scale
34. A Linear Code Sequence And Jump - consisting of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of executable statements - the end of the linear sequence - and the targe
false-pass result
test run
LCSAJ
incident
35. An entity in a programming language - which is typically the smallest indivisible unit of execution.
expected result
output
performance
statement
36. A white box test design technique in which test cases are designed to execute single condition outcomes that independently affect a decision outcome.
risk level
testware
condition determination testing
test control
37. A tool that carries out static analysis.
installation wizard
static analysis tool
incident management
adaptability
38. Procedure to derive and/or select test cases based on the tester's experience - knowledge and intuition.
requirements phase
maturity
experienced-based test design technique
test process
39. [Beizer] A black box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle test cases are designed to cover each partition at least once.
test environment
basis test set
output domain
partition testing
40. The fundamental test process comprises test planning and control - test analysis and design - test implementation and execution - evaluating exit criteria and reporting - and test closure activities.
test process
alpha testing
robustness
test level
41. A form of static analysis based on a representation of sequences of events (paths) in the execution through a component or system.
precondition
control flow analysis
LCSAJ
daily build
42. A transition between two states of a component or system.
fault tolerance
state table
incident
state transition
43. The number of independent paths through a program. Cyclomatic complexity is defined as: L - N + 2P - where - L = the number of edges/links in a graph - N = the number of nodes in a graph - P = the number of disconnected parts of the graph (e.g. a cal
condition coverage
cyclomatic complexity
production acceptance testing
suitability
44. An element of configuration management - consisting of the recording and reporting of information needed to manage a configuration effectively. This information includes a listing of the approved configuration identification - the status of proposed
automated testware
test management
false-fail result
status accounting
45. Testing conducted to evaluate a component or system in its operational environment. [IEEE 610]
CAST
classification tree
security tool
operational testing
46. Decision rules used to determine whether a test item (function) or feature has passed or failed a test. [IEEE 829]
pass/fail criteria
big-bang testing
path sensitizing
independence of testing
47. The composition of a component or system as defined by the number - nature - and interconnections of its constituent parts.
behavior
top-down testing
co-existence
configuration
48. A test tool to perform automated test comparison of actual results with expected results.
level test plan
test comparator
test infrastructure
qualification
49. A system whose failure or malfunction may result in death or serious injury to people - or loss or severe damage to equipment - or environmental harm.
accuracy
CASE
simulation
safety critical system
50. 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
variable
peer review
audit