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. The ratio between the number of defects found and the size of the component/system tested.
impact
keyword-driven testing
test control Tasks
defect density
2. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
experience-based techniques
debugging
debugging tools
3. A set of conditions that a system needs to meet in order to be accepted by end users
SW development model
waterfall model benefits
environmental needs
acceptance criteria
4. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
multiple condition coverage
equivalence partitioning
resolution types
maintainability
5. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
cyclomatic complexity
test execution tasks
test implementation tasks
functional testing
6. Process used to create a SW product from initial conception to public release
SW development model
efficiency
interoperability testing
black-box testing
7. Ability of software to provide appropriate performance relative to amount of resources used.
code coverage
action
error
efficiency
8. Separation of testing responsibilities which encourages the accomplishment of objective testing
configuration management tools
test execution tasks
independence of testing
incident report identifier
9. Informal testing technique in which test planning and execution run in parallel
exploratory testing
decision table testing
coverage
integration management tools
10. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
integration management tools
integration
business process-based testing
iterative-incremental development models
11. Actual inputs required to execute a test case
input specifications
impact analysis
instrumentation
interoperability testing
12. Testing software in its operational environment
Incidents
test tool deployment Success Factors
incident description subheadings
operational testing
13. Tools used by developers to identify defects in programs.
debugging tools
acceptance criteria
LCSAJ testing
risk-based testing
14. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
maintainability testing
condition determination coverage
beta testing
waterfall model phases
15. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
system testing
defect density
equivalence partitions
16. Calculates the number of executed branch outcomes in code.
decision coverage
conditions
keyword-driven testing
independence of testing
17. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
defect masking
decision testing
integration testing
18. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables
waterfall model benefits
equivalence partitioning
functional requirements
defect masking
19. Testing an integrated system to validate it meets requirements
operational testing
system testing
maintainability
functional testing
20. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
test levels
Three main SW development models
error guessing
21. Occurrences that happen before and after an unexpected event
maintainability
anomalous events
waterfall model benefits
actual result
22. Special-purpose software used to simulate a component called by the component under test
test condition
stub
automation tools
inspection
23. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
driver
cause-effect graphic testing
test management tool features
functional requirements
24. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
decision testing
test control Tasks
iterative-incremental development models
test data preparation tools
25. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
resolution types
stub
boundary value analysis
backbone integration
26. Tests interfaces between components and between integrated components and systems.
impact
keyword-driven testing
Three main SW development models
integration testing
27. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
black-box testing
impact analysis
IEEE incident report template
fault attack
28. An event or item that can be tested using one or more test cases
test condition
configuration management
contract acceptance testing
load testing
29. Develop & proiroitize test cases Create groups of test cases Set up test environment
decision testing
anomalous events
test implementation tasks
interoperability testing
30. Black-box testing technique used to create groups of input conditions that create the same kind of output.
boundary value analysis
equivalence partitioning
configuration management
experience-based techniques
31. Deviation of a software system from its expected delivery services or results
functionality
test data preparation tools
incremental testing
failure
32. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
test condition
incremental testing
efficiency
multiple condition coverage
33. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
component testing
monitor
environmental needs
backbone integration
34. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
operational testing
test implementation tasks
equivalence partitioning
test analysis & design tasks
35. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
nonfunctional requirements
environmental needs
incident description subheadings
test planning Tasks
36. Waterfall iterative-incremental "V"
Three main SW development models
instrumentation
system testing
defect masking
37. A table showing combinations of inputs and their associated actions.
impact
incident report identifier
decision table
test control Tasks
38. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
experience-based techniques
cause-effect graphic testing
coverage
39. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
maintainability testing
Incidents
black-box testing
decision table testing
40. Based on analysis of functional specifications of a system.
functional testing tool
functional testing
test analysis & design tasks
horizontal traceability
41. The process of finding analyzing and removing causes of failure in a software product.
debugging
inspection
configuration management
monitor
42. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
incident life cycle phases
fault attack
backbone integration
load testing
43. Human action that generates an incorrect result.
interoperability testing
condition determination coverage
backbone integration
error
44. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
system testing
automation tools
risk-based testing
control flow structure
45. Integrate different kinds of tools to make test management more efficient and simple.
testing process phases
integration management tools
bottom-up integration
beta testing
46. Sequence in which data items are accessed or modified by code.
data flow structure
independence of testing
system testing
test log uses
47. An analysis that determines the portion of code on software executed by a set of test cases
functional testing tool
code coverage
decision table testing
stub
48. A document that provides the structure for writing test cases.
nonfunctional requirements
input specifications
Three main SW development models
IEEE test case specification template
49. Operational testing performed at an _external_ site without involvement of the developing organization.
agile software development model
conditions
beta testing
incident life cycle phases
50. Conditions required to begin testing activities.
entry criteria
business process-based testing
component integration testing
black-box testing