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. Events that occurred during the testing process our investigation.
Incidents
data flow structure
SW development model
incident report identifier
2. Component - Integration - System - Acceptance
test levels
error guessing
test log uses
exploratory testing
3. Measures amount of testing performed by a collection of test cases
environmental needs
acceptance criteria
test data preparation tools
coverage
4. Response of the application to an input
integration
functionality
COTS
action
5. Find defects in code while the software application being tested is running.
decision coverage
condition determination coverage
acceptance criteria
dynamic analysis tools
6. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
decision testing
coverage
testing process phases
test levels
7. Process used to create a SW product from initial conception to public release
SW development model
nonfunctional requirements
component integration testing
LCSAJ testing
8. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
interoperability
control flow structure
documentation tools
functional incremental integration
9. Combining components or sytems into larger structural units or subsystems.
risk-based testing
integration
Three main SW development models
automation tools
10. Requirements that determine the functionality of a software system.
functional requirements
environmental needs
multiple condition coverage
beta testing
11. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
LCSAJ testing
condition coverage
documentation tools
monitor
12. Testing software components that are separately testable. Also module program and unit testing.
incident description subheadings
debugging
component testing
input specifications
13. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
configuration management tools
incident report identifier
decision testing
14. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
functional testing tool
operational testing
condition determination coverage
integration testing
15. A task of maintaining and controlling changes to all entities of a system.
configuration management
informal review
equivalence partitioning
incident description subheadings
16. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
conditions
waterfall model benefits
waterfall model phases
experience-based techniques
17. A review not based on a formal documented procedure
environmental needs
informal review
maintenance testing
incident description subheadings
18. 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
informal review
agile software development model
acceptance criteria
load testing
19. An analysis that determines the portion of code on software executed by a set of test cases
debugging tools
code coverage
test data preparation tools
bottom-up integration
20. Informal testing technique in which test planning and execution run in parallel
impact
condition determination coverage
defect masking
exploratory testing
21. An event or item that can be tested using one or more test cases
impact
multiple condition coverage
test condition
Impact subheadings
22. Conditions required to begin testing activities.
system testing
debugging
defect masking
entry criteria
23. A table showing combinations of inputs and their associated actions.
waterfall model benefits
test condition
decision table
IEEE test case specification template
24. Software products or applications designed to automate manual testing tasks.
error guessing
automation tools
maintenance testing
debugging tools
25. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
maintainability
data-driven testing
driver
26. A unique identifier for each incident report generated during test execution.
Three main SW development models
incident report identifier
maintainability
input specifications
27. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
exit criteria
nonfunctional requirements
cause-effect graphic testing
coverage
28. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
integration testing
experience-based techniques
agile software development model
bottom-up integration
29. 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
SW development model
incident management tools
test execution tasks
30. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
Impact subheadings
interoperability testing
business process-based testing
31. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
incremental testing
decision testing
code coverage
32. The process of finding analyzing and removing causes of failure in a software product.
condition determination coverage
stub
debugging
COTS
33. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
coverage measurement tools
incident description subheadings
integration testing
operational testing
34. 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.
IEEE test case specification template
inspection
waterfall model phases
error guessing
35. A set of conditions that a system needs to meet in order to be accepted by end users
conditions
decision testing
test management tool features
acceptance criteria
36. Actual inputs required to execute a test case
cause-effect graphic testing
anomalous events
decision table testing
input specifications
37. 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
error
informal review
test data preparation tools
38. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
driver
exit criteria
efficiency
functional incremental integration
39. Develop & proiroitize test cases Create groups of test cases Set up test environment
testing process phases
IEEE test case specification template
operational testing
test implementation tasks
40. Tests interfaces between components and between integrated components and systems.
contract acceptance testing
integration testing
control flow structure
inspection
41. The ratio between the number of defects found and the size of the component/system tested.
error guessing
defect density
beta testing
fault attack
42. 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
functional testing
functional requirements
independence of testing
waterfall model benefits
43. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
failure
decision coverage
documentation tools
keyword-driven testing
44. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
action
resolution types
test data preparation tools
data-driven testing
45. Special-purpose software used to simulate a component called by the component under test
stub
decision testing
LCSAJ
big-bang testing
46. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incremental testing
control flow structure
maintainability
anomalous events
47. Insertion of additional code in the existing program in order to count coverage items.
horizontal traceability
component integration testing
instrumentation
incident life cycle phases
48. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
bottom-up integration
test control Tasks
integration testing
interoperability testing
49. A technique used to improve testing coverage by deliberately introducing faults in code.
risk-based testing
fault attack
test analysis & design tasks
component
50. Tools used by developers to identify defects in programs.
debugging tools
beta testing
test analysis & design tasks
input specifications