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. A technique used to improve testing coverage by deliberately introducing faults in code.
integration management tools
test execution tasks
incremental testing
fault attack
2. 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).
configuration management tools
environmental needs
test management tool features
exit criteria
3. Ability of software to provide appropriate performance relative to amount of resources used.
test condition
decision table testing
maintenance testing
efficiency
4. The ratio between the number of defects found and the size of the component/system tested.
defect density
Incidents
LCSAJ testing
test analysis & design tasks
5. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
informal review
black-box testing
fault attack
6. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
cause-effect graphic testing
integration management tools
ad hoc integration
resolution types
7. Tests interfaces between components and between integrated components and systems.
defect masking
exploratory testing
code coverage
integration 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
big-bang testing
agile software development model
maintainability
failure
9. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
conformance testing tools
IEEE incident report template
test implementation tasks
10. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
Three main SW development models
keyword-driven testing
boundary value analysis
component testing
11. All possible combinations of input values and preconditions are tested.
instrumentation
impact analysis
incident report
exhaustive testing
12. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
data flow structure
functional testing
condition coverage
ad hoc integration
13. One defect prevents the detection of another.
defect masking
test analysis & design tasks
integration management tools
SW development model
14. A table showing combinations of inputs and their associated actions.
data-driven testing
decision table
impact
anomalous events
15. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.
test log uses
data-driven testing
bottom-up integration
failure
16. Integration approach components or subsystems are combined all at once rather than in stages.
exit criteria
exhaustive testing
system testing
big-bang testing
17. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
coverage measurement tools
conditions
incremental testing
18. Sequence in which data items are accessed or modified by code.
dynamic analysis tools
accuracy
data flow structure
IEEE test case specification template
19. Incident Report - Identifier - Summary - Incident - Description - Impact
maintainability testing
risk-based testing
IEEE incident report template
fault attack
20. A set of conditions that a system needs to meet in order to be accepted by end users
independence of testing
informal review
ad hoc integration
acceptance criteria
21. A document that records the description of each event that occurs during the testing process and that requires further investigation
interoperability testing
incident report
interoperability
horizontal traceability
22. Special additions or changes to the environment required to run a test case.
debugging
action
debugging tools
environmental needs
23. The smallest software item that can be tested in isolation.
testing process phases
contract acceptance testing
component testing
component
24. Special-purpose software used to simulate a component called by the component under test
stub
test management tool features
test log uses
test implementation tasks
25. Components are integrated in the order in which they are developed
Incidents
IEEE test case specification template
exhaustive testing
ad hoc integration
26. Events that occurred during the testing process our investigation.
automation tools
Incidents
functional testing tool
failure
27. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintainability testing
test control Tasks
exhaustive testing
coverage
28. Integrate different kinds of tools to make test management more efficient and simple.
equivalence partitioning
LCSAJ testing
integration management tools
acceptance testing
29. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
multiple condition coverage
impact
decision testing
30. Develop & proiroitize test cases Create groups of test cases Set up test environment
test implementation tasks
waterfall model phases
action
functional testing
31. Human action that generates an incorrect result.
debugging tools
error
impact analysis
IEEE test case specification template
32. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
test implementation tasks
functional incremental integration
environmental needs
iterative-incremental development models
33. Process used to create a SW product from initial conception to public release
SW development model
ad hoc integration
decision table
LCSAJ testing
34. Behavior or response of a software application that you observe when you execute the action steps in the test case.
waterfall model phases
failure rate
actual result
action
35. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
component testing
operational testing
Incidents
36. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
test levels
contract acceptance testing
load testing
37. 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
component testing
inspection
environmental needs
38. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
test tool deployment Success Factors
nonfunctional requirements
ad hoc integration
integration management tools
39. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
stub
exhaustive testing
test management tool features
automation tools
40. An analysis that determines the portion of code on software executed by a set of test cases
keyword-driven testing
agile software development model
informal review
code coverage
41. Occurrences that happen before and after an unexpected event
equivalence partitions
anomalous events
configuration management tools
SW development model
42. Input or combination of inputs required to test software.
environmental needs
efficiency
failure rate
conditions
43. Tools used by developers to identify defects in programs.
debugging tools
acceptance criteria
LCSAJ testing
error
44. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
component
test log uses
defect
instrumentation
45. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
interoperability
coverage
experience-based techniques
test execution tasks
46. 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
informal review
test levels
accuracy
47. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
decision table
automation tools
black-box testing
experience-based techniques
48. Conditions required to begin testing activities.
coverage measurement tools
independence of testing
system testing
entry criteria
49. Insertion of additional code in the existing program in order to count coverage items.
component
test control Tasks
failure
instrumentation
50. Used to test the functionality of software as mentioned in software requirement specifications.
big-bang testing
functional testing tool
error guessing
automation tools