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 white box test design technique in which test cases are designed to execute branches.
best practice
test planning
branch testing
recovery testing
2. 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]
test run
high level test case
static analyzer
buffer
3. A skilled professional who is involved in the testing of a component or system.
requirements management tool
database integrity testing
tester
risk control
4. A tool that provides support to the review process. Typical features include review planning and tracking support - communication support - collaborative reviews and a repository for collecting and reporting of metrics.
compatibility testing
review tool
business process-based testing
test execution automation
5. A memory access defect due to the attempt by a process to store data beyond the boundaries of a fixed length buffer - resulting in overwriting of adjacent memory areas or the raising of an overflow exception. See also buffer. A device or storage area
accessibility testing
functional testing
buffer overflow
cause-effect graph
6. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.
test suite
static analysis
wild pointer
test control
7. 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
test target
test oracle
performance testing
component specification
8. Computer instructions and data definitions expressed in a programming language or in a form output by an assembler - compiler or other translator. [IEEE 610]
reliability testing
fault seeding
code
test execution technique
9. Testing the integration of systems and packages; testing interfaces to external organizations (e.g. Electronic Data Interchange - Internet).
system integration testing
variable
review tool
specification
10. The evaluation of a condition to True or False.
boundary value
big-bang testing
condition outcome
low level test case
11. The degree to which a component - system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610]
recoverability
replaceability
quality
operational profile testing
12. Testing to determine the security of the software product. See also functionality testing. The process of testing to determine the functionality of a software product.
state transition testing
safety critical system
security testing
staged representation
13. The process of combining components or systems into larger assemblies.
integration
anomaly
unreachable code
output
14. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes.
business process-based testing
LCSAJ
benchmark test
iterative development model
15. 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
functional test design technique
defect masking
performance profiling
condition
16. The set from which valid output values can be selected. See also domain. The set from which valid input and/or output values can be selected.
system testing
test summary report
output domain
defect tracking tool
17. A tool that provides support to the test management and control part of a test process. It often has several capabilities - such as testware management - scheduling of tests - the logging of results - progress tracking - incident management and test
test management tool
validation
project risk
performance indicator
18. 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.
portability testing
cost of quality
thread testing
software
19. 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
defect report
incremental development model
performance
data definition
20. An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements - e.g. tests that exercise specific functions or probe non-functional attributes such as reliability or usability.
system integration testing
requirements-based testing
buffer
certification
21. A group of test activities aimed at testing a component or system focused on a specific test objective - i.e. functional test - usability test - regression test etc. A test type may take place on one or more test levels or test phases. [After TMap]
test specification
test type
incident report
pass
22. An occurrence in which one defect prevents the detection of another. [After IEEE 610]
test scenario
re-testing
defect masking
LCSAJ coverage
23. 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
documentation testing
robustness
specification
quality management
24. The individual element to be tested. There usually is one test object and many test items. See also test object. A reason or purpose for designing and executing a test.
result
test item
installation guide
false-fail result
25. Any (work) product that must be delivered to someone other than the (work) product's author.
software life cycle
deliverable
classification tree method
configuration control board (CCB)
26. 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]
usability testing
exit criteria
elementary comparison testing
test evaluation report
27. The capability of the software product to interact with one or more specified components or systems. [After ISO 9126] See also functionality. The capability of the software product to provide functions which meet stated and implied needs when the sof
interoperability
test performance indicator
consistency
condition determination coverage
28. A data item that specifies the location of another data item; for example - a data item that specifies the address of the next employee record to be processed. [IEEE 610]
informal review
back-to-back testing
release note
pointer
29. Choosing a set of input values to force the execution of a given path.
test execution automation
path sensitizing
precondition
scripted testing
30. A specific category of risk related to the type of testing that can mitigate (control) that category. For example the risk of user-interactions being misunderstood can be mitigated by usability testing.
risk type
review
modelling tool
deliverable
31. Testing to determine the ease by which users with disabilities can use a component or system. [Gerrard]
horizontal traceability
accessibility testing
baseline
compliance
32. Testing to determine the robustness of the software product.
quality management
operational profile testing
robustness testing
negative testing
33. A document produced at the end of the test process summarizing all testing activities and results. It also contains an evaluation of the test process and lessons learned.
test evaluation report
test run
coverage
condition outcome
34. The process of testing to determine the reliability of a software product.
Fault Tree Analysis (FTA)
result
reliability testing
CASE
35. Part of quality management focused on providing confidence that quality requirements will be fulfilled. [ISO 9000]
quality assurance
test management
certification
best practice
36. The set from which valid input and/or output values can be selected.
domain
installation guide
test charter
entry point
37. A sequence of events - e.g. executable statements - of a component or system from an entry point to an exit point.
use case
path
process cycle test
isolation testing
38. The tracing of requirements for a test level through the layers of test documentation (e.g. test plan - test design specification - test case specification and test procedure specification or test script).
benchmark test
horizontal traceability
dynamic analysis
buffer overflow
39. An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests. [After Bach]
state transition testing
exploratory testing
tester
installability
40. A five level staged framework that describes the key elements of an effective software process. The Capability Maturity Model covers best-practices for planning - engineering and managing software development and maintenance. [CMM] See also Capabilit
recoverability testing
blocked test case
Capability Maturity Model (CMM)
non-functional requirement
41. The effect on the component or system by the measurement instrument when the component or system is being measured - e.g. by a performance testing tool or monitor. For example performance may be slightly worse when performance testing tools are being
static code analyzer
test closure
feasible path
probe effect
42. The degree - expressed as a percentage - to which a specified coverage item has been exercised by a test suite.
level test plan
static code analysis
operational profile
coverage
43. 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]
statement
CASE
priority
stub
44. 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.
interface testing
test design
configuration control
recoverability testing
45. A formula based test estimation method based on function point analysis. [TMap]
test evaluation report
adaptability
syntax testing
Test Point Analysis (TPA)
46. 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]
incremental testing
maintenance
code-based testing
high level test case
47. Testware used in automated testing - such as tool scripts.
maturity
automated testware
risk level
test implementation
48. 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
static code analyzer
condition coverage
portability
49. The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. [After IEEE 829]
suspension criteria
stress testing
independence of testing
baseline
50. A static usability test technique to determine the compliance of a user interface with recognized usability principles (the so-called "heuristics").
structural coverage
test script
heuristic evaluation
test planning
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