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. Testing the attributes of a component or system that do not relate to functionality - e.g. reliability - efficiency - usability - maintainability and portability.
condition determination coverage
pair testing
re-testing
non-functional testing
2. A model structure wherein attaining the goals of a set of process areas establishes a maturity level; each level builds a foundation for subsequent levels. [CMMI]
structural coverage
statistical testing
negative testing
staged representation
3. (1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. See also Capability Maturity Model - Test Maturity Model. (2) The capability of the software product to avoid failure as a res
Failure Mode - Effect and Criticality Analysis (FMECA)
maturity
cause-effect graph
defect based test design technique
4. 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
pairwise testing
formal review
compatibility testing
module
5. 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
functionality testing
status accounting
stress testing
defect tracking tool
6. A human action that produces an incorrect result. [After IEEE 610]
test type
defect based test design technique
error
operational profile
7. Data that exists (for example - in a database) before a test is executed - and that affects or is affected by the component or system under test.
test schedule
equivalence partition coverage
test data
automated testware
8. Non fulfillment of a specified requirement. [ISO 9000]
best practice
non-conformity
stub
LCSAJ
9. The method used to perform the actual test execution - either manual or automated.
classification tree
usability testing
root cause
test execution technique
10. 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.
test case specification
mutation analysis
buffer overflow
configuration auditing
11. Testing of software used to convert data from existing systems for use in replacement systems.
deliverable
maintenance
migration testing
data definition
12. A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation - correction and re-testing of defects and provide reporting facilities.
defect tracking tool
non-functional testing
configuration identification
functional testing
13. The capability of the software product to enable the user to understand whether the software is suitable - and how it can be used for particular tasks and conditions of use. [ISO 9126] See also usability. The capability of the software to be understo
functionality
requirements management tool
vertical traceability
understandability
14. The process of testing an integrated system to verify that it meets specified requirements. [Hetzel]
requirements-based testing
risk analysis
system testing
technical review
15. The process of transforming general testing objectives into tangible test conditions and test cases.
simulator
path coverage
test design
postcondition
16. A program of activities designed to improve the performance and maturity of the organization's processes - and the result of such a program. [CMMI]
process improvement
defect taxonomy
performance testing tool
test harness
17. 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
availability
scripting language
LCSAJ
iterative development model
18. The tracing of requirements through the layers of development documentation to components.
cause-effect graph
vertical traceability
negative testing
capture/playback tool
19. The process of testing to determine the functionality of a software product.
functionality testing
compliance
feature
stress testing
20. A specification or software product that has been formally reviewed or agreed upon - that thereafter serves as the basis for further development - and that can be changed only through a formal change control process. [After IEEE 610]
test execution schedule
baseline
blocked test case
stability
21. The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage. [IEEE 610]
availability
failure
recoverability testing
non-functional testing
22. A software tool that translates programs expressed in a high order language into their machine language equivalents. [IEEE 610]
modelling tool
driver
risk management
compiler
23. The process of evaluating behavior - e.g. memory performance - CPU usage - of a system or component during execution. [After IEEE 610]
operational profile testing
coverage
simulator
dynamic analysis
24. 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
software quality
test execution
regression testing
test comparison
25. An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members.
test basis
requirements phase
test policy
Wide Band Delphi
26. A document specifying a set of test cases (objective - inputs - test actions - expected results - and execution preconditions) for a test item. [After IEEE 829]
coverage
test management
code-based testing
test case specification
27. A memory access defect due to the attempt by a process to store data beyond the boundaries of a fixed length buffer - resulting in overwriting of adjacent memory areas or the raising of an overflow exception. See also buffer. A device or storage area
classification tree
buffer overflow
test level
compliance
28. The physical or functional manifestation of a failure. For example - a system in failure mode may be characterized by slow operation - incorrect outputs - or complete termination of execution. [IEEE 610]
failure mode
risk type
LCSAJ
configuration management
29. 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
cyclomatic complexity
retrospective meeting
severity
measurement
30. 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
functional testing
negative testing
project risk
31. The process of identifying risks using techniques such as brainstorming - checklists and failure history.
performance indicator
continuous representation
operational profile
risk identification
32. 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]
process
test environment
test phase
test type
33. A test approach in which the test suite comprises all combinations of input values and preconditions.
stress testing
test control
input domain
exhaustive testing
34. 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.
metric
capture/replay tool
structural coverage
learnability
35. Computer instructions and data definitions expressed in a programming language or in a form output by an assembler - compiler or other translator. [IEEE 610]
audit trail
risk
code
expected result
36. Testing of software used to convert data from existing systems for use in replacement systems.
horizontal traceability
false-fail result
portability
conversion testing
37. The capability of the software product to be adapted for different specified environments without applying actions or means other than those provided for this purpose for the software considered. [ISO 9126] See also portability. The ease with which t
adaptability
failure
test approach
module
38. (1) A standard against which measurements or comparisons can be made. (2) A test that is be used to compare components or systems to each other or to a standard as in (1). [After IEEE 610]
test oracle
daily build
phase test plan
benchmark test
39. 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]
vertical traceability
component integration testing
failure rate
risk analysis
40. Acronym for Computer Aided Software Engineering.
CASE
decision condition coverage
statement coverage
equivalence partitioning
41. A measurement scale and the method used for measurement. [ISO 14598]
test comparison
system testing
metric
component integration testing
42. The capability of the software product to be used in place of another specified software product for the same purpose in the same environment. [ISO 9126] See also portability. The ease with which the software product can be transferred from one hardw
test process
replaceability
postcondition
compliance
43. The evaluation of a condition to True or False.
off-the-shelf software
safety critical system
condition outcome
pair programming
44. The testing of individual software components. [After IEEE 610]
buffer overflow
simulation
maintenance testing
component testing
45. A test tool to perform automated test comparison of actual results with expected results.
component integration testing
test comparison
test comparator
defect management
46. The process of recognizing - investigating - taking action and disposing of incidents. It involves logging incidents - classifying them and identifying the impact. [After IEEE 1044]
incident management
defect management
testware
test tool
47. The number or category assigned to an attribute of an entity by making a measurement. [ISO 14598]
postcondition
coverage item
measure
test run
48. Deviation of the component or system from its expected delivery - service or result. [After Fenton]
test session
configuration control board (CCB)
failure
robustness testing
49. A high level document describing the principles - approach and major objectives of the organization regarding testing.
test level
measure
test infrastructure
test policy
50. 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]
staged representation
result
reliability
attack