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 document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
functional testing
dynamic analysis tools
test execution tasks
2. Severity - Priority
Impact subheadings
failure rate
defect masking
horizontal traceability
3. Ability of software to provide appropriate performance relative to amount of resources used.
integration testing
coverage
efficiency
LCSAJ
4. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
boundary value analysis
risk-based testing
acceptance criteria
condition determination coverage
5. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
test execution tasks
test condition
defect masking
multiple condition coverage
6. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
experience-based techniques
instrumentation
debugging tools
incident description subheadings
7. An analysis that determines the portion of code on software executed by a set of test cases
impact
incident report
documentation tools
code coverage
8. Software products or applications designed to automate manual testing tasks.
ad hoc integration
test condition
entry criteria
automation tools
9. Record details of test cases executed Record order of execution record results
integration
resolution types
LCSAJ
test log uses
10. Requirements that determine the functionality of a software system.
acceptance criteria
stub
actual result
functional requirements
11. Find defects in code while the software application being tested is running.
fault attack
dynamic analysis tools
incident report identifier
test control Tasks
12. Insertion of additional code in the existing program in order to count coverage items.
informal review
waterfall model benefits
instrumentation
incident management tools
13. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
SW development model
exit criteria
horizontal traceability
conformance testing tools
14. Tools used to store and manage incidents return phone defects failures or anomalies.
input specifications
incident management tools
cause-effect graphic testing
incident description subheadings
15. Integrate different kinds of tools to make test management more efficient and simple.
functional requirements
exit criteria
coverage
integration management tools
16. Occurrences that happen before and after an unexpected event
test management tool features
equivalence partitioning
anomalous events
decision table testing
17. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
iterative-incremental development models
incident life cycle phases
keyword-driven testing
integration management tools
18. Based on analysis of functional specifications of a system.
cyclomatic complexity
functional testing
driver
debugging
19. Used to replace a component that calls another component.
black-box testing
interoperability
driver
defect density
20. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
fault attack
functional requirements
IEEE incident report template
21. Black-box test design technique - test cases are designed from a decision table.
experience-based techniques
data-driven testing
test log uses
decision table testing
22. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
ad hoc integration
alpha testing
boundary value analysis
SW development model
23. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
anomalous events
incident management tools
contract acceptance testing
test management tool features
24. Testing software in its operational environment
operational testing
horizontal traceability
alpha testing
beta testing
25. Increased load (transations) used to test behavior of system under high volume.
acceptance criteria
load testing
data flow structure
functional incremental integration
26. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
multiple condition coverage
integration
incident description subheadings
27. Input or combination of inputs required to test software.
cyclomatic complexity
operational testing
test implementation tasks
conditions
28. 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
agile software development model
business process-based testing
test log uses
decision table
29. Combining components or sytems into larger structural units or subsystems.
failure
incident report
integration
SW development model
30. A unique identifier for each incident report generated during test execution.
SW development model
fault attack
business process-based testing
incident report identifier
31. Response of the application to an input
action
test condition
driver
entry criteria
32. Special-purpose software used to simulate a component that calls the component under test
driver
experience-based techniques
IEEE test case specification template
test condition
33. Process used to create a SW product from initial conception to public release
functional requirements
LCSAJ
SW development model
test execution tasks
34. Sequence in which data items are accessed or modified by code.
incident life cycle phases
impact
test levels
data flow structure
35. Events that occurred during the testing process our investigation.
functional incremental integration
boundary value analysis
Incidents
decision coverage
36. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
LCSAJ testing
decision testing
resolution types
waterfall model phases
37. Component - Integration - System - Acceptance
stub
conformance testing tools
test levels
defect
38. 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
data flow structure
keyword-driven testing
test planning Tasks
defect masking
39. A component of the incident report that determines the actual effect of the incident on the software and its users.
functional testing
control flow structure
error
impact
40. Testing an integrated system to validate it meets requirements
system testing
decision table testing
driver
data-driven testing
41. A review not based on a formal documented procedure
test analysis & design tasks
test execution tasks
data-driven testing
informal review
42. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
test tool deployment Success Factors
stub
Three main SW development models
43. Measures amount of testing performed by a collection of test cases
component
test data preparation tools
coverage
decision table testing
44. Human action that generates an incorrect result.
fault attack
error
integration management tools
exit criteria
45. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
acceptance criteria
waterfall model phases
horizontal traceability
failure
46. Special additions or changes to the environment required to run a test case.
test execution tasks
environmental needs
error guessing
test analysis & design tasks
47. Linear Code Sequence and Jump.
test implementation tasks
LCSAJ
Impact subheadings
instrumentation
48. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
efficiency
incident report
debugging
defect
49. A functional testing approach in which test cases are designed based on business processes.
impact analysis
business process-based testing
test data preparation tools
decision table testing
50. The smallest software item that can be tested in isolation.
component
test planning Tasks
test implementation tasks
defect