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 metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
automation tools
decision table
keyword-driven testing
condition determination coverage
2. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
decision table
monitor
integration testing
decision coverage
3. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
incident description subheadings
maintenance testing
debugging tools
maintainability
4. A document that records the description of each event that occurs during the testing process and that requires further investigation
decision testing
incident report
multiple condition coverage
SW development model
5. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
impact
configuration management
waterfall model phases
coverage
6. Events that occurred during the testing process our investigation.
decision coverage
keyword-driven testing
waterfall model phases
Incidents
7. 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
experience-based techniques
Impact subheadings
test control Tasks
8. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
boundary value analysis
nonfunctional requirements
decision table testing
acceptance criteria
9. A technique used to improve testing coverage by deliberately introducing faults in code.
exit criteria
defect
fault attack
decision table testing
10. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
anomalous events
data flow structure
failure
risk-based testing
11. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
component integration testing
test management tool features
functional incremental integration
LCSAJ
12. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
resolution types
acceptance testing
functional testing
13. Severity - Priority
test planning Tasks
error guessing
test levels
Impact subheadings
14. Calculates the number of executed branch outcomes in code.
operational testing
maintainability
functional incremental integration
decision coverage
15. A task of maintaining and controlling changes to all entities of a system.
functional testing
configuration management
entry criteria
exit criteria
16. Requirements that determine the functionality of a software system.
functional requirements
IEEE test case specification template
interoperability testing
input specifications
17. Measures amount of testing performed by a collection of test cases
coverage
monitor
load testing
debugging tools
18. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
testing process phases
conditions
interoperability testing
cyclomatic complexity
19. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
SW development model
test control Tasks
defect
horizontal traceability
20. 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
configuration management tools
incremental testing
incident management tools
21. Record details of test cases executed Record order of execution record results
conformance testing tools
operational testing
test log uses
defect density
22. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
impact analysis
boundary value analysis
maintainability testing
configuration management tools
23. Special-purpose software used to simulate a component called by the component under test
Three main SW development models
incremental testing
test levels
stub
24. 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
fault attack
resolution types
SW development model
agile software development model
25. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
COTS
impact analysis
cause-effect graphic testing
driver
26. Tools used by developers to identify defects in programs.
component integration testing
efficiency
incident life cycle phases
debugging tools
27. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
black-box testing
component testing
failure rate
test implementation tasks
28. Components are combined and tested in the order in which basic functionalities start working
error guessing
action
functional incremental integration
interoperability testing
29. Components are integrated in the order in which they are developed
IEEE incident report template
component testing
ad hoc integration
input specifications
30. All possible combinations of input values and preconditions are tested.
exhaustive testing
dynamic analysis tools
efficiency
incident management tools
31. Used to replace a component that calls another component.
data flow structure
fault attack
defect
driver
32. 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
exit criteria
test tool deployment Success Factors
cause-effect graphic testing
entry criteria
33. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
COTS
alpha testing
experience-based techniques
monitor
34. Actual inputs required to execute a test case
accuracy
waterfall model phases
input specifications
failure rate
35. Human action that generates an incorrect result.
incident report
error
LCSAJ testing
fault attack
36. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
incident description subheadings
functional testing tool
defect masking
component integration testing
37. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities
test planning Tasks
Incidents
component integration testing
acceptance criteria
38. A unique identifier for each incident report generated during test execution.
COTS
incident report identifier
coverage measurement tools
incident description subheadings
39. 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).
incident description subheadings
configuration management tools
acceptance criteria
beta testing
40. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
error
exit criteria
Impact subheadings
contract acceptance testing
41. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
LCSAJ testing
test implementation tasks
iterative-incremental development models
42. Behavior or response of a software application that you observe when you execute the action steps in the test case.
integration
decision testing
exit criteria
actual result
43. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
big-bang testing
monitor
test analysis & design tasks
44. 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
decision table
functional incremental integration
waterfall model benefits
test execution tasks
45. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.
debugging tools
bottom-up integration
component integration testing
ad hoc integration
46. Software products or applications designed to automate manual testing tasks.
inspection
automation tools
control flow structure
configuration management
47. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test control Tasks
component testing
anomalous events
debugging tools
48. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
driver
monitor
operational testing
backbone integration
49. Examine changes made to an operational system cause defects.
IEEE incident report template
incident life cycle phases
component testing
maintenance testing
50. The smallest software item that can be tested in isolation.
integration management tools
driver
SW development model
component