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. Tools used to identify and calculate coverage items in program code.
test planning Tasks
coverage measurement tools
data flow structure
cause-effect graphic testing
2. Tests interfaces between components and between integrated components and systems.
agile software development model
IEEE incident report template
defect density
integration testing
3. The process of finding analyzing and removing causes of failure in a software product.
contract acceptance testing
debugging
big-bang testing
acceptance criteria
4. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
COTS
LCSAJ
input specifications
functionality
5. Special additions or changes to the environment required to run a test case.
environmental needs
system testing
business process-based testing
incident description subheadings
6. 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
test data preparation tools
incident management tools
equivalence partitioning
bottom-up integration
7. Combining components or sytems into larger structural units or subsystems.
informal review
input specifications
integration
independence of testing
8. 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
impact
functionality
agile software development model
backbone integration
9. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
equivalence partitions
decision testing
independence of testing
defect density
10. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
ad hoc integration
accuracy
load testing
keyword-driven testing
11. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
test control Tasks
iterative-incremental development models
defect masking
risk-based testing
12. Conditions required to begin testing activities.
contract acceptance testing
entry criteria
incident description subheadings
LCSAJ
13. 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
ad hoc integration
Three main SW development models
operational testing
test planning Tasks
14. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
business process-based testing
test management tool features
incident life cycle phases
test tool deployment Success Factors
15. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
test condition
test tool deployment Success Factors
coverage
incident life cycle phases
16. Ability of software to provide appropriate performance relative to amount of resources used.
decision coverage
interoperability
decision testing
efficiency
17. Occurrences that happen before and after an unexpected event
impact
test analysis & design tasks
anomalous events
big-bang testing
18. Special-purpose software used to simulate a component called by the component under test
stub
decision table testing
acceptance criteria
equivalence partitioning
19. 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
waterfall model phases
Three main SW development models
integration testing
20. The ratio between the number of defects found and the size of the component/system tested.
instrumentation
condition determination coverage
defect density
SW development model
21. Based on analysis of functional specifications of a system.
debugging tools
Three main SW development models
functional testing
boundary value analysis
22. Process used to create a SW product from initial conception to public release
operational testing
data flow structure
SW development model
incremental testing
23. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
alpha testing
coverage measurement tools
interoperability testing
24. Sequence in which instructions are executed through a component or system
control flow structure
configuration management tools
defect masking
exploratory testing
25. Components are integrated in the order in which they are developed
test tool deployment Success Factors
ad hoc integration
dynamic analysis tools
Impact subheadings
26. Record details of test cases executed Record order of execution record results
test log uses
big-bang testing
component testing
independence of testing
27. Events that occurred during the testing process our investigation.
data flow structure
configuration management
risk-based testing
Incidents
28. The smallest software item that can be tested in isolation.
alpha testing
component
driver
test log uses
29. Human action that generates an incorrect result.
exploratory testing
informal review
error
debugging tools
30. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
coverage
functional testing tool
interoperability
incremental testing
31. Input or combination of inputs required to test software.
debugging
conditions
equivalence partitioning
defect masking
32. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
instrumentation
test data preparation tools
failure rate
resolution types
33. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
equivalence partitions
decision table testing
horizontal traceability
waterfall model phases
34. Testing performed to determine whether the system meets acceptance criteria
anomalous events
acceptance testing
exhaustive testing
iterative-incremental development models
35. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
incident report identifier
black-box testing
environmental needs
testing process phases
36. Components are combined and tested in the order in which basic functionalities start working
exit criteria
functional incremental integration
test condition
maintainability
37. A document that provides the structure for writing test cases.
IEEE test case specification template
equivalence partitioning
decision coverage
test tool deployment Success Factors
38. All possible combinations of input values and preconditions are tested.
component
integration management tools
incident management tools
exhaustive testing
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).
functional requirements
contract acceptance testing
horizontal traceability
configuration management tools
40. Requirements that determine the functionality of a software system.
defect density
functional requirements
independence of testing
operational testing
41. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
component
maintainability
test management tool features
error guessing
42. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
test analysis & design tasks
impact analysis
acceptance criteria
incremental testing
43. 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
functional requirements
maintainability testing
test tool deployment Success Factors
debugging tools
44. 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
test control Tasks
maintenance testing
defect density
45. Develop & proiroitize test cases Create groups of test cases Set up test environment
incident report
resolution types
test implementation tasks
incremental testing
46. A technique used to improve testing coverage by deliberately introducing faults in code.
black-box testing
resolution types
test levels
fault attack
47. Linear Code Sequence and Jump.
LCSAJ
failure rate
efficiency
exhaustive testing
48. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
instrumentation
waterfall model phases
COTS
defect
49. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
condition determination coverage
boundary value analysis
interoperability testing
backbone integration
50. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
component integration testing
interoperability testing
failure rate
integration