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. [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.
partition testing
reliability growth model
decision table
tester
2. The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.
hyperlink
smoke test
branch coverage
orthogonal array testing
3. 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
probe effect
compliance
measurement
4. 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]
test summary report
configuration control
test approach
test estimation
5. 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
adaptability
LCSAJ
outcome
horizontal traceability
6. 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)
daily build
failure mode
test procedure specification
7. The process of developing and prioritizing test procedures - creating test data and - optionally - preparing test harnesses and writing automated test scripts.
actual result
exit point
test implementation
failure rate
8. A scripting technique that stores test input and expected results in a table or spreadsheet - so that a single control script can execute all of the tests in the table. Data driven testing is often used to support the application of test execution to
site acceptance testing
requirements management tool
simulator
data driven testing
9. The percentage of LCSAJs of a component that have been exercised by a test suite. 100% LCSAJ coverage implies 100% decision coverage.
LCSAJ coverage
decision testing
ttractiveness
static code analysis
10. The process of testing to determine the performance of a software product. See also efficiency testing. The process of testing to determine the efficiency of a software product.
fault seeding
performance testing
monitor
low level test case
11. The testing activities that must be repeated when testing is re-started after a suspension. [After IEEE 829]
error guessing
resumption criteria
emulator
dynamic analysis tool
12. 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.
phase test plan
test case suite
instrumenter
root cause
13. The process through which decisions are reached and protective measures are implemented for reducing risks to - or maintaining risks within - specified levels.
risk control
safety critical system
review tool
certification
14. A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.
Test Point Analysis (TPA)
LCSAJ coverage
blocked test case
syntax testing
15. An approach to testing to reduce the level of product risks and inform stakeholders on their status - starting in the initial stages of a project. It involves the identification of product risks and their use in guiding the test process.
safety critical system
failure mode
functional integration
risk-based testing
16. Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. [ISO 9000]
input
product risk
component specification
validation
17. A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.
V-model
defect taxonomy
process
test specification
18. Recording the details of any incident that occurred - e.g. during testing.
configuration management tool
operational testing
incident logging
complexity
19. 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
walkthrough
N-switch testing
operational acceptance testing
scribe
20. 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.
pointer
efficiency
static code analyzer
project risk
21. 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.
coverage analysis
test tool
risk type
audit trail
22. 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
state table
test strategy
requirements-based testing
regression testing
23. A type of test tool that is able to execute other software using an automated test script - e.g. capture/playback. [Fewster and Graham]
test execution tool
test driven development
installability testing
wild pointer
24. Modification of a software product after delivery to correct defects - to improve performance or other attributes - or to adapt the product to a modified environment. [IEEE 1219]
process
maintenance
statement
black-box testing
25. A white box test design technique in which test cases are designed to execute LCSAJs.
LCSAJ testing
operational acceptance testing
scalability testing
testable requirements
26. The process of identifying risks using techniques such as brainstorming - checklists and failure history.
feasible path
risk identification
automated testware
mutation analysis
27. A defect in a program's dynamic store allocation logic that causes it to fail to reclaim memory after it has finished using it - eventually causing the program to fail due to lack of memory.
test execution tool
acceptance testing
memory leak
status accounting
28. The process of testing to determine the maintainability of a software product.
static analysis tool
failure mode
serviceability testing
pass
29. The process of recognizing - investigating - taking action and disposing of defects. It involves recording defects - classifying them and identifying the impact. [After IEEE 1044]
defect management
functional integration
capture/playback tool
learnability
30. Coordinated activities to direct and control an organization with regard to quality. Direction and control with regard to quality generally includes the establishment of the quality policy and quality objectives - quality planning - quality control -
tester
complexity
test object
quality management
31. 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]
quality
system integration testing
test script
fault seeding
32. 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]
documentation testing
dynamic analysis
acceptance criteria
condition determination testing
33. The representation of selected behavioral characteristics of one physical or abstract system by another system. [ISO 2382/1]
entry criteria
ad hoc testing
walkthrough
simulation
34. 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.
fault tolerance
intake test
qualification
exercised
35. An uninterrupted period of time spent in executing tests. In exploratory testing - each test session is focused on a charter - but testers can also explore new opportunities or issues during a session. The tester creates and executes test cases on th
test session
consistency
quality
test script
36. Testing to determine the scalability of the software product.
scalability testing
variable
peer review
priority
37. 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
configuration item
test reproduceability
Capability Maturity Model Integration (CMMI)
scalability
38. 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.
static code analyzer
pair testing
test progress report
pair programming
39. The set from which valid input and/or output values can be selected.
domain
functional test design technique
defect based test design technique
test harness
40. The percentage of sequences of N+1 transitions that have been exercised by a test suite. [Chow]
instrumentation
test phase
bespoke software
N-switch coverage
41. Testing in which two or more variants of a component or system are executed with the same inputs - the outputs compared - and analyzed in cases of discrepancies. [IEEE 610]
back-to-back testing
reliability testing
maintenance
test target
42. 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.
acceptance criteria
off-the-shelf software
robustness testing
portability testing
43. Testing of software or specification by manual simulation of its execution. See also static analysis. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.
CAST
wild pointer
desk checking
test design tool
44. The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) project's goal and the risk assessment carried out - starting points regarding the test process - the test design
black-box testing
test approach
Test Maturity Model Integrated (TMMi)
load profile
45. The first executable statement within a component.
partition testing
intake test
dynamic comparison
entry point
46. The process of combining components or systems into larger assemblies.
integration
state transition testing
entry criteria
COTS
47. The person responsible for project management of testing activities and resources - and evaluation of a test object. The individual who directs - controls - administers - plans and regulates the evaluation of a test object.
boundary value
verification
test manager
test
48. A development life cycle where a project is broken into a series of increments - each of which delivers a portion of the functionality in the overall project requirements. The requirements are prioritized and delivered in priority order in the approp
metric
reliability testing
incremental development model
path
49. Two or more single conditions joined by means of a logical operator (AND - OR or XOR) - e.g. 'A>B AND C>1000'.
compound condition
input value
quality
test driven development
50. During the test closure phase of a test process data is collected from completed activities to consolidate experience - testware - facts and numbers. The test closure phase consists of finalizing and archiving the testware and evaluating the test pro
test closure
multiple condition coverage
test execution tool
technical review