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 set of one or more test cases. [IEEE 829]
test strategy
condition testing
replaceability
test
2. A sequence of events - e.g. executable statements - of a component or system from an entry point to an exit point.
pass/fail criteria
test cycle
path
test policy
3. 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
elementary comparison testing
heuristic evaluation
black-box testing
iterative development model
4. The process of testing the installability of a software product. See also portability testing. The process of testing to determine the portability of a software product.
risk control
test case specification
installability testing
test type
5. A white box test design technique in which test cases are designed to execute statements.
monkey testing
maintainability
installation guide
statement testing
6. Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. [ISO 9000]
maintainability
risk-based testing
changeability
validation
7. The percentage of boundary values that have been exercised by a test suite.
security testing tool
test design specification
boundary value coverage
condition determination coverage
8. 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.
test execution schedule
thread testing
basis test set
domain
9. The set from which valid input values can be selected. See also domain. The set from which valid input and/or output values can be selected.
ttractiveness
input domain
installability testing
basis test set
10. 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
input
production acceptance testing
verification
acceptance testing
11. A method to determine test suite thoroughness by measuring the extent to which a test suite can discriminate the program from slight variants (mutants) of the program.
mutation analysis
unreachable code
code coverage
test progress report
12. Testing practice for a project using agile methodologies - such as extreme programming (XP) - treating development as the customer of testing and emphasizing the test first design paradigm. See also test driven development. A way of developing softwa
pointer
user acceptance testing
statement testing
agile testing
13. A test plan that typically addresses one test phase. 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
capture/replay tool
test execution automation
test management
phase test plan
14. 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.
output domain
experienced-based test design technique
condition determination testing
structural coverage
15. The use of software - e.g. capture/playback tools - to control the execution of tests - the comparison of actual results to expected results - the setting up of test preconditions - and other test control and reporting functions.
functional integration
test execution automation
acceptance testing
ttractiveness
16. The behavior produced/observed when a component or system is tested.
interoperability testing
non-functional test design techniques
multiple condition coverage
actual outcome
17. 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
unreachable code
test basis
component integration testing
availability
18. A scripting technique that stores test input and expected results in a table or spreadsheet - so that a single control script can execute all of the tests in the table. Data driven testing is often used to support the application of test execution to
compliance
process
data driven testing
test case
19. Testing the attributes of a component or system that do not relate to functionality - e.g. reliability - efficiency - usability - maintainability and portability.
equivalence partitioning
test summary report
test
non-functional testing
20. A specification of the activity which a component or system being tested may experience in production. A load profile consists of a designated number of virtual users who process a defined set of transactions in a specified time period and according
scribe
multiple condition coverage
load profile
risk type
21. The degree of uniformity - standardization - and freedom from contradiction among the documents or parts of a component or system. [IEEE 610]
analyzability
intake test
quality assurance
consistency
22. A collection of components organized to accomplish a specific function or set of functions. [IEEE 610]
system
LCSAJ coverage
statistical testing
phase test plan
23. Testing by means of a random selection from a large range of inputs and by randomly pushing buttons - ignorant on how the product is being used.
testability
Failure Mode - Effect and Criticality Analysis (FMECA)
monkey testing
N-switch testing
24. Testing based on an analysis of the internal structure of the component or system.
defect masking
white-box testing
data definition
basic block
25. Method aiming to measure the size of the functionality of an information system. The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity - the estimation of the needed resources -
defect report
inspection
Function Point Analysis (FPA)
resumption criteria
26. A test result in which a defect is reported although no such defect actually exists in the test object.
thread testing
false-fail result
defect management
instrumenter
27. Procedure to derive and/or select test cases based on an analysis of the specification of the functionality of a component or system without reference to its internal structure. See also black box test design technique. Procedure to derive and/or sel
scalability testing
procedure testing
functional test design technique
testware
28. 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.
scribe
Test Maturity Model (TMM)
deliverable
top-down testing
29. A tool that supports operational security.
unit test framework
security tool
defect tracking tool
monitor
30. Commonly used to refer to a test procedure specification - especially an automated one.
defect tracking tool
path sensitizing
dynamic analysis
test script
31. A subset of all defined/planned test cases that cover the main functionality of a component or system - to ascertaining that the most crucial functions of a program work - but not bothering with finer details. A daily build and smoke test is among in
smoke test
software life cycle
keyword driven testing
input domain
32. A test is deemed to fail if its actual result does not match its expected result.
fail
instrumenter
replaceability
review tool
33. A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in reliability failures.
structural coverage
reliability growth model
functionality
fault seeding tool
34. 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.
test reproduceability
test data
test design specification
recoverability
35. The degree to which a component or system has a design and/or internal structure that is difficult to understand - maintain and verify. See also cyclomatic complexity. The number of independent paths through a program. Cyclomatic complexity is define
complexity
static testing
safety critical system
fail
36. 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
verification
bespoke software
boundary value coverage
classification tree
37. The activity of establishing or updating a test plan.
test planning
scenario testing
requirements-based testing
resource utilization testing
38. A test approach in which the test suite comprises all combinations of input values and preconditions.
exhaustive testing
compound condition
condition coverage
test progress report
39. Testing where components or systems are integrated and tested one or some at a time - until all the components or systems are integrated and tested.
white-box test design technique
consistency
failure
incremental testing
40. A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation - correction and re-testing of incidents and provide reporting facilities. See also defect manage
test tool
incident management tool
resource utilization
orthogonal array testing
41. A scheme for the execution of test procedures. The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed.
LCSAJ
feasible path
version control
test execution schedule
42. A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.
defect taxonomy
use case
retrospective meeting
compliance
43. A superior method or innovative practice that contributes to the improved performance of an organization under given context - usually recognized as 'best' by other peer organizations.
impact analysis
best practice
partition testing
data definition
44. 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)
statistical testing
security tool
test comparison
re-testing
45. A document summarizing testing activities and results - produced at regular intervals - to report progress of testing activities against a baseline (such as the original test plan) and to communicate risks and alternatives requiring a decision to man
test progress report
incident
changeability
defect based test design technique
46. Testing of software used to convert data from existing systems for use in replacement systems.
phase test plan
migration testing
accuracy
re-testing
47. An independent evaluation of software products or processes to ascertain compliance to standards - guidelines - specifications - and/or procedures based on objective criteria - including documents that specify: (1) the form or content of the products
accessibility testing
condition determination coverage
audit
low level test case
48. The capability of the software product to adhere to standards - conventions or regulations in laws and similar prescriptions. [ISO 9126]
compliance
informal review
decision table testing
exercised
49. A review characterized by documented procedures and requirements - e.g. inspection.
formal review
statement testing
classification tree
Failure Mode and Effect Analysis (FMEA)
50. Procedure used to derive and/or select test cases.
test specification technique
replaceability
failure rate
pair testing