SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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. The percentage of equivalence partitions that have been exercised by a test suite.
master test plan
equivalence partition coverage
test specification technique
severity
2. All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by way of formal amendment procedure - then the test basis is called a frozen t
master test plan
black-box testing
test basis
deliverable
3. The capability of the software product to achieve acceptable levels of risk of harm to people - business - software - property or the environment in a specified context of use. [ISO 9126]
safety
false-fail result
installability
interface testing
4. The process of testing to determine the recoverability of a software product. See also reliability testing. The process of testing to determine the reliability of a software product.
test
test management
test implementation
recoverability testing
5. Operational testing by potential and/or existing users/customers at an external site not otherwise involved with the developers - to determine whether or not a component or system satisfies the user/customer needs and fits within the business process
memory leak
compatibility testing
N-switch coverage
beta testing
6. A path for which a set of input values and preconditions exists which causes it to be executed.
robustness testing
anomaly
feasible path
multiple condition testing
7. A tool that supports operational security.
regression testing
debugging tool
operability
security tool
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
isolation testing
Failure Mode and Effect Analysis (FMEA)
benchmark test
wild pointer
9. 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
pair programming
syntax testing
requirements management tool
Test Point Analysis (TPA)
10. 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
scripting language
quality assurance
test execution technique
frozen test basis
11. The degree of impact that a defect has on the development or operation of a component or system. [After IEEE 610]
input value
severity
memory leak
white-box test design technique
12. A risk directly related to the test object. See also risk. A factor that could result in future negative consequences; usually expressed as impact and likelihood.
use case testing
buffer overflow
product risk
incident logging
13. 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 - or structural element.
maintenance testing
orthogonal array
test condition
exit criteria
14. 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
operational acceptance testing
functional integration
integration
system of systems
15. A black box test design technique where test cases are selected - possibly using a pseudo-random generation algorithm - to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performa
deliverable
random testing
test target
use case testing
16. Acronym for Computer Aided Software Testing. See also test automation.The use of software to perform or support test activities - e.g. test management - test design - test execution and results checking.
static analyzer
test environment
performance testing
CAST
17. A systematic evaluation of software acquisition - supply - development - operation - or maintenance process - performed by or on behalf of management that monitors progress - determines the status of plans and schedules - confirms requirements and th
management review
efficiency
site acceptance testing
top-down testing
18. 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
technical review
instrumenter
memory leak
debugging tool
19. 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.
capture/replay tool
actual outcome
data flow testing
test schedule
20. 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.
test manager
exercised
quality
installation wizard
21. 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.
error guessing
blocked test case
continuous representation
input domain
22. 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.
syntax testing
path testing
version control
static code analyzer
23. 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.
resource utilization testing
pairwise testing
measurement
test management tool
24. The percentage of sequences of N+1 transitions that have been exercised by a test suite. [Chow]
installation wizard
test monitoring
black-box testing
N-switch coverage
25. A factor that could result in future negative consequences; usually expressed as impact and likelihood.
testing
software quality
pairwise testing
risk
26. A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing. Statistical testing using a model of system operations (short duration tasks)
statistical testing
compliance testing
risk analysis
decision testing
27. The process of running a test on the component or system under test - producing actual result(s).
technical review
instrumentation
test phase
test execution
28. 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
operational testing
LCSAJ coverage
risk level
29. A review of a software work product by colleagues of the producer of the product for the purpose of identifying defects and improvements. Examples are inspection - technical review and walkthrough.
bottom-up testing
Capability Maturity Model (CMM)
test level
peer review
30. An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members.
re-testing
CASE
Wide Band Delphi
continuous representation
31. 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]
configuration item
test design
system testing
compliance testing
32. A statement of test objectives - and possibly test ideas about how to test. Test charters are used in exploratory testing. See also exploratory testing. An informal test design technique where the tester actively controls the design of the tests as t
robustness testing
test charter
user acceptance testing
test procedure specification
33. 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
intake test
operational environment
reliability testing
34. A sequence of one or more consecutive executable statements containing no branches. Note: A node in a control flow graph represents a basic block.
control flow
integration
basic block
quality management
35. The data received from an external source by the test object during test execution. The external source can be hardware - software or human.
component
test input
data flow
actual result
36. A basic block that can be selected for execution based on a program construct in which one of two or more alternative program paths is available - e.g. case - jump - go to - if-then-else.
Failure Mode and Effect Analysis (FMEA)
functionality testing
changeability
branch
37. The process of recording information about tests executed into a test log.
Failure Mode - Effect and Criticality Analysis (FMECA)
changeability
test logging
incident management
38. Procedure used to derive and/or select test cases.
cost of quality
condition
entry criteria
test design technique
39. A development life cycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or external) of an executable product - a subset of the final product under dev
iterative development model
defect
coverage tool
interface testing
40. A review characterized by documented procedures and requirements - e.g. inspection.
formal review
resource utilization
unreachable code
syntax testing
41. A detailed check of the test basis to determine whether the test basis is at an adequate quality level to act as an input document for the test process. [After TMap]
operational acceptance testing
testability review
test harness
test management tool
42. 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.
specification
entry point
dynamic testing
Test Maturity Model Integrated (TMMi)
43. 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
level test plan
dynamic analysis tool
keyword driven testing
master test plan
44. An attribute of a component or system specified or implied by requirements documentation (for example reliability - usability or design constraints). [After IEEE 1008]
functionality
adaptability
component
feature
45. A white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes.
re-testing
scribe
non-conformity
decision condition testing
46. A tool that provides support for the identification and control of configuration items - their status over changes and versions - and the release of baselines consisting of configuration items.
configuration management tool
requirements-based testing
test policy
test session
47. A sequence of transactions in a dialogue between a user and the system with a tangible result.
functionality
metric
use case
defect tracking tool
48. A form of static analysis based on a representation of sequences of events (paths) in the execution through a component or system.
control flow analysis
technical review
defect
Failure Mode and Effect Analysis (FMEA)
49. 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.
efficiency testing
back-to-back testing
component
off-the-shelf software
50. Simulated or actual operational testing by potential users/customers or an independent test team at the developers' site - but outside the development organization. Alpha testing is often employed for off-the-shelf software as a form of internal acce
alpha testing
code
testing
error