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. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
coverage measurement tools
testing process phases
integration testing
beta testing
2. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
beta testing
incident report
test planning Tasks
risk-based testing
3. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
integration
functional testing tool
maintainability testing
experience-based techniques
4. Incident Report - Identifier - Summary - Incident - Description - Impact
entry criteria
IEEE incident report template
instrumentation
exploratory testing
5. Ability of software to provide appropriate performance relative to amount of resources used.
failure
IEEE test case specification template
efficiency
impact analysis
6. Black-box testing technique used to create groups of input conditions that create the same kind of output.
risk-based testing
backbone integration
equivalence partitioning
boundary value analysis
7. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
equivalence partitions
maintenance testing
backbone integration
error guessing
8. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
multiple condition coverage
interoperability
decision testing
horizontal traceability
9. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
exit criteria
code coverage
documentation tools
environmental needs
10. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
functional testing
failure rate
functional incremental integration
integration management tools
11. Components are combined and tested in the order in which basic functionalities start working
system testing
test planning Tasks
component integration testing
functional incremental integration
12. The ratio between the number of defects found and the size of the component/system tested.
maintenance testing
component
defect density
Three main SW development models
13. A table showing combinations of inputs and their associated actions.
data flow structure
decision table
beta testing
equivalence partitions
14. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
code coverage
incident management tools
interoperability
test execution tasks
15. A technique used to improve testing coverage by deliberately introducing faults in code.
risk-based testing
equivalence partitions
fault attack
test levels
16. Based on analysis of functional specifications of a system.
Impact subheadings
impact
functional testing
actual result
17. Special-purpose software used to simulate a component that calls the component under test
actual result
driver
independence of testing
defect density
18. 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
maintainability testing
test tool deployment Success Factors
Incidents
IEEE test case specification template
19. Requirements that determine the functionality of a software system.
backbone integration
business process-based testing
functional requirements
condition determination coverage
20. 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
LCSAJ testing
test levels
test data preparation tools
configuration management
21. Tools used to store and manage incidents return phone defects failures or anomalies.
informal review
test data preparation tools
incident management tools
fault attack
22. Used to replace a component that calls another component.
conformance testing tools
fault attack
component
driver
23. Sequence in which data items are accessed or modified by code.
data flow structure
conditions
black-box testing
business process-based testing
24. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
defect masking
fault attack
defect
25. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
decision testing
functionality
condition determination coverage
impact
26. Integration approach components or subsystems are combined all at once rather than in stages.
test analysis & design tasks
big-bang testing
test management tool features
failure rate
27. 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
test analysis & design tasks
incident life cycle phases
actual result
agile software development model
28. One defect prevents the detection of another.
operational testing
Impact subheadings
automation tools
defect masking
29. Special-purpose software used to simulate a component called by the component under test
control flow structure
conformance testing tools
operational testing
stub
30. Insertion of additional code in the existing program in order to count coverage items.
input specifications
instrumentation
incident life cycle phases
boundary value analysis
31. Specific groups that represent a set of valid or invalid partitions for input conditions.
defect masking
coverage measurement tools
iterative-incremental development models
equivalence partitions
32. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
cyclomatic complexity
test condition
test control Tasks
Impact subheadings
33. Testing performed to determine whether the system meets acceptance criteria
cause-effect graphic testing
acceptance testing
code coverage
test implementation tasks
34. Input or combination of inputs required to test software.
debugging
conditions
agile software development model
test levels
35. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
functional requirements
bottom-up integration
monitor
condition coverage
36. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
testing process phases
COTS
configuration management
system testing
37. Behavior or response of a software application that you observe when you execute the action steps in the test case.
error
keyword-driven testing
actual result
integration testing
38. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
COTS
error guessing
test data preparation tools
backbone integration
39. Calculates the number of executed branch outcomes in code.
Three main SW development models
decision coverage
debugging
maintainability testing
40. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
functional requirements
maintainability
test data preparation tools
error
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.
test execution tasks
contract acceptance testing
impact analysis
component
42. Used to test the functionality of software as mentioned in software requirement specifications.
interoperability
coverage
horizontal traceability
functional testing tool
43. A document that provides the structure for writing test cases.
LCSAJ
IEEE test case specification template
efficiency
test data preparation tools
44. Component - Integration - System - Acceptance
test tool deployment Success Factors
test levels
monitor
action
45. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
exit criteria
configuration management tools
iterative-incremental development models
Incidents
46. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
Incidents
actual result
test analysis & design tasks
47. A unique identifier for each incident report generated during test execution.
test log uses
incremental testing
incident report identifier
failure
48. A set of conditions that a system needs to meet in order to be accepted by end users
interoperability testing
acceptance criteria
big-bang testing
acceptance testing
49. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
resolution types
beta testing
control flow structure
waterfall model phases
50. Testing an integrated system to validate it meets requirements
test implementation tasks
equivalence partitioning
driver
system testing