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.
action
waterfall model benefits
defect density
anomalous events
2. An analysis that determines the portion of code on software executed by a set of test cases
documentation tools
code coverage
exit criteria
test tool deployment Success Factors
3. Incident Report - Identifier - Summary - Incident - Description - Impact
ad hoc integration
inspection
iterative-incremental development models
IEEE incident report template
4. Find defects in code while the software application being tested is running.
debugging
dynamic analysis tools
maintainability
test management tool features
5. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
inspection
condition determination coverage
black-box testing
instrumentation
6. Sequence in which instructions are executed through a component or system
control flow structure
integration
accuracy
risk-based testing
7. A document that records the description of each event that occurs during the testing process and that requires further investigation
LCSAJ
incident report
incident life cycle phases
exhaustive testing
8. One defect prevents the detection of another.
input specifications
maintenance testing
Impact subheadings
defect masking
9. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
documentation tools
waterfall model phases
risk-based testing
monitor
10. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
IEEE test case specification template
waterfall model phases
incident management tools
exhaustive testing
11. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
exit criteria
decision coverage
big-bang testing
iterative-incremental development models
12. Based on analysis of functional specifications of a system.
LCSAJ
driver
functional testing
Three main SW development models
13. An event or item that can be tested using one or more test cases
test analysis & design tasks
decision testing
test condition
IEEE test case specification template
14. Testing software components that are separately testable. Also module program and unit testing.
incident report identifier
component testing
incident management tools
data-driven testing
15. Human action that generates an incorrect result.
actual result
debugging
test management tool features
error
16. Combining components or sytems into larger structural units or subsystems.
interoperability
condition coverage
integration
horizontal traceability
17. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
test execution tasks
COTS
test levels
experience-based techniques
18. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
exit criteria
stub
test log uses
incident life cycle phases
19. Black-box test design technique - test cases are designed from a decision table.
decision table testing
conditions
test data preparation tools
bottom-up integration
20. Operational testing performed at an _external_ site without involvement of the developing organization.
test execution tasks
beta testing
interoperability testing
test tool deployment Success Factors
21. Conditions required to begin testing activities.
entry criteria
incident management tools
driver
fault attack
22. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
LCSAJ
action
functionality
contract acceptance testing
23. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
test tool deployment Success Factors
test management tool features
condition coverage
incident life cycle phases
24. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
operational testing
maintainability
accuracy
documentation tools
25. 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.
load testing
error
data flow structure
inspection
26. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
dynamic analysis tools
testing process phases
test implementation tasks
IEEE test case specification template
27. Component - Integration - System - Acceptance
failure rate
test levels
backbone integration
configuration management tools
28. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
waterfall model benefits
functional testing
defect
condition coverage
29. A functional testing approach in which test cases are designed based on business processes.
conformance testing tools
business process-based testing
incident report
driver
30. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
dynamic analysis tools
defect masking
horizontal traceability
31. Informal testing technique in which test planning and execution run in parallel
multiple condition coverage
data flow structure
exploratory testing
configuration management tools
32. Specific groups that represent a set of valid or invalid partitions for input conditions.
conditions
environmental needs
component integration testing
equivalence partitions
33. 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).
configuration management tools
waterfall model phases
fault attack
incident report identifier
34. A task of maintaining and controlling changes to all entities of a system.
nonfunctional requirements
COTS
experience-based techniques
configuration management
35. The smallest software item that can be tested in isolation.
IEEE incident report template
component
waterfall model phases
cyclomatic complexity
36. Special-purpose software used to simulate a component called by the component under test
stub
incident management tools
test data preparation tools
maintenance testing
37. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
bottom-up integration
coverage measurement tools
failure rate
component integration testing
38. The process of finding analyzing and removing causes of failure in a software product.
cause-effect graphic testing
functional testing tool
functional requirements
debugging
39. Events that occurred during the testing process our investigation.
exploratory testing
Incidents
backbone integration
iterative-incremental development models
40. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
integration testing
black-box testing
risk-based testing
component integration testing
41. A unique identifier for each incident report generated during test execution.
incident report identifier
functional incremental integration
maintainability testing
documentation tools
42. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
inspection
test control Tasks
SW development model
functional requirements
43. White-box design technique used to design test cases for a software component using LCSAJ.
stub
system testing
dynamic analysis tools
LCSAJ testing
44. Occurrences that happen before and after an unexpected event
condition determination coverage
documentation tools
bottom-up integration
anomalous events
45. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
resolution types
failure
defect density
incremental testing
46. 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
documentation tools
test data preparation tools
interoperability testing
acceptance criteria
47. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
incident management tools
functionality
driver
48. Used to test the functionality of software as mentioned in software requirement specifications.
instrumentation
debugging tools
functional testing tool
cyclomatic complexity
49. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
coverage
efficiency
error
50. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
decision table
exhaustive testing
component testing