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. The testing activities that must be repeated when testing is re-started after a suspension. [After IEEE 829]
resumption criteria
test session
inspection
volume testing
2. 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
test design technique
benchmark test
pairwise testing
procedure testing
3. A form of static analysis based on the definition and usage of variables.
pointer
requirements-based testing
data flow analysis
acceptance criteria
4. The assessment of change to the layers of development documentation - test documentation and components - in order to implement a given change to specified requirements.
unit testing
impact analysis
V-model
boundary value coverage
5. A minimal software item that can be tested in isolation.
safety critical system
big-bang testing
module
experienced-based test design technique
6. 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
beta testing
specified input
verification
fault tolerance
7. 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
configuration management tool
performance
cause-effect graph
emulator
8. 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.
adaptability
test data preparation tool
performance testing tool
capture/playback tool
9. The capability of the software product to avoid unexpected effects from modifications in the software. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements
testing
condition determination testing
false-fail result
stability
10. 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
efficiency
process improvement
regression testing
11. 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
equivalence partition coverage
experienced-based test design technique
coverage tool
12. 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
use case testing
attack
maintainability testing
alpha testing
13. The period of time in a software development life cycle during which the components of a software product are executed - and the software product is evaluated to determine whether or not requirements have been satisfied. [IEEE 610]
test harness
test cycle
test execution phase
control flow graph
14. A test approach in which the test suite comprises all combinations of input values and preconditions.
decision table testing
exhaustive testing
system integration testing
bottom-up testing
15. A test plan that typically addresses one test level. 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 testin
risk level
hyperlink
specified input
level test plan
16. Execution of the test process against a single identifiable release of the test object.
milestone
accuracy
incident management
test cycle
17. 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
maintainability testing
beta testing
syntax testing
test case
18. 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
variable
Failure Mode - Effect and Criticality Analysis (FMECA)
attack
test session
19. A set of one or more test cases. [IEEE 829]
test suite
test strategy
test summary report
test
20. A test result which fails to identify the presence of a defect that is actually present in the test object.
false-pass result
configuration item
actual outcome
module
21. The process of testing to determine the interoperability of a software product. See also functionality testing. The process of testing to determine the functionality of a software product.
defect density
functional integration
interoperability testing
defect management tool
22. Execution of a test on a specific version of the test object.
equivalence partitioning
test management tool
test run
continuous representation
23. Testing that runs test cases that failed the last time they were run - in order to verify the success of corrective actions.
LCSAJ testing
static analysis tool
re-testing
test design specification
24. 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
off-the-shelf software
formal review
scenario testing
management review
25. A tool used to check that no brtoken hyperlinks are present on a web site.
component integration testing
hyperlink tool
formal review
load profile
26. A grid showing the resulting transitions for each state combined with each possible event - showing both valid and invalid transitions.
test execution automation
process improvement
state table
coverage tool
27. The organizational artifacts needed to perform testing - consisting of test environments - test tools - office environment and procedures.
test harness
inspection
adaptability
test infrastructure
28. The capability of the software product to provide appropriate performance - relative to the amount of resources used under stated conditions. [ISO 9126]
test data preparation tool
state table
efficiency
master test plan
29. Hardware and software products installed at users' or customers' sites where the component or system under test will be used. The software may include operating systems - database management systems - and other applications.
module
operational acceptance testing
operational environment
retrospective meeting
30. The process of recognizing - investigating - taking action and disposing of defects. It involves recording defects - classifying them and identifying the impact. [After IEEE 1044]
exhaustive testing
safety critical system
recoverability testing
defect management
31. An input for which the specification predicts a result.
operational environment
specified input
testware
measurement
32. 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
recoverability
availability
requirement
replaceability
33. A set of interrelated activities - which transform inputs into outputs. [ISO 12207]
requirement
process
test monitoring
safety testing
34. A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script. [After IEEE 829]
operational profile
decision coverage
test scenario
risk type
35. 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]
invalid testing
risk identification
test phase
smoke test
36. A group of people responsible for evaluating and approving or disapproving proposed changes to configuration items - and for ensuring implementation of approved changes. [IEEE 610]
LCSAJ testing
behavior
configuration control board (CCB)
Test Point Analysis (TPA)
37. Tests aimed at showing that a component or system does not work. Negative testing is related to the testers' attitude rather than a specific test approach or test design technique - e.g. testing with invalid input values or exceptions. [After Beizer]
best practice
software life cycle
negative testing
test manager
38. 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]
hazard analysis
equivalence partitioning
version control
pairwise testing
39. A document that consists of a test design specification - test case specification and/or test procedure specification.
test input
condition coverage
path coverage
test specification
40. A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark) - a user-manual - or an individual's specialized knowledge - but should not be the code. [Afte
configuration management
equivalence partition
buffer
oracle
41. An integration test type that is concerned with testing the interfaces between components or systems.
test planning
interface testing
cause-effect graph
test approach
42. The process of recording information about tests executed into a test log.
test logging
static code analysis
operational environment
incident report
43. 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
test oracle
LCSAJ
efficiency testing
cause-effect graphing
44. A formula based test estimation method based on function point analysis. [TMap]
decision table
Test Point Analysis (TPA)
incident logging
acceptance criteria
45. 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.
risk-based testing
process
equivalence partitioning
walkthrough
46. A pointer within a web page that leads to other web pages.
state transition
maturity
hyperlink
data flow
47. The degree to which a component - system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610]
pairwise testing
quality
portability
cost of quality
48. 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
root cause
test harness
reliability
49. The process of finding - analyzing and removing the causes of failures in software.
risk identification
requirement
requirements management tool
debugging
50. A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.
monitor
compliance
process cycle test
syntax 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