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 test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
experience-based techniques
waterfall model benefits
decision testing
incremental testing
2. A set of conditions that a system needs to meet in order to be accepted by end users
IEEE incident report template
defect masking
test management tool features
acceptance criteria
3. Occurrences that happen before and after an unexpected event
anomalous events
contract acceptance testing
debugging tools
test control Tasks
4. Testing software in its operational environment
interoperability
operational testing
inspection
maintainability testing
5. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
failure
data flow structure
waterfall model benefits
6. Components are integrated in the order in which they are developed
coverage
cause-effect graphic testing
monitor
ad hoc integration
7. Sequence in which data items are accessed or modified by code.
data flow structure
big-bang testing
configuration management
informal review
8. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
integration testing
COTS
IEEE incident report template
9. Response of the application to an input
action
acceptance criteria
failure rate
decision coverage
10. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
maintainability testing
testing process phases
alpha testing
11. Deviation of a software system from its expected delivery services or results
system testing
interoperability
failure
data-driven testing
12. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
backbone integration
keyword-driven testing
driver
13. Component - Integration - System - Acceptance
backbone integration
action
test levels
system testing
14. 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
risk-based testing
incident report
waterfall model benefits
defect
15. Tools used by developers to identify defects in programs.
Impact subheadings
debugging tools
test levels
contract acceptance testing
16. Testing software components that are separately testable. Also module program and unit testing.
component testing
integration testing
ad hoc integration
LCSAJ
17. Conditions required to begin testing activities.
entry criteria
defect masking
inspection
equivalence partitions
18. A document that provides the structure for writing test cases.
IEEE test case specification template
cyclomatic complexity
conformance testing tools
anomalous events
19. A table showing combinations of inputs and their associated actions.
IEEE test case specification template
incident report identifier
decision table
equivalence partitions
20. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
condition determination coverage
interoperability
operational testing
resolution types
21. One defect prevents the detection of another.
defect masking
alpha testing
interoperability
load testing
22. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
multiple condition coverage
test control Tasks
functionality
test analysis & design tasks
23. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
test planning Tasks
LCSAJ
ad hoc integration
24. Integrate different kinds of tools to make test management more efficient and simple.
maintainability testing
equivalence partitions
LCSAJ testing
integration management tools
25. Combining components or sytems into larger structural units or subsystems.
decision table
integration
equivalence partitioning
Three main SW development models
26. A task of maintaining and controlling changes to all entities of a system.
maintainability
keyword-driven testing
condition coverage
configuration management
27. Linear Code Sequence and Jump.
LCSAJ
conformance testing tools
functional testing tool
backbone integration
28. Human action that generates an incorrect result.
error
test control Tasks
driver
equivalence partitioning
29. Requirements that determine the functionality of a software system.
functional requirements
experience-based techniques
functionality
maintainability testing
30. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
exhaustive testing
decision testing
automation tools
horizontal traceability
31. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
efficiency
impact analysis
defect masking
32. Used to replace a component that calls another component.
driver
test tool deployment Success Factors
equivalence partitions
interoperability testing
33. An event or item that can be tested using one or more test cases
fault attack
iterative-incremental development models
test condition
Impact subheadings
34. Allows storage of test input and expected results in one or more central data sources or databases.
automation tools
defect
data-driven testing
test data preparation tools
35. 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
condition determination coverage
test planning Tasks
data flow structure
cause-effect graphic testing
36. 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
multiple condition coverage
ad hoc integration
test tool deployment Success Factors
contract acceptance testing
37. Black-box test design technique - test cases are designed from a decision table.
driver
decision table testing
defect density
decision table
38. A functional testing approach in which test cases are designed based on business processes.
business process-based testing
agile software development model
functional testing
LCSAJ
39. All possible combinations of input values and preconditions are tested.
exit criteria
exhaustive testing
functional requirements
LCSAJ
40. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
horizontal traceability
code coverage
incident description subheadings
actual result
41. 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
waterfall model phases
control flow structure
test data preparation tools
entry criteria
42. A unique identifier for each incident report generated during test execution.
functionality
resolution types
incident report identifier
IEEE test case specification template
43. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
Three main SW development models
environmental needs
error
44. Input or combination of inputs required to test software.
test data preparation tools
exploratory testing
cyclomatic complexity
conditions
45. Record details of test cases executed Record order of execution record results
functional testing tool
instrumentation
test log uses
defect
46. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
input specifications
inspection
informal review
47. A document that records the description of each event that occurs during the testing process and that requires further investigation
maintenance testing
decision table testing
test tool deployment Success Factors
incident report
48. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
test control Tasks
maintainability testing
test planning Tasks
condition determination coverage
49. Tests interfaces between components and between integrated components and systems.
integration testing
waterfall model benefits
test implementation tasks
debugging
50. Software products or applications designed to automate manual testing tasks.
incident description subheadings
environmental needs
automation tools
action