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 tree showing equivalence parititions hierarchically ordered - which is used to design test cases in the classification tree method. See also classification tree method. A black box test design technique in which test cases - described by means of a
classification tree
path sensitizing
test script
serviceability testing
2. A white box test design technique in which test cases are designed to execute statements.
isolation testing
statement testing
white-box test design technique
control flow analysis
3. Formal testing with respect to user needs - requirements - and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user - customers or other authorized entity to determine whether or n
acceptance testing
output value
basic block
expected result
4. The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires each single condition in every decision statement to be tested as True and False.
test environment
condition coverage
exit criteria
Defect Detection Percentage (DDP)
5. A device or storage area used to store data temporarily for differences in rates of data flow - time or occurrence of events - or amounts of data that can be handeld by the devices or processes involved in the transfer or use of the data. [IEEE 610]
requirements phase
migration testing
buffer
test procedure
6. A skeletal or special-purpose implementation of a software component - used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component. [After IEEE 610]
test execution tool
walkthrough
state diagram
stub
7. A requirement that specifies a function that a component or system must perform. [IEEE 610]
functional requirement
actual result
boundary value coverage
scripting language
8. A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.
agile testing
white-box test design technique
syntax testing
incident management
9. 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]
version control
orthogonal array
efficiency testing
equivalence partitioning
10. 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.
behavior
ad hoc testing
configuration identification
test scenario
11. The percentage of LCSAJs of a component that have been exercised by a test suite. 100% LCSAJ coverage implies 100% decision coverage.
risk control
LCSAJ coverage
scribe
volume testing
12. An incremental approach to integration testing where the component at the top of the component hierarchy is tested first - with lower level components being simulated by stubs. Tested components are then used to test lower level components. The proce
top-down testing
post-execution comparison
daily build
test design specification
13. 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]
safety testing
test environment
incident logging
driver
14. A portion of an input or output domain for which the behavior of a component or system is assumed to be the same - based on the specification.
security tool
test infrastructure
equivalence partition
interface testing
15. Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also component integration testing - system integration testing. Testing performed to expose defects in the interfaces and int
behavior
integration testing
pass
cause-effect graphing
16. A tool that supports operational security.
maintainability testing
static analysis
path
security tool
17. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.
testable requirements
smoke test
static analysis
test case specification
18. Testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs and drivers - if needed.
isolation testing
use case testing
anomaly
automated testware
19. A type of peer review that relies on visual examination of documents to detect defects - e.g. violations of development standards and non-conformance to higher level documentation. The most formal review technique and therefore always based on a docu
operational environment
inspection
test harness
configuration auditing
20. An attribute of a component or system specified or implied by requirements documentation (for example reliability - usability or design constraints). [After IEEE 1008]
dynamic comparison
infeasible path
feature
buffer
21. The process through which decisions are reached and protective measures are implemented for reducing risks to - or maintaining risks within - specified levels.
qualification
measurement
risk control
development testing
22. A version of component integration testing where the progressive integration of components follows the implementation of subsets of the requirements - as opposed to the integration of components by levels of a hierarchy.
basis test set
thread testing
understandability
stress testing
23. A reason or purpose for designing and executing a test.
site acceptance testing
changeability
test schedule
test objective
24. A document describing the scope - approach - resources and schedule of intended test activities. It identifies amongst others test items - the features to be tested - the testing tasks - who will do each task - degree of tester independence - the tes
test scenario
test plan
requirement
risk type
25. A sequence of executable statements within a component.
subpath
agile testing
test phase
installation guide
26. Execution of a test on a specific version of the test object.
non-functional requirement
reliability
test run
defect tracking tool
27. The process of assigning a number or category to an entity to describe an attribute of that entity. [ISO 14598]
modelling tool
test management tool
measurement
performance testing
28. A path for which a set of input values and preconditions exists which causes it to be executed.
Capability Maturity Model (CMM)
actual result
resource utilization testing
feasible path
29. A measurement scale and the method used for measurement. [ISO 14598]
condition outcome
metric
equivalence partitioning
post-execution comparison
30. Computer programs - procedures - and possibly associated documentation and data pertaining to the operation of a computer system. [IEEE 610]
test item
N-switch testing
test phase
software
31. 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.
hyperlink tool
CAST
output value
compliance
32. A set of input values - execution preconditions - expected results and execution postconditions - developed for a particular objective or test condition - such as to exercise a particular program path or to verify compliance with a specific requireme
random testing
test case
dynamic testing
decision testing
33. 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.
understandability
test case suite
code
decision table
34. 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.
test manager
statement coverage
boundary value
condition determination testing
35. Definition of user profiles in performance - load and/or stress testing. Profiles should reflect anticipated or actual usage based on an operational profile of a component or system - and hence the expected workload. See also load profile - operation
scalability testing
integration testing
performance profiling
portability
36. A computational model consisting of a finite number of states and transitions between those states - possibly with accompanying actions. [IEEE 610]
multiple condition coverage
walkthrough
finite state machine
certification
37. A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements - including the constraints of time - cost and resources. [ISO 9000]
availability
risk
static analyzer
project
38. The consequence/outcome of the execution of a test. It includes outputs to screens - changes to data - reports - and communication messages sent out.
input domain
test design technique
outcome
maintainability
39. The process of testing to determine the functionality of a software product.
test comparison
debugging tool
functionality testing
precondition
40. 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
intake test
level test plan
documentation testing
41. 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
simulator
test progress report
test session
code-based testing
42. The capability of the software product to enable specified modifications to be implemented. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements - modified
changeability
state table
testable requirements
safety testing
43. Testing of a component or system at specification or implementation level without execution of that software - e.g. reviews or static code analysis.
test cycle
static testing
scribe
system testing
44. Testing the quality of the documentation - e.g. user guide or installation guide.
scenario testing
documentation testing
compliance testing
availability
45. A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]
security testing tool
defect report
operational environment
test execution schedule
46. Procedure used to derive and/or select test cases.
test design technique
debugging
changeability
system testing
47. 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
decision outcome
outcome
V-model
stress testing
48. A minimal software item that can be tested in isolation.
qualification
module
capture/replay tool
debugging
49. A test plan that typically addresses multiple test levels. See also test plan. A document describing the scope - approach - resources and schedule of intended test activities. It identifies amongst others test items - the features to be tested - the
process cycle test
walkthrough
behavior
master test plan
50. The percentage of all condition outcomes and decision outcomes that have been exercised by a test suite. 100% decision condition coverage implies both 100% condition coverage and 100% decision coverage.
decision condition coverage
accuracy
maintainability testing
robustness testing
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