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 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
risk identification
thread testing
requirement
2. 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
infeasible path
product risk
path testing
3. A point in time in a project at which defined (intermediate) deliverables and results should be ready.
test execution technique
milestone
ttractiveness
hazard analysis
4. An executable statement where a variable is assigned a value.
vertical traceability
unit
intake test
data definition
5. 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
user test
memory leak
regression testing
component integration testing
6. The percentage of all single condition outcomes that independently affect a decision outcome that have been exercised by a test case suite. 100% condition determination coverage implies 100% decision condition coverage.
condition determination coverage
functionality testing
exit point
site acceptance testing
7. Testing based on an analysis of the internal structure of the component or system.
testware
code-based testing
unreachable code
management review
8. 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.
heuristic evaluation
concurrency testing
static code analyzer
keyword driven testing
9. The process of transforming general testing objectives into tangible test conditions and test cases.
acceptance criteria
risk analysis
test design
definition-use pair
10. A tool that provides an environment for unit or component testing in which a component can be tested in isolation or with suitable stubs and drivers. It also provides other support for the developer - such as debugging capabilities. [Graham]
classification tree
risk level
unit test framework
risk control
11. A tool that carries out static analysis.
static analysis tool
oracle
pairwise testing
static analyzer
12. The testing of individual software components. [After IEEE 610]
component testing
robustness
dynamic analysis tool
maintenance testing
13. A black box test design technique in which test cases are designed to execute combinations of inputs using the concept of condition determination coverage. [TMap]
test harness
elementary comparison testing
input
test procedure specification
14. 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]
basis test set
fault seeding
top-down testing
operational environment
15. 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]
testability review
recoverability
operational profile
orthogonal array testing
16. Procedure to derive and/or select test cases for nonfunctional testing based on an analysis of the specification of a component or system without reference to its internal structure. See also black box test design technique. Procedure to derive and/o
acceptance testing
release note
non-functional test design techniques
functionality
17. Supplied software on any suitable media - which leads the installer through the installation process. It normally runs the installation process - provides feedback on installation results - and prompts for options.
priority
installation wizard
phase test plan
qualification
18. Testing to determine the scalability of the software product.
integration testing
multiple condition coverage
equivalence partitioning
scalability testing
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
operational acceptance testing
test item
testing
load testing
20. Acronym for Commercial Off-The-Shelf software. See off-the-shelf software. 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.
Test Process Improvement (TPI)
COTS
security
walkthrough
21. The capability of the software product to be installed in a specified environment [ISO 9126]. See also portability. The ease with which the software product can be transferred from one hardware or software environment to another. [ISO 9126]
operational profile testing
white-box testing
installability
equivalence partitioning
22. The percentage of equivalence partitions that have been exercised by a test suite.
failure mode
Fault Tree Analysis (FTA)
best practice
equivalence partition coverage
23. A white box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).
multiple condition testing
quality management
coverage item
testware
24. Execution of the test process against a single identifiable release of the test object.
validation
expected result
test cycle
exception handling
25. 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)
pair programming
requirement
statistical testing
risk analysis
26. An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed - e.g. statement coverage - decision coverage or condition coverage.
top-down testing
code coverage
resource utilization testing
installability testing
27. Computer programs - procedures - and possibly associated documentation and data pertaining to the operation of a computer system. [IEEE 610]
software
test level
performance indicator
best practice
28. Commonly used to refer to a test procedure specification - especially an automated one.
cyclomatic complexity
test script
error guessing
installability
29. 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
project
data flow
moderator
30. A tool used by programmers to reproduce failures - investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs step by step - to halt a program at any program statement and to set and examine
testability
test data preparation tool
dynamic analysis tool
debugging tool
31. An element of storage in a computer that is accessible by a software program by referring to it by a name.
technical review
risk level
management review
variable
32. An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review - informal review - technical review - inspection - and walkthrough. [After IEEE 1028]
replaceability
error guessing
coverage
review
33. The use of software to perform or support test activities - e.g. test management - test design - test execution and results checking.
test automation
test target
defect management tool
test
34. The process of testing to determine the portability of a software product.
portability testing
functionality
test design technique
test harness
35. Acceptance testing by users/customers at their site - to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes - normally including hardware as well as software.
error guessing
release note
instrumenter
site acceptance testing
36. A capability maturity model structure wherein capability levels provide a recommended order for approaching process improvement within specified process areas. [CMMI]
continuous representation
load testing
tester
maintenance testing
37. 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
LCSAJ coverage
decision condition coverage
portability testing
test basis
38. A type of test tool that is able to execute other software using an automated test script - e.g. capture/playback. [Fewster and Graham]
exploratory testing
serviceability testing
test execution tool
defect based test design technique
39. 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.
safety critical system
quality management
test data
qualification
40. The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions. [IEEE 610] See also error-tolerance - fault-tolerance. The ability of a system or component to continue normal o
scribe
security testing
robustness
intake test
41. Testing the changes to an operational system or the impact of a changed environment to an operational system.
decision condition coverage
test planning
pairwise testing
maintenance testing
42. The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate. [After IEEE 610] See also efficiency. The capability of the software product to provide appropriat
performance
defect masking
requirements management tool
incident
43. The process of assessing identified risks to estimate their impact and probability of occurrence (likelihood).
resumption criteria
usability testing
risk analysis
ttractiveness
44. A test result in which a defect is reported although no such defect actually exists in the test object.
exploratory testing
quality management
false-fail result
incremental testing
45. The capability of the software product to enable modified software to be tested. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements - modified to make fut
data flow
entry criteria
testability
usability
46. A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system. [After TMap]
testability
configuration auditing
security tool
driver
47. A high level metric of effectiveness and/or efficiency used to guide and control progressive test development - e.g. Defect Detection Percentage (DDP).
multiple condition coverage
stability
test performance indicator
management review
48. Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.
fault seeding tool
white-box test design technique
debugging tool
maintainability testing
49. Deviation of the component or system from its expected delivery - service or result. [After Fenton]
infeasible path
fail
decision testing
failure
50. A framework to describe the software development life cycle activities from requirements specification to maintenance. The V-model illustrates how testing activities can be integrated into each phase of the software development life cycle.
process
serviceability testing
unit test framework
V-model
Sorry!:) No result found.
Can you answer 50 questions in 15 minutes?
Let me suggest you:
Browse all subjects
Browse all tests
Most popular tests
Major Subjects
Tests & Exams
AP
CLEP
DSST
GRE
SAT
GMAT
Certifications
CISSP go to https://www.isc2.org/
PMP
ITIL
RHCE
MCTS
More...
IT Skills
Android Programming
Data Modeling
Objective C Programming
Basic Python Programming
Adobe Illustrator
More...
Business Skills
Advertising Techniques
Business Accounting Basics
Business Strategy
Human Resource Management
Marketing Basics
More...
Soft Skills
Body Language
People Skills
Public Speaking
Persuasion
Job Hunting And Resumes
More...
Vocabulary
GRE Vocab
SAT Vocab
TOEFL Essential Vocab
Basic English Words For All
Global Words You Should Know
Business English
More...
Languages
AP German Vocab
AP Latin Vocab
SAT Subject Test: French
Italian Survival
Norwegian Survival
More...
Engineering
Audio Engineering
Computer Science Engineering
Aerospace Engineering
Chemical Engineering
Structural Engineering
More...
Health Sciences
Basic Nursing Skills
Health Science Language Fundamentals
Veterinary Technology Medical Language
Cardiology
Clinical Surgery
More...
English
Grammar Fundamentals
Literary And Rhetorical Vocab
Elements Of Style Vocab
Introduction To English Major
Complete Advanced Sentences
Literature
Homonyms
More...
Math
Algebra Formulas
Basic Arithmetic: Measurements
Metric Conversions
Geometric Properties
Important Math Facts
Number Sense Vocab
Business Math
More...
Other Major Subjects
Science
Economics
History
Law
Performing-arts
Cooking
Logic & Reasoning
Trivia
Browse all subjects
Browse all tests
Most popular tests