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. Requirements that determine the functionality of a software system.
integration
debugging
maintenance testing
functional requirements
2. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
cause-effect graphic testing
documentation tools
defect
debugging tools
3. Sequence in which data items are accessed or modified by code.
ad hoc integration
data flow structure
test levels
equivalence partitioning
4. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
exit criteria
contract acceptance testing
defect masking
incident description subheadings
5. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
component integration testing
integration management tools
resolution types
bottom-up integration
6. Find defects in code while the software application being tested is running.
dynamic analysis tools
actual result
beta testing
Incidents
7. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
documentation tools
failure rate
experience-based techniques
boundary value analysis
8. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintainability testing
actual result
efficiency
LCSAJ testing
9. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
entry criteria
impact analysis
data-driven testing
functional incremental integration
10. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
boundary value analysis
functional testing
incident report identifier
11. Special-purpose software used to simulate a component called by the component under test
exhaustive testing
decision testing
entry criteria
stub
12. Occurrences that happen before and after an unexpected event
anomalous events
test levels
contract acceptance testing
debugging tools
13. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
system testing
contract acceptance testing
risk-based testing
14. A review not based on a formal documented procedure
informal review
condition coverage
coverage
functionality
15. Linear Code Sequence and Jump.
test control Tasks
LCSAJ
exhaustive testing
action
16. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
dynamic analysis tools
cause-effect graphic testing
test analysis & design tasks
17. Measures amount of testing performed by a collection of test cases
risk-based testing
condition coverage
coverage
beta testing
18. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
documentation tools
test analysis & design tasks
component integration testing
testing process phases
19. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
IEEE test case specification template
functional testing tool
maintainability
functional incremental integration
20. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
incremental testing
testing process phases
functional testing
21. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
driver
IEEE incident report template
entry criteria
22. 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
Incidents
test execution tasks
test data preparation tools
exit criteria
23. Human action that generates an incorrect result.
test planning Tasks
error
debugging tools
incident life cycle phases
24. Black-box testing technique used to create groups of input conditions that create the same kind of output.
business process-based testing
resolution types
interoperability
equivalence partitioning
25. Calculates the number of executed branch outcomes in code.
functional incremental integration
configuration management
decision coverage
functional requirements
26. 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).
SW development model
configuration management tools
incident report identifier
beta testing
27. Software products or applications designed to automate manual testing tasks.
configuration management tools
beta testing
test implementation tasks
automation tools
28. Components are integrated in the order in which they are developed
monitor
ad hoc integration
conformance testing tools
code coverage
29. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
test execution tasks
interoperability
defect masking
dynamic analysis tools
30. A functional testing approach in which test cases are designed based on business processes.
fault attack
business process-based testing
incident life cycle phases
horizontal traceability
31. 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
entry criteria
decision coverage
anomalous events
32. Severity - Priority
Impact subheadings
independence of testing
driver
incident description subheadings
33. 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
configuration management tools
incident description subheadings
test tool deployment Success Factors
34. Special additions or changes to the environment required to run a test case.
error guessing
test data preparation tools
maintainability
environmental needs
35. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
test analysis & design tasks
integration management tools
interoperability testing
36. A unique identifier for each incident report generated during test execution.
test log uses
incident report identifier
cyclomatic complexity
efficiency
37. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
input specifications
failure
interoperability
system testing
38. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
boundary value analysis
component testing
testing process phases
acceptance criteria
39. Tools used to store and manage incidents return phone defects failures or anomalies.
risk-based testing
functional testing tool
functional testing
incident management tools
40. A technique used to improve testing coverage by deliberately introducing faults in code.
business process-based testing
fault attack
decision coverage
waterfall model phases
41. Tools used to identify and calculate coverage items in program code.
boundary value analysis
error
coverage measurement tools
component
42. The process of finding analyzing and removing causes of failure in a software product.
exploratory testing
debugging
dynamic analysis tools
incident life cycle phases
43. 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
alpha testing
horizontal traceability
decision testing
44. Based on analysis of functional specifications of a system.
keyword-driven testing
efficiency
dynamic analysis tools
functional testing
45. Testing software in its operational environment
operational testing
incremental testing
environmental needs
control flow structure
46. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
action
condition determination coverage
component testing
environmental needs
47. Operational testing performed at an _external_ site without involvement of the developing organization.
instrumentation
interoperability
beta testing
inspection
48. Response of the application to an input
monitor
functional incremental integration
action
inspection
49. The ratio between the number of defects found and the size of the component/system tested.
experience-based techniques
defect density
action
driver
50. Conditions required to begin testing activities.
debugging tools
test management tool features
multiple condition coverage
entry criteria