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. Measures amount of testing performed by a collection of test cases
experience-based techniques
coverage
incident life cycle phases
inspection
2. Insertion of additional code in the existing program in order to count coverage items.
agile software development model
test tool deployment Success Factors
instrumentation
load testing
3. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
boundary value analysis
decision testing
component testing
data-driven testing
4. Tests interfaces between components and between integrated components and systems.
integration testing
business process-based testing
debugging tools
incident life cycle phases
5. Special-purpose software used to simulate a component that calls the component under test
test analysis & design tasks
integration management tools
driver
operational testing
6. Components are integrated in the order in which they are developed
equivalence partitioning
test implementation tasks
anomalous events
ad hoc integration
7. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
maintenance testing
condition coverage
decision coverage
LCSAJ testing
8. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
black-box testing
decision coverage
incremental testing
9. Examine changes made to an operational system cause defects.
LCSAJ testing
maintenance testing
actual result
resolution types
10. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
Incidents
cause-effect graphic testing
integration testing
maintainability testing
11. One defect prevents the detection of another.
waterfall model phases
functionality
impact analysis
defect masking
12. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
efficiency
defect masking
iterative-incremental development models
coverage
13. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintainability testing
driver
Incidents
test data preparation tools
14. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template
exhaustive testing
incident life cycle phases
stub
test data preparation tools
15. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
maintenance testing
configuration management tools
equivalence partitioning
experience-based techniques
16. Tools used to store and manage incidents return phone defects failures or anomalies.
test analysis & design tasks
debugging tools
driver
incident management tools
17. Integrate different kinds of tools to make test management more efficient and simple.
SW development model
integration management tools
accuracy
nonfunctional requirements
18. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
alpha testing
stub
test control Tasks
multiple condition coverage
19. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
test execution tasks
incremental testing
cause-effect graphic testing
20. Record details of test cases executed Record order of execution record results
SW development model
test execution tasks
test log uses
bottom-up integration
21. A document that provides the structure for writing test cases.
cyclomatic complexity
iterative-incremental development models
IEEE test case specification template
failure
22. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
cyclomatic complexity
keyword-driven testing
defect masking
LCSAJ testing
23. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
integration management tools
stub
multiple condition coverage
incident management tools
24. Used to replace a component that calls another component.
load testing
driver
horizontal traceability
IEEE incident report template
25. Black-box testing technique used to create groups of input conditions that create the same kind of output.
incident report identifier
functional incremental integration
equivalence partitioning
LCSAJ testing
26. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
alpha testing
test planning Tasks
nonfunctional requirements
functional testing
27. A unique identifier for each incident report generated during test execution.
conditions
test levels
boundary value analysis
incident report identifier
28. The ratio between the number of defects found and the size of the component/system tested.
SW development model
integration
defect density
test levels
29. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
Three main SW development models
equivalence partitioning
functional testing tool
30. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
accuracy
test management tool features
equivalence partitioning
decision testing
31. 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
error
SW development model
waterfall model benefits
LCSAJ testing
32. Requirements that determine the functionality of a software system.
decision table
functional requirements
error guessing
data flow structure
33. Incident Report - Identifier - Summary - Incident - Description - Impact
incident report identifier
IEEE incident report template
incident life cycle phases
failure rate
34. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
equivalence partitions
nonfunctional requirements
entry criteria
35. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
configuration management
IEEE test case specification template
incident life cycle phases
agile software development model
36. A table showing combinations of inputs and their associated actions.
impact
acceptance testing
decision table
incident report
37. 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.
decision table
entry criteria
inspection
acceptance criteria
38. Based on analysis of functional specifications of a system.
input specifications
exhaustive testing
functional testing
impact
39. Tools used by developers to identify defects in programs.
entry criteria
beta testing
inspection
debugging tools
40. The process of finding analyzing and removing causes of failure in a software product.
action
conformance testing tools
debugging
ad hoc integration
41. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
driver
LCSAJ
incremental testing
42. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
decision table
error guessing
maintainability
failure
43. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
efficiency
monitor
decision testing
44. Process used to create a SW product from initial conception to public release
failure
alpha testing
SW development model
integration testing
45. Component - Integration - System - Acceptance
accuracy
test condition
test levels
multiple condition coverage
46. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
nonfunctional requirements
horizontal traceability
integration testing
test implementation tasks
47. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
operational testing
exploratory testing
documentation tools
test data preparation tools
48. Waterfall iterative-incremental "V"
driver
Three main SW development models
IEEE test case specification template
test control Tasks
49. Used to test the functionality of software as mentioned in software requirement specifications.
exploratory testing
configuration management
debugging
functional testing tool
50. Separation of testing responsibilities which encourages the accomplishment of objective testing
data flow structure
independence of testing
impact
decision testing