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.
efficiency
test analysis & design tasks
data-driven testing
incident description subheadings
2. 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
data flow structure
test tool deployment Success Factors
exit criteria
functionality
3. Develop & proiroitize test cases Create groups of test cases Set up test environment
component integration testing
test implementation tasks
accuracy
maintainability testing
4. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
test levels
test control Tasks
keyword-driven testing
5. Calculates the number of executed branch outcomes in code.
decision coverage
test levels
decision testing
fault attack
6. 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
multiple condition coverage
test analysis & design tasks
7. Waterfall iterative-incremental "V"
coverage
equivalence partitioning
Three main SW development models
nonfunctional requirements
8. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
testing process phases
functional incremental integration
test execution tasks
keyword-driven testing
9. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
configuration management
alpha testing
exploratory testing
waterfall model benefits
10. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
stub
functional testing tool
experience-based techniques
waterfall model phases
11. Occurrences that happen before and after an unexpected event
exhaustive testing
anomalous events
integration management tools
Impact subheadings
12. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
control flow structure
functionality
exhaustive testing
informal review
13. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
test levels
black-box testing
decision coverage
test execution tasks
14. 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
integration testing
instrumentation
agile software development model
test condition
15. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
driver
conformance testing tools
dynamic analysis tools
interoperability
16. Special-purpose software used to simulate a component that calls the component under test
functional incremental integration
bottom-up integration
driver
cause-effect graphic testing
17. Actual inputs required to execute a test case
instrumentation
input specifications
maintenance testing
component testing
18. Tools used by developers to identify defects in programs.
decision coverage
debugging tools
maintenance testing
system testing
19. A document that provides the structure for writing test cases.
experience-based techniques
defect density
alpha testing
IEEE test case specification template
20. Black-box test design technique - test cases are designed from a decision table.
test analysis & design tasks
decision table testing
test implementation tasks
incident life cycle phases
21. Tests interfaces between components and between integrated components and systems.
accuracy
cyclomatic complexity
test management tool features
integration testing
22. Software products or applications designed to automate manual testing tasks.
automation tools
Incidents
waterfall model benefits
component testing
23. Special additions or changes to the environment required to run a test case.
environmental needs
big-bang testing
independence of testing
defect density
24. 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
coverage measurement tools
test data preparation tools
boundary value analysis
environmental needs
25. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
defect
bottom-up integration
efficiency
26. Testing software in its operational environment
configuration management
impact analysis
operational testing
actual result
27. One defect prevents the detection of another.
functional incremental integration
component
defect masking
conditions
28. Based on analysis of functional specifications of a system.
functional testing
incident report identifier
agile software development model
test control Tasks
29. A set of conditions that a system needs to meet in order to be accepted by end users
test execution tasks
acceptance criteria
incident life cycle phases
driver
30. Ability of software to provide appropriate performance relative to amount of resources used.
IEEE test case specification template
efficiency
integration testing
test condition
31. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
actual result
fault attack
coverage measurement tools
32. Linear Code Sequence and Jump.
operational testing
input specifications
independence of testing
LCSAJ
33. Measures amount of testing performed by a collection of test cases
alpha testing
coverage
Incidents
debugging
34. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
Impact subheadings
LCSAJ
test planning Tasks
multiple condition coverage
35. Testing performed to determine whether the system meets acceptance criteria
LCSAJ testing
acceptance testing
anomalous events
test log uses
36. Component - Integration - System - Acceptance
exit criteria
test levels
test log uses
entry criteria
37. Response of the application to an input
documentation tools
load testing
action
IEEE incident report template
38. Sequence in which instructions are executed through a component or system
control flow structure
test execution tasks
test data preparation tools
component
39. 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
load testing
control flow structure
waterfall model benefits
functionality
40. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
defect density
defect masking
failure rate
condition determination coverage
41. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
contract acceptance testing
integration testing
inspection
Impact subheadings
42. A review not based on a formal documented procedure
cause-effect graphic testing
informal review
incremental testing
SW development model
43. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
configuration management tools
condition determination coverage
IEEE test case specification template
44. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
system testing
risk-based testing
control flow structure
experience-based techniques
45. Conditions required to begin testing activities.
test analysis & design tasks
test data preparation tools
entry criteria
impact
46. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintainability testing
conditions
conformance testing tools
equivalence partitioning
47. Severity - Priority
decision table
functional testing tool
coverage
Impact subheadings
48. The smallest software item that can be tested in isolation.
test condition
component
Impact subheadings
acceptance testing
49. Testing software components that are separately testable. Also module program and unit testing.
testing process phases
stub
data-driven testing
component testing
50. A functional testing approach in which test cases are designed based on business processes.
documentation tools
business process-based testing
beta testing
maintenance testing