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 identify and calculate coverage items in program code.
coverage measurement tools
incident life cycle phases
test control Tasks
equivalence partitioning
2. Occurrences that happen before and after an unexpected event
incident management tools
anomalous events
test planning Tasks
impact
3. 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).
component integration testing
test condition
configuration management tools
component
4. Behavior or response of a software application that you observe when you execute the action steps in the test case.
incident life cycle phases
actual result
independence of testing
black-box testing
5. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
debugging
load testing
decision table
6. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
test log uses
exit criteria
fault attack
monitor
7. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
stub
alpha testing
LCSAJ
Three main SW development models
8. Waterfall iterative-incremental "V"
condition coverage
test condition
test management tool features
Three main SW development models
9. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
interoperability testing
monitor
resolution types
test planning Tasks
10. Sequence in which data items are accessed or modified by code.
conformance testing tools
monitor
operational testing
data flow structure
11. Tests interfaces between components and between integrated components and systems.
integration testing
incident description subheadings
efficiency
defect masking
12. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
risk-based testing
interoperability testing
test control Tasks
exhaustive testing
13. A table showing combinations of inputs and their associated actions.
component testing
functional requirements
decision table
conditions
14. 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.
inspection
component
instrumentation
driver
15. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
test execution tasks
multiple condition coverage
nonfunctional requirements
efficiency
16. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
bottom-up integration
incident life cycle phases
impact analysis
equivalence partitions
17. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
waterfall model benefits
Impact subheadings
keyword-driven testing
nonfunctional requirements
18. The ratio between the number of defects found and the size of the component/system tested.
monitor
defect density
testing process phases
IEEE test case specification template
19. Deviation of a software system from its expected delivery services or results
failure
informal review
operational testing
integration management tools
20. Special-purpose software used to simulate a component that calls the component under test
driver
waterfall model phases
configuration management
coverage
21. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
SW development model
equivalence partitions
driver
incident life cycle phases
22. Tools used by developers to identify defects in programs.
debugging
debugging tools
integration management tools
incident report
23. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
efficiency
waterfall model phases
horizontal traceability
maintenance testing
24. Human action that generates an incorrect result.
error
condition coverage
exploratory testing
incident life cycle phases
25. Conditions required to begin testing activities.
acceptance testing
exit criteria
component testing
entry criteria
26. A functional testing approach in which test cases are designed based on business processes.
inspection
business process-based testing
monitor
exhaustive testing
27. Increased load (transations) used to test behavior of system under high volume.
load testing
maintainability
conformance testing tools
component integration testing
28. 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
COTS
test tool deployment Success Factors
big-bang testing
impact
29. Testing performed to determine whether the system meets acceptance criteria
test tool deployment Success Factors
driver
SW development model
acceptance testing
30. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
debugging tools
contract acceptance testing
waterfall model phases
monitor
31. White-box design technique used to design test cases for a software component using LCSAJ.
decision table testing
component testing
LCSAJ testing
backbone integration
32. Components are integrated in the order in which they are developed
data-driven testing
ad hoc integration
error guessing
LCSAJ testing
33. A unique identifier for each incident report generated during test execution.
bottom-up integration
fault attack
incident report identifier
waterfall model benefits
34. Special additions or changes to the environment required to run a test case.
action
waterfall model benefits
defect density
environmental needs
35. Testing software components that are separately testable. Also module program and unit testing.
conformance testing tools
data-driven testing
test execution tasks
component testing
36. Measures amount of testing performed by a collection of test cases
IEEE incident report template
Impact subheadings
test tool deployment Success Factors
coverage
37. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
waterfall model benefits
decision table
acceptance criteria
38. 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
business process-based testing
component
black-box testing
39. A document that provides the structure for writing test cases.
IEEE test case specification template
operational testing
functional testing tool
cyclomatic complexity
40. Testing an integrated system to validate it meets requirements
exit criteria
cyclomatic complexity
system testing
nonfunctional requirements
41. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations
load testing
risk-based testing
agile software development model
equivalence partitioning
42. A technique used to improve testing coverage by deliberately introducing faults in code.
backbone integration
functional testing tool
fault attack
entry criteria
43. An analysis that determines the portion of code on software executed by a set of test cases
integration testing
experience-based techniques
code coverage
Three main SW development models
44. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
instrumentation
condition coverage
efficiency
multiple condition coverage
45. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
functionality
nonfunctional requirements
black-box testing
inspection
46. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
incident report identifier
maintenance testing
beta testing
47. Calculates the number of executed branch outcomes in code.
exhaustive testing
environmental needs
test log uses
decision coverage
48. Specific groups that represent a set of valid or invalid partitions for input conditions.
defect masking
Impact subheadings
equivalence partitions
test management tool features
49. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
contract acceptance testing
test implementation tasks
decision testing
50. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
functional requirements
exploratory testing
maintainability testing
test management tool features