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. Integrate different kinds of tools to make test management more efficient and simple.
informal review
maintenance testing
integration management tools
decision testing
2. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
Incidents
experience-based techniques
test levels
maintainability
3. Examine changes made to an operational system cause defects.
waterfall model phases
maintenance testing
incident description subheadings
error guessing
4. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
entry criteria
multiple condition coverage
maintainability testing
decision table testing
5. 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).
ad hoc integration
test execution tasks
stub
configuration management tools
6. Ability of software to provide appropriate performance relative to amount of resources used.
incident report
efficiency
failure rate
maintainability
7. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
stub
component testing
Impact subheadings
condition coverage
8. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
impact
agile software development model
driver
9. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
exhaustive testing
test log uses
coverage
10. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
code coverage
interoperability testing
dynamic analysis tools
11. 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 implementation tasks
test control Tasks
test planning Tasks
contract acceptance testing
12. Special-purpose software used to simulate a component that calls the component under test
code coverage
debugging
driver
risk-based testing
13. 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
waterfall model benefits
bottom-up integration
code coverage
control flow structure
14. Sequence in which data items are accessed or modified by code.
LCSAJ
component integration testing
condition coverage
data flow structure
15. All possible combinations of input values and preconditions are tested.
incident management tools
documentation tools
exhaustive testing
interoperability testing
16. Testing software in its operational environment
horizontal traceability
incident management tools
operational testing
test management tool features
17. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
multiple condition coverage
incident report identifier
boundary value analysis
instrumentation
18. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
bottom-up integration
conditions
business process-based testing
maintainability
19. 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
defect masking
test planning Tasks
incident management tools
boundary value analysis
20. Waterfall iterative-incremental "V"
test log uses
integration testing
test levels
Three main SW development models
21. 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
condition coverage
conditions
action
test data preparation tools
22. The capability of a software product to provide agreed and correct output with the required degree of precision
condition determination coverage
bottom-up integration
accuracy
functional requirements
23. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
test levels
iterative-incremental development models
incident description subheadings
automation tools
24. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
incident life cycle phases
maintainability
anomalous events
25. Events that occurred during the testing process our investigation.
test execution tasks
control flow structure
fault attack
Incidents
26. Black-box testing technique used to create groups of input conditions that create the same kind of output.
bottom-up integration
documentation tools
defect density
equivalence partitioning
27. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
incremental testing
coverage measurement tools
driver
28. Software products or applications designed to automate manual testing tasks.
automation tools
maintenance testing
test execution tasks
component integration testing
29. Linear Code Sequence and Jump.
incident description subheadings
LCSAJ
decision table testing
driver
30. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
Incidents
beta testing
failure rate
testing process phases
31. Response of the application to an input
defect
action
horizontal traceability
test levels
32. Based on analysis of functional specifications of a system.
test implementation tasks
functional testing
system testing
decision table testing
33. Conditions required to begin testing activities.
exit criteria
component integration testing
entry criteria
coverage measurement tools
34. Special-purpose software used to simulate a component called by the component under test
data-driven testing
functionality
component
stub
35. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
boundary value analysis
operational testing
cause-effect graphic testing
risk-based testing
36. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
configuration management
horizontal traceability
ad hoc integration
test execution tasks
37. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
maintainability testing
incident description subheadings
cyclomatic complexity
functional testing tool
38. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
black-box testing
exploratory testing
impact analysis
39. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
actual result
interoperability
action
impact analysis
40. A component of the incident report that determines the actual effect of the incident on the software and its users.
failure rate
condition coverage
impact
interoperability testing
41. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
error guessing
debugging tools
exit criteria
42. Operational testing performed at an _external_ site without involvement of the developing organization.
component testing
test implementation tasks
backbone integration
beta testing
43. A functional testing approach in which test cases are designed based on business processes.
LCSAJ
waterfall model phases
business process-based testing
experience-based techniques
44. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
maintenance testing
IEEE incident report template
independence of testing
45. A table showing combinations of inputs and their associated actions.
IEEE test case specification template
testing process phases
decision table
multiple condition coverage
46. 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
decision coverage
equivalence partitions
agile software development model
decision table testing
47. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
error guessing
cyclomatic complexity
test implementation tasks
stub
48. Specific groups that represent a set of valid or invalid partitions for input conditions.
condition determination coverage
error guessing
equivalence partitions
informal review
49. Requirements that determine the functionality of a software system.
functional testing tool
configuration management tools
functional requirements
maintainability
50. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
interoperability
actual result
functionality
black-box testing