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. 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).
configuration management tools
error
experience-based techniques
functional testing
2. Response of the application to an input
debugging tools
ad hoc integration
action
driver
3. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
driver
incident life cycle phases
ad hoc integration
component integration testing
4. Insertion of additional code in the existing program in order to count coverage items.
horizontal traceability
instrumentation
test management tool features
driver
5. Component - Integration - System - Acceptance
Three main SW development models
cause-effect graphic testing
big-bang testing
test levels
6. A document that provides the structure for writing test cases.
coverage
IEEE test case specification template
decision table testing
component
7. Examine changes made to an operational system cause defects.
maintenance testing
data flow structure
system testing
acceptance testing
8. Testing software components that are separately testable. Also module program and unit testing.
maintainability testing
component testing
operational testing
data-driven testing
9. One defect prevents the detection of another.
cause-effect graphic testing
failure
acceptance testing
defect masking
10. A set of conditions that a system needs to meet in order to be accepted by end users
test execution tasks
acceptance criteria
integration
defect density
11. Tests interfaces between components and between integrated components and systems.
IEEE incident report template
test tool deployment Success Factors
integration testing
coverage
12. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
integration
integration management tools
nonfunctional requirements
equivalence partitioning
13. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
component
input specifications
multiple condition coverage
14. Linear Code Sequence and Jump.
incident description subheadings
component integration testing
LCSAJ
testing process phases
15. Tools used by developers to identify defects in programs.
data-driven testing
SW development model
conformance testing tools
debugging tools
16. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
functional testing
COTS
test condition
17. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
backbone integration
boundary value analysis
test planning Tasks
exploratory testing
18. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
inspection
incremental testing
incident management tools
19. A table showing combinations of inputs and their associated actions.
test condition
Three main SW development models
anomalous events
decision table
20. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
multiple condition coverage
contract acceptance testing
driver
21. Black-box testing technique used to create groups of input conditions that create the same kind of output.
system testing
equivalence partitions
component
equivalence partitioning
22. Special-purpose software used to simulate a component called by the component under test
stub
driver
beta testing
failure
23. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
integration management tools
test implementation tasks
documentation tools
incident description subheadings
24. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
driver
decision testing
resolution types
test management tool features
25. Integrate different kinds of tools to make test management more efficient and simple.
equivalence partitions
environmental needs
data flow structure
integration management tools
26. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
component integration testing
horizontal traceability
incremental testing
maintainability
27. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
incident report
LCSAJ
cause-effect graphic testing
multiple condition coverage
28. Process used to create a SW product from initial conception to public release
informal review
SW development model
monitor
action
29. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
black-box testing
configuration management tools
decision testing
action
30. Sequence in which data items are accessed or modified by code.
test execution tasks
data flow structure
defect
incident life cycle phases
31. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
integration testing
IEEE test case specification template
decision coverage
32. Incident Report - Identifier - Summary - Incident - Description - Impact
boundary value analysis
iterative-incremental development models
conditions
IEEE incident report template
33. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
test data preparation tools
contract acceptance testing
decision table
decision table testing
34. Specific groups that represent a set of valid or invalid partitions for input conditions.
data-driven testing
equivalence partitions
efficiency
configuration management tools
35. Testing an integrated system to validate it meets requirements
test management tool features
system testing
dynamic analysis tools
conformance testing tools
36. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
control flow structure
conditions
impact analysis
37. Actual inputs required to execute a test case
accuracy
data-driven testing
code coverage
input specifications
38. Used to test the functionality of software as mentioned in software requirement specifications.
incident life cycle phases
driver
functional testing tool
actual result
39. Requirements that determine the functionality of a software system.
coverage measurement tools
functional incremental integration
functional requirements
waterfall model phases
40. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.
anomalous events
bottom-up integration
horizontal traceability
iterative-incremental development models
41. Conditions required to begin testing activities.
entry criteria
test execution tasks
cause-effect graphic testing
contract acceptance testing
42. Sequence in which instructions are executed through a component or system
test data preparation tools
fault attack
acceptance testing
control flow structure
43. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
data flow structure
instrumentation
test control Tasks
environmental needs
44. An event or item that can be tested using one or more test cases
test condition
data-driven testing
operational testing
acceptance testing
45. Behavior or response of a software application that you observe when you execute the action steps in the test case.
actual result
big-bang testing
instrumentation
failure
46. The smallest software item that can be tested in isolation.
dynamic analysis tools
component
incremental testing
test execution tasks
47. Occurrences that happen before and after an unexpected event
configuration management tools
anomalous events
experience-based techniques
functional incremental integration
48. Develop & proiroitize test cases Create groups of test cases Set up test environment
backbone integration
horizontal traceability
test implementation tasks
accuracy
49. Human action that generates an incorrect result.
test planning Tasks
defect density
error
experience-based techniques
50. Operational testing performed at an _external_ site without involvement of the developing organization.
configuration management tools
beta testing
component testing
defect