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 software tool that translates programs expressed in a high order language into their machine language equivalents. [IEEE 610]
analyzability
compatibility testing
reliability testing
compiler
2. Formal or informal testing conducted during the implementation of a component or system - usually in the development environment by developers. [After IEEE 610]
configuration control
stub
development testing
integration
3. 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
statistical testing
component integration testing
risk control
4. The process of evaluating behavior - e.g. memory performance - CPU usage - of a system or component during execution. [After IEEE 610]
mutation analysis
dynamic analysis
independence of testing
test run
5. Part of quality management focused on providing confidence that quality requirements will be fulfilled. [ISO 9000]
path
quality assurance
unit test framework
bottom-up testing
6. A review not based on a formal (documented) procedure.
informal review
testable requirements
defect management tool
test design technique
7. The consequence/outcome of the execution of a test. It includes outputs to screens - changes to data - reports - and communication messages sent out.
outcome
test approach
buffer overflow
performance
8. Testing the quality of the documentation - e.g. user guide or installation guide.
random testing
documentation testing
Wide Band Delphi
test design tool
9. A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and Graham - IEEE 1028] See also peer review. A review of a software work product by colleagues of the producer of the product for the p
verification
big-bang testing
coverage
technical review
10. A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]
test summary report
best practice
test script
black-box testing
11. The process of assessing identified risks to estimate their impact and probability of occurrence (likelihood).
master test plan
risk analysis
severity
functionality testing
12. 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
resource utilization
equivalence partition coverage
cyclomatic complexity
data flow
13. Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. [ISO 9000]
validation
defect
resource utilization
test specification
14. Testing to determine how the occurrence of two or more activities within the same interval of time - achieved either by interleaving the activities or by simultaneous execution - is handled by the component or system. [After IEEE 610]
recoverability testing
concurrency testing
risk management
static code analyzer
15. 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
staged representation
big-bang testing
interoperability testing
dynamic testing
16. A document specifying a set of test cases (objective - inputs - test actions - expected results - and execution preconditions) for a test item. [After IEEE 829]
structural coverage
dynamic analysis tool
boundary value coverage
test case specification
17. Testing to determine the ease by which users with disabilities can use a component or system. [Gerrard]
test strategy
top-down testing
database integrity testing
accessibility testing
18. An environment containing hardware - instrumentation - simulators - software tools - and other support elements needed to conduct a test. [After IEEE 610]
suitability
test environment
test design technique
domain
19. A white box test design technique in which test cases are designed to execute LCSAJs.
performance
LCSAJ testing
integration
condition testing
20. Code that cannot be reached and therefore is impossible to execute.
defect density
unreachable code
fault seeding tool
regression testing
21. Testing where components or systems are integrated and tested one or some at a time - until all the components or systems are integrated and tested.
incremental testing
project risk
severity
bottom-up testing
22. 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).
defect management tool
horizontal traceability
deliverable
security tool
23. The period of time that begins when a software product is conceived and ends when the software is no longer available for use. The software life cycle typically includes a concept phase - requirements phase - design phase - implementation phase - tes
software life cycle
test summary report
stub
test design technique
24. The ratio of the number of failures of a given category to a given unit of measure - e.g. failures per unit of time - failures per number of transactions - failures per number of computer runs. [IEEE 610]
test phase
co-existence
requirements phase
failure rate
25. Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software - as a result of the changes made. It is performed when the software or its environment is c
development testing
test design technique
regression testing
test session
26. 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.
top-down testing
condition coverage
test execution phase
ad hoc testing
27. The percentage of equivalence partitions that have been exercised by a test suite.
statement testing
test script
orthogonal array testing
equivalence partition coverage
28. A test tool to perform automated test comparison of actual results with expected results.
monitor
multiple condition coverage
test automation
test comparator
29. A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.
syntax testing
volume testing
LCSAJ coverage
test log
30. 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
Test Point Analysis (TPA)
learnability
fault seeding
functional testing
31. A program element is said to be exercised by a test case when the input value causes the execution of that element - such as a statement - decision - or other structural element.
orthogonal array testing
stability
Test Point Analysis (TPA)
exercised
32. The percentage of definition-use pairs that have been exercised by a test suite.
data flow coverage
quality attribute
test
audit trail
33. The process of intentionally adding known defects to those already in the component or system for the purpose of monitoring the rate of detection and removal - and estimating the number of remaining defects. [IEEE 610]
maturity
resource utilization
fault seeding
multiple condition coverage
34. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.
variable
static analysis
testability review
configuration control
35. The percentage of LCSAJs of a component that have been exercised by a test suite. 100% LCSAJ coverage implies 100% decision coverage.
test case suite
configuration item
process improvement
LCSAJ coverage
36. The set from which valid output values can be selected. See also domain. The set from which valid input and/or output values can be selected.
output domain
equivalence partitioning
statement coverage
white-box testing
37. A black box test design technique in which test cases are designed to execute user scenarios.
test level
use case testing
executable statement
path sensitizing
38. Testing of software used to convert data from existing systems for use in replacement systems.
installability testing
coverage
migration testing
code coverage
39. An instance of an output. See also output.A variable (whether stored within a component or outside) that is written by a component.
output value
safety testing
configuration management tool
back-to-back testing
40. The process of confirming that a component - system or person complies with its specified requirements - e.g. by passing an exam.
database integrity testing
resource utilization
configuration management
certification
41. 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.
code coverage
data flow analysis
test tool
decision coverage
42. A test environment comprised of stubs and drivers needed to execute a test.
test harness
cause-effect graph
condition
state transition
43. 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.
changeability
test process
acceptance testing
unreachable code
44. 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
test case suite
LCSAJ coverage
testability review
wild pointer
45. Any event occurring that requires investigation. [After IEEE 1008]
syntax testing
test phase
off-the-shelf software
incident
46. 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]
cost of quality
configuration item
high level test case
testware
47. The process of assigning a number or category to an entity to describe an attribute of that entity. [ISO 14598]
classification tree
incident logging
measurement
operational profile testing
48. Directed and focused attempt to evaluate the quality - especially reliability - of a test object by attempting to force specific failures to occur.
attack
statement
smoke test
white-box test design technique
49. 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
condition determination testing
black-box testing
safety
COTS
50. 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
experienced-based test design technique
Capability Maturity Model Integration (CMMI)
walkthrough
component