SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
CTFL
Start Test
Study First
Subjects
:
certifications
,
ctfl
,
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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
iterative-incremental development models
interoperability testing
dynamic analysis tools
error
2. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
functionality
defect
LCSAJ
automation tools
3. A document that provides the structure for writing test cases.
keyword-driven testing
automation tools
IEEE test case specification template
test management tool features
4. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
waterfall model benefits
actual result
test log uses
5. A task of maintaining and controlling changes to all entities of a system.
integration testing
configuration management
test planning Tasks
interoperability testing
6. The process of finding analyzing and removing causes of failure in a software product.
incremental testing
Impact subheadings
debugging
entry criteria
7. Used to test the functionality of software as mentioned in software requirement specifications.
code coverage
big-bang testing
ad hoc integration
functional testing tool
8. Waterfall iterative-incremental "V"
multiple condition coverage
configuration management tools
Three main SW development models
equivalence partitioning
9. Sequence in which data items are accessed or modified by code.
data flow structure
test management tool features
entry criteria
actual result
10. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
operational testing
testing process phases
Impact subheadings
monitor
11. Integration approach components or subsystems are combined all at once rather than in stages.
maintainability
test execution tasks
big-bang testing
Incidents
12. Sequence in which instructions are executed through a component or system
instrumentation
control flow structure
interoperability testing
environmental needs
13. Tools used to store and manage incidents return phone defects failures or anomalies.
environmental needs
incident management tools
test tool deployment Success Factors
configuration management
14. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test planning Tasks
input specifications
test control Tasks
failure rate
15. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons
data flow structure
test tool deployment Success Factors
impact
incident report identifier
16. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
IEEE test case specification template
actual result
beta testing
17. Special additions or changes to the environment required to run a test case.
functional incremental integration
failure rate
code coverage
environmental needs
18. Testing an integrated system to validate it meets requirements
functional testing
system testing
backbone integration
interoperability testing
19. Tools used to identify and calculate coverage items in program code.
incident management tools
instrumentation
coverage measurement tools
conditions
20. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
nonfunctional requirements
waterfall model phases
integration
incident report
21. Separation of testing responsibilities which encourages the accomplishment of objective testing
functional testing
functional incremental integration
independence of testing
configuration management tools
22. A component of the incident report that determines the actual effect of the incident on the software and its users.
action
test log uses
functional testing tool
impact
23. Testing performed to determine whether the system meets acceptance criteria
black-box testing
incident life cycle phases
acceptance testing
instrumentation
24. Combining components or sytems into larger structural units or subsystems.
condition coverage
integration
ad hoc integration
test tool deployment Success Factors
25. An event or item that can be tested using one or more test cases
test levels
defect masking
LCSAJ testing
test condition
26. Special-purpose software used to simulate a component called by the component under test
driver
conditions
stub
exhaustive testing
27. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
acceptance criteria
cyclomatic complexity
test data preparation tools
data-driven testing
28. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).
incident report
automation tools
configuration management tools
actual result
29. Severity - Priority
driver
condition determination coverage
black-box testing
Impact subheadings
30. Based on analysis of functional specifications of a system.
contract acceptance testing
integration
agile software development model
functional testing
31. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
monitor
black-box testing
impact analysis
LCSAJ testing
32. Insertion of additional code in the existing program in order to count coverage items.
beta testing
Incidents
cyclomatic complexity
instrumentation
33. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
test execution tasks
driver
decision coverage
34. Testing software components that are separately testable. Also module program and unit testing.
black-box testing
control flow structure
component testing
decision table testing
35. Process used to create a SW product from initial conception to public release
test levels
exit criteria
keyword-driven testing
SW development model
36. The smallest software item that can be tested in isolation.
component
test execution tasks
keyword-driven testing
debugging
37. Black-box test design technique - test cases are designed from a decision table.
debugging tools
decision table testing
environmental needs
bottom-up integration
38. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
data-driven testing
ad hoc integration
failure rate
incident report identifier
39. A document that records the description of each event that occurs during the testing process and that requires further investigation
cause-effect graphic testing
incident report
test implementation tasks
error
40. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
integration
incident life cycle phases
Incidents
error
41. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
test control Tasks
condition coverage
fault attack
acceptance criteria
42. Measures amount of testing performed by a collection of test cases
conformance testing tools
coverage
cause-effect graphic testing
code coverage
43. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
test log uses
driver
instrumentation
44. A set of conditions that a system needs to meet in order to be accepted by end users
exit criteria
system testing
acceptance criteria
exhaustive testing
45. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
load testing
error guessing
exhaustive testing
waterfall model benefits
46. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.
test analysis & design tasks
dynamic analysis tools
inspection
accuracy
47. Operational testing performed at an _external_ site without involvement of the developing organization.
incident management tools
beta testing
SW development model
driver
48. Specific groups that represent a set of valid or invalid partitions for input conditions.
equivalence partitions
functional requirements
interoperability testing
dynamic analysis tools
49. Components are integrated in the order in which they are developed
incident description subheadings
keyword-driven testing
functional testing
ad hoc integration
50. Tools used by developers to identify defects in programs.
debugging tools
data flow structure
incident management tools
Three main SW development models