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. Used to test the functionality of software as mentioned in software requirement specifications.
system testing
driver
alpha testing
functional testing tool
2. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
decision table
equivalence partitions
incident report
3. A review not based on a formal documented procedure
informal review
interoperability
keyword-driven testing
experience-based techniques
4. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
driver
test tool deployment Success Factors
automation tools
5. All possible combinations of input values and preconditions are tested.
multiple condition coverage
horizontal traceability
test tool deployment Success Factors
exhaustive testing
6. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
bottom-up integration
condition coverage
interoperability
anomalous events
7. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
test data preparation tools
incremental testing
data flow structure
incident management tools
8. Tools used to store and manage incidents return phone defects failures or anomalies.
experience-based techniques
iterative-incremental development models
incident management tools
agile software development model
9. Deviation of a software system from its expected delivery services or results
failure
inspection
cause-effect graphic testing
test implementation tasks
10. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
LCSAJ
documentation tools
dynamic analysis tools
test management tool features
11. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
backbone integration
test management tool features
maintainability
cause-effect graphic testing
12. Process used to create a SW product from initial conception to public release
data-driven testing
defect density
SW development model
informal review
13. Testing software components that are separately testable. Also module program and unit testing.
defect masking
impact analysis
actual result
component testing
14. Testing an integrated system to validate it meets requirements
component integration testing
functional testing tool
system testing
resolution types
15. The smallest software item that can be tested in isolation.
beta testing
debugging tools
impact
component
16. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
big-bang testing
iterative-incremental development models
equivalence partitioning
conformance testing tools
17. 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).
black-box testing
decision coverage
code coverage
configuration management tools
18. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
driver
configuration management
LCSAJ testing
19. The ratio between the number of defects found and the size of the component/system tested.
cyclomatic complexity
LCSAJ testing
defect density
instrumentation
20. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
monitor
cyclomatic complexity
experience-based techniques
defect masking
21. Components are combined and tested in the order in which basic functionalities start working
fault attack
defect density
functionality
functional incremental integration
22. One defect prevents the detection of another.
dynamic analysis tools
efficiency
defect masking
entry criteria
23. Events that occurred during the testing process our investigation.
Incidents
test analysis & design tasks
agile software development model
LCSAJ
24. Severity - Priority
driver
load testing
Impact subheadings
keyword-driven testing
25. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
IEEE test case specification template
component integration testing
keyword-driven testing
Impact subheadings
26. Integration approach components or subsystems are combined all at once rather than in stages.
backbone integration
LCSAJ
independence of testing
big-bang testing
27. 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 tool deployment Success Factors
maintainability testing
functionality
iterative-incremental development models
28. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
incident life cycle phases
testing process phases
incremental testing
29. Black-box testing technique used to create groups of input conditions that create the same kind of output.
beta testing
component testing
equivalence partitioning
exit criteria
30. A document that provides the structure for writing test cases.
functional requirements
experience-based techniques
decision testing
IEEE test case specification template
31. A functional testing approach in which test cases are designed based on business processes.
test planning Tasks
business process-based testing
integration
driver
32. Special-purpose software used to simulate a component that calls the component under test
environmental needs
IEEE incident report template
equivalence partitioning
driver
33. Black-box test design technique - test cases are designed from a decision table.
decision table testing
IEEE test case specification template
SW development model
exit criteria
34. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
condition coverage
waterfall model phases
maintainability
entry criteria
35. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
test log uses
experience-based techniques
functional incremental integration
impact analysis
36. Testing software in its operational environment
input specifications
operational testing
error
incident report identifier
37. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
incident management tools
acceptance criteria
COTS
maintainability
38. A document that records the description of each event that occurs during the testing process and that requires further investigation
system testing
incident report
SW development model
cause-effect graphic testing
39. A technique used to improve testing coverage by deliberately introducing faults in code.
agile software development model
exit criteria
functionality
fault attack
40. Software products or applications designed to automate manual testing tasks.
automation tools
test tool deployment Success Factors
Incidents
driver
41. Tests interfaces between components and between integrated components and systems.
bottom-up integration
coverage measurement tools
integration testing
test condition
42. Incident Report - Identifier - Summary - Incident - Description - Impact
maintenance testing
IEEE incident report template
backbone integration
maintainability
43. Operational testing performed at an _external_ site without involvement of the developing organization.
iterative-incremental development models
beta testing
informal review
test control Tasks
44. Allows storage of test input and expected results in one or more central data sources or databases.
cause-effect graphic testing
defect masking
data-driven testing
data flow structure
45. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
keyword-driven testing
functional testing
IEEE test case specification template
defect
46. 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.
inspection
Impact subheadings
failure
conformance testing tools
47. Combining components or sytems into larger structural units or subsystems.
integration
risk-based testing
incident management tools
integration testing
48. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
black-box testing
test control Tasks
decision coverage
boundary value analysis
49. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
component integration testing
actual result
test analysis & design tasks
50. Behavior or response of a software application that you observe when you execute the action steps in the test case.
multiple condition coverage
actual result
exit criteria
decision table