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. Allows storage of test input and expected results in one or more central data sources or databases.
incident report
entry criteria
integration testing
data-driven testing
2. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
multiple condition coverage
impact analysis
error guessing
LCSAJ testing
3. Component - Integration - System - Acceptance
test levels
acceptance criteria
test control Tasks
informal review
4. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
COTS
decision table
SW development model
5. Tools used by developers to identify defects in programs.
debugging tools
incident management tools
actual result
debugging
6. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
inspection
conformance testing tools
conditions
testing process phases
7. 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
test implementation tasks
fault attack
test control Tasks
8. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
defect masking
incident management tools
acceptance criteria
9. Ability of software to provide appropriate performance relative to amount of resources used.
actual result
IEEE incident report template
efficiency
functional testing
10. Examine changes made to an operational system cause defects.
condition determination coverage
incident report identifier
cause-effect graphic testing
maintenance testing
11. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
test log uses
actual result
COTS
failure rate
12. A document that records the description of each event that occurs during the testing process and that requires further investigation
conformance testing tools
exhaustive testing
incident report
exploratory testing
13. Tools used to store and manage incidents return phone defects failures or anomalies.
incremental testing
IEEE incident report template
incident management tools
LCSAJ testing
14. Find defects in code while the software application being tested is running.
dynamic analysis tools
test analysis & design tasks
waterfall model phases
exhaustive testing
15. One defect prevents the detection of another.
defect masking
monitor
system testing
risk-based testing
16. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
acceptance criteria
cyclomatic complexity
acceptance testing
test log uses
17. Conditions required to begin testing activities.
test management tool features
defect
entry criteria
nonfunctional requirements
18. The process of finding analyzing and removing causes of failure in a software product.
horizontal traceability
debugging
iterative-incremental development models
multiple condition coverage
19. Testing performed to determine whether the system meets acceptance criteria
acceptance testing
fault attack
SW development model
defect masking
20. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
defect density
action
incident life cycle phases
acceptance criteria
21. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
condition coverage
incremental testing
instrumentation
conformance testing tools
22. Input or combination of inputs required to test software.
conditions
environmental needs
iterative-incremental development models
conformance testing tools
23. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
impact
functional incremental integration
condition coverage
24. Incident Report - Identifier - Summary - Incident - Description - Impact
conditions
incremental testing
IEEE incident report template
iterative-incremental development models
25. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
boundary value analysis
exit criteria
conditions
incident management tools
26. Testing software components that are separately testable. Also module program and unit testing.
component testing
actual result
bottom-up integration
cause-effect graphic testing
27. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
load testing
equivalence partitions
acceptance testing
boundary value analysis
28. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
condition coverage
failure
debugging
iterative-incremental development models
29. A functional testing approach in which test cases are designed based on business processes.
informal review
maintainability
business process-based testing
decision coverage
30. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
Impact subheadings
interoperability testing
exploratory testing
nonfunctional requirements
31. Record details of test cases executed Record order of execution record results
test log uses
dynamic analysis tools
functional incremental integration
boundary value analysis
32. Components are integrated in the order in which they are developed
ad hoc integration
coverage
debugging
maintainability testing
33. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
decision coverage
decision table testing
test log uses
34. 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
functionality
interoperability
test tool deployment Success Factors
nonfunctional requirements
35. Human action that generates an incorrect result.
component integration testing
test levels
error
entry criteria
36. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
integration
LCSAJ
COTS
debugging
37. Special-purpose software used to simulate a component that calls the component under test
equivalence partitioning
test control Tasks
driver
system testing
38. A set of conditions that a system needs to meet in order to be accepted by end users
contract acceptance testing
acceptance criteria
impact
decision table
39. A unique identifier for each incident report generated during test execution.
defect density
incident report identifier
functional incremental integration
dynamic analysis tools
40. Black-box testing technique used to create groups of input conditions that create the same kind of output.
configuration management tools
equivalence partitioning
interoperability
black-box testing
41. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
debugging
efficiency
functionality
agile software development model
42. Measures amount of testing performed by a collection of test cases
environmental needs
coverage
code coverage
acceptance testing
43. Components are combined and tested in the order in which basic functionalities start working
equivalence partitions
impact analysis
functional incremental integration
cyclomatic complexity
44. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
defect density
defect masking
conformance testing tools
incident description subheadings
45. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
incident description subheadings
impact analysis
resolution types
backbone integration
46. Behavior or response of a software application that you observe when you execute the action steps in the test case.
actual result
coverage measurement tools
integration testing
decision table testing
47. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
test control Tasks
nonfunctional requirements
test tool deployment Success Factors
defect
48. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
error guessing
keyword-driven testing
functional testing
functional testing tool
49. Special additions or changes to the environment required to run a test case.
operational testing
decision testing
impact
environmental needs
50. The smallest software item that can be tested in isolation.
interoperability testing
stub
environmental needs
component