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. A task of maintaining and controlling changes to all entities of a system.
debugging tools
configuration management
integration management tools
multiple condition coverage
2. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incremental testing
coverage measurement tools
integration
functional testing
3. Record details of test cases executed Record order of execution record results
stub
test log uses
defect
integration management tools
4. Waterfall iterative-incremental "V"
defect masking
Three main SW development models
driver
monitor
5. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
accuracy
ad hoc integration
resolution types
documentation tools
6. Conditions required to begin testing activities.
test condition
entry criteria
business process-based testing
anomalous events
7. Severity - Priority
Impact subheadings
driver
documentation tools
equivalence partitioning
8. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
acceptance criteria
exit criteria
incident life cycle phases
waterfall model benefits
9. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
horizontal traceability
condition determination coverage
test levels
conformance testing tools
10. Behavior or response of a software application that you observe when you execute the action steps in the test case.
actual result
action
testing process phases
bottom-up integration
11. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
component testing
risk-based testing
maintainability
12. Separation of testing responsibilities which encourages the accomplishment of objective testing
nonfunctional requirements
independence of testing
exit criteria
LCSAJ testing
13. An analysis that determines the portion of code on software executed by a set of test cases
nonfunctional requirements
test levels
code coverage
incident management tools
14. Tests interfaces between components and between integrated components and systems.
system testing
conditions
test log uses
integration testing
15. Requirements that determine the functionality of a software system.
efficiency
failure rate
coverage
functional requirements
16. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
data flow structure
independence of testing
waterfall model benefits
17. Black-box testing technique used to create groups of input conditions that create the same kind of output.
automation tools
defect
equivalence partitioning
test condition
18. A document that records the description of each event that occurs during the testing process and that requires further investigation
decision coverage
incident report
integration
bottom-up integration
19. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
entry criteria
multiple condition coverage
inspection
equivalence partitioning
20. Special-purpose software used to simulate a component called by the component under test
operational testing
functionality
monitor
stub
21. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
equivalence partitioning
test condition
boundary value analysis
cyclomatic complexity
22. Used to test the functionality of software as mentioned in software requirement specifications.
component integration testing
functional testing tool
multiple condition coverage
Incidents
23. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
contract acceptance testing
interoperability
functional requirements
informal review
24. Allows storage of test input and expected results in one or more central data sources or databases.
functional incremental integration
business process-based testing
experience-based techniques
data-driven testing
25. Tools used by developers to identify defects in programs.
debugging tools
failure rate
code coverage
debugging
26. A table showing combinations of inputs and their associated actions.
functional incremental integration
decision table
experience-based techniques
maintenance testing
27. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
coverage measurement tools
test execution tasks
alpha testing
conditions
28. Informal testing technique in which test planning and execution run in parallel
failure rate
exploratory testing
load testing
black-box testing
29. Black-box test design technique - test cases are designed from a decision table.
inspection
decision table testing
interoperability testing
risk-based testing
30. A review not based on a formal documented procedure
actual result
decision testing
informal review
test log uses
31. Input or combination of inputs required to test software.
conditions
risk-based testing
test log uses
configuration management tools
32. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
test condition
test levels
component
33. Testing performed to determine whether the system meets acceptance criteria
failure
defect
acceptance testing
automation tools
34. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
test analysis & design tasks
COTS
waterfall model phases
boundary value analysis
35. Insertion of additional code in the existing program in order to count coverage items.
error guessing
instrumentation
functional incremental integration
incident report
36. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
keyword-driven testing
interoperability testing
boundary value analysis
SW development model
37. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
documentation tools
COTS
coverage measurement tools
38. Specific groups that represent a set of valid or invalid partitions for input conditions.
testing process phases
waterfall model benefits
functional testing
equivalence partitions
39. Calculates the number of executed branch outcomes in code.
decision coverage
cause-effect graphic testing
acceptance testing
accuracy
40. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
dynamic analysis tools
cause-effect graphic testing
keyword-driven testing
data-driven testing
41. Measures amount of testing performed by a collection of test cases
test log uses
instrumentation
coverage
independence of testing
42. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
exploratory testing
black-box testing
control flow structure
incident life cycle phases
43. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
maintenance testing
functionality
acceptance testing
exploratory testing
44. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
condition determination coverage
big-bang testing
functional incremental integration
decision testing
45. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
functional requirements
experience-based techniques
exit criteria
black-box testing
46. A technique used to improve testing coverage by deliberately introducing faults in code.
cause-effect graphic testing
fault attack
accuracy
test management tool features
47. 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.
monitor
inspection
code coverage
nonfunctional requirements
48. 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
test analysis & design tasks
boundary value analysis
error guessing
test data preparation tools
49. 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).
experience-based techniques
data flow structure
test condition
configuration management tools
50. The process of finding analyzing and removing causes of failure in a software product.
interoperability testing
Impact subheadings
debugging
exit criteria