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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
operational testing
integration
anomalous events
interoperability testing
2. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
incident description subheadings
monitor
big-bang testing
3. An event or item that can be tested using one or more test cases
test condition
fault attack
test levels
failure rate
4. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
interoperability
test execution tasks
efficiency
documentation tools
5. 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
COTS
component integration testing
impact
6. Find defects in code while the software application being tested is running.
data-driven testing
dynamic analysis tools
decision testing
risk-based testing
7. Actual inputs required to execute a test case
interoperability testing
SW development model
LCSAJ
input specifications
8. Deviation of a software system from its expected delivery services or results
functional requirements
incident life cycle phases
failure
configuration management tools
9. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
debugging tools
multiple condition coverage
conformance testing tools
COTS
10. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
conditions
equivalence partitions
defect masking
11. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
defect masking
incident life cycle phases
acceptance testing
backbone integration
12. One defect prevents the detection of another.
defect masking
SW development model
big-bang testing
Impact subheadings
13. A document that records the description of each event that occurs during the testing process and that requires further investigation
integration
multiple condition coverage
business process-based testing
incident report
14. A task of maintaining and controlling changes to all entities of a system.
configuration management tools
IEEE incident report template
configuration management
exhaustive testing
15. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
iterative-incremental development models
efficiency
driver
16. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
acceptance criteria
error
waterfall model phases
17. 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
condition determination coverage
integration
18. Sequence in which data items are accessed or modified by code.
data flow structure
documentation tools
test analysis & design tasks
iterative-incremental development models
19. Special additions or changes to the environment required to run a test case.
documentation tools
code coverage
environmental needs
Incidents
20. Allows storage of test input and expected results in one or more central data sources or databases.
maintainability testing
cyclomatic complexity
data-driven testing
functional incremental integration
21. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
inspection
acceptance criteria
maintainability testing
impact
22. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
operational testing
test data preparation tools
exit criteria
23. 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
test control Tasks
black-box testing
incident report identifier
test tool deployment Success Factors
24. Measures amount of testing performed by a collection of test cases
functional incremental integration
decision coverage
coverage
defect masking
25. An analysis that determines the portion of code on software executed by a set of test cases
dynamic analysis tools
code coverage
iterative-incremental development models
resolution types
26. 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.
conformance testing tools
backbone integration
alpha testing
inspection
27. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
defect masking
interoperability testing
test log uses
28. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
waterfall model benefits
COTS
keyword-driven testing
integration testing
29. Testing software components that are separately testable. Also module program and unit testing.
Impact subheadings
incremental testing
component testing
impact
30. Component - Integration - System - Acceptance
integration management tools
functional requirements
test levels
iterative-incremental development models
31. Black-box testing technique used to create groups of input conditions that create the same kind of output.
maintenance testing
environmental needs
equivalence partitioning
interoperability testing
32. Sequence in which instructions are executed through a component or system
acceptance criteria
incident report identifier
IEEE incident report template
control flow structure
33. The smallest software item that can be tested in isolation.
test execution tasks
ad hoc integration
component
data-driven testing
34. Response of the application to an input
test tool deployment Success Factors
code coverage
action
entry criteria
35. Linear Code Sequence and Jump.
failure rate
configuration management
defect masking
LCSAJ
36. Black-box test design technique - test cases are designed from a decision table.
decision table testing
decision coverage
incident report identifier
coverage measurement tools
37. A review not based on a formal documented procedure
LCSAJ
data-driven testing
condition determination coverage
informal review
38. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test analysis & design tasks
test planning Tasks
defect density
cause-effect graphic testing
39. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
LCSAJ testing
test control Tasks
boundary value analysis
monitor
40. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
coverage measurement tools
IEEE incident report template
configuration management
monitor
41. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
monitor
experience-based techniques
alpha testing
defect density
42. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
waterfall model phases
system testing
instrumentation
43. Occurrences that happen before and after an unexpected event
functional testing tool
anomalous events
inspection
control flow structure
44. Based on analysis of functional specifications of a system.
functional testing
SW development model
exhaustive testing
debugging tools
45. Ability of software to provide appropriate performance relative to amount of resources used.
coverage
configuration management
efficiency
exit criteria
46. Requirements that determine the functionality of a software system.
functional requirements
test management tool features
waterfall model phases
boundary value analysis
47. Special-purpose software used to simulate a component that calls the component under test
driver
decision table testing
test control Tasks
functionality
48. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
condition determination coverage
exit criteria
system testing
interoperability testing
49. Tools used by developers to identify defects in programs.
beta testing
defect density
LCSAJ testing
debugging tools
50. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
COTS
coverage measurement tools
condition coverage
maintainability