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 set from which valid input and/or output values can be selected.
domain
interoperability
test execution schedule
wild pointer
2. A white box test design technique in which test cases are designed to execute single condition outcomes that independently affect a decision outcome.
learnability
condition determination testing
top-down testing
root cause
3. Procedure used to derive and/or select test cases.
compliance testing
orthogonal array testing
test specification technique
oracle
4. 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]
project
incident management
process
component integration testing
5. Part of quality management focused on providing confidence that quality requirements will be fulfilled. [ISO 9000]
reviewer
volume testing
compatibility testing
quality assurance
6. 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.
test execution
subpath
static code analyzer
ttractiveness
7. Computer instructions and data definitions expressed in a programming language or in a form output by an assembler - compiler or other translator. [IEEE 610]
project risk
code
software quality
defect based test design technique
8. 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
back-to-back testing
test specification technique
inspection
validation
9. A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and Graham - IEEE 1028] See also peer review. A review of a software work product by colleagues of the producer of the product for the p
site acceptance testing
technical review
test
boundary value coverage
10. Statistical testing using a model of system operations (short duration tasks) and their probability of typical use. [Musa]
operational profile testing
keyword driven testing
branch testing
test reproduceability
11. 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.
domain
test data
review tool
non-functional requirement
12. Testing performed to expose defects in the interfaces and interaction between integrated components.
component integration testing
Defect Detection Percentage (DDP)
pass/fail criteria
version control
13. A black box test design technique in which test cases are designed to execute user scenarios.
wild pointer
error tolerance
bespoke software
scenario testing
14. The capability of the software product to enable the user to learn its application. [ISO 9126] See also usability. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO
fault tolerance
learnability
test objective
test
15. The process of combining components or systems into larger assemblies.
thread testing
test design tool
integration
test comparison
16. [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.
multiple condition testing
partition testing
exploratory testing
defect management
17. A high level document describing the principles - approach and major objectives of the organization regarding testing.
test automation
test policy
statement testing
Failure Mode - Effect and Criticality Analysis (FMECA)
18. The result of a decision (which therefore determines the branches to be taken).
decision outcome
branch coverage
static analysis tool
test design
19. The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage. [IEEE 610]
operational profile testing
production acceptance testing
availability
reliability
20. An integration test type that is concerned with testing the interfaces between components or systems.
interface testing
decision table testing
status accounting
software
21. Testing aimed at ensuring that the component or system can operate in conjunction with new or existing users' business procedures or operational procedures.
basic block
black-box test design technique
procedure testing
test driven development
22. A test management task that deals with developing and applying a set of corrective actions to get a test project on track when monitoring shows a deviation from what was planned. See also test management. The planning - estimating - monitoring and co
status accounting
safety critical system
test control
test phase
23. The method used to perform the actual test execution - either manual or automated.
defect management tool
condition testing
heuristic evaluation
test execution technique
24. 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.
scripted testing
equivalence partitioning
incremental development model
component testing
25. 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.
data flow analysis
pair programming
intake test
thread testing
26. A feature or characteristic that affects an item's quality. [IEEE 610]
incident management
process
stub
quality attribute
27. A tool that provides run-time information on the state of the software code. These tools are most commonly used to identify unassigned pointers - check pointer arithmetic and to monitor the allocation - use and de-allocation of memory and to flag mem
test oracle
risk analysis
component
dynamic analysis tool
28. 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).
safety
horizontal traceability
formal review
security testing
29. A continuous framework for test process improvement that describes the key elements of an effective test process - especially targeted at system testing and acceptance testing.
Test Process Improvement (TPI)
Test Point Analysis (TPA)
post-execution comparison
classification tree
30. 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.
hyperlink tool
test item
load testing
cause-effect graphing
31. The function to check on the contents of libraries of configuration items - e.g. for standards compliance. [IEEE 610]
test monitoring
fault tolerance
configuration auditing
maintainability testing
32. Procedure to derive and/or select test cases based on the tester's experience - knowledge and intuition.
operational profile
test harness
experienced-based test design technique
project risk
33. A set of interrelated activities - which transform inputs into outputs. [ISO 12207]
false-fail result
beta testing
test objective
process
34. Separation of responsibilities - which encourages the accomplishment of objective testing. [After DO-178b]
postcondition
configuration control board (CCB)
independence of testing
procedure testing
35. 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
testability
user test
multiple condition testing
test plan
36. Testing to determine the ease by which users with disabilities can use a component or system. [Gerrard]
requirement
exit point
path testing
accessibility testing
37. A tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE tool repository - e.g. requirements management tool - from specified test conditions held in the tool itself - or from code.
risk control
test design tool
test execution automation
product risk
38. The capability of the software product to use appropriate amounts and types of resources - for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files - when the software performs its
emulator
branch testing
resource utilization
thread testing
39. 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
Capability Maturity Model Integration (CMMI)
output value
functional integration
modelling tool
40. A tool that supports the validation of models of the software or system [Graham].
test automation
modelling tool
debugging
incremental development model
41. The percentage of definition-use pairs that have been exercised by a test suite.
test design specification
data flow coverage
functionality testing
data definition
42. An attribute of a test indicating whether the same results are produced each time the test is executed.
test reproduceability
acceptance criteria
debugging tool
portability
43. A formula based test estimation method based on function point analysis. [TMap]
entry point
test procedure
Test Point Analysis (TPA)
test charter
44. Commonly used to refer to a test procedure specification - especially an automated one.
software
test script
low level test case
test manager
45. A five level staged framework for test process improvement - related to the Capability Maturity Model (CMM) - that describes the key elements of an effective test process.
coverage analysis
invalid testing
Test Maturity Model (TMM)
safety
46. A black box test design technique in which test cases are designed based on boundary values. See also boundary value. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either si
interoperability
test planning
boundary value analysis
static analyzer
47. A black box test design technique where test cases are selected - possibly using a pseudo-random generation algorithm - to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performa
project risk
random testing
management review
statement coverage
48. Testware used in automated testing - such as tool scripts.
moderator
project
test objective
automated testware
49. 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.
unit test framework
test implementation
ad hoc testing
state transition testing
50. A sequence of transactions in a dialogue between a user and the system with a tangible result.
replaceability
use case
ad hoc testing
dynamic analysis tool