SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
accuracy
control flow structure
driver
risk-based testing
2. Conditions required to begin testing activities.
waterfall model phases
acceptance criteria
entry criteria
incident life cycle phases
3. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
black-box testing
configuration management tools
environmental needs
4. 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
input specifications
efficiency
waterfall model phases
test tool deployment Success Factors
5. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
component testing
incremental testing
Impact subheadings
6. Occurrences that happen before and after an unexpected event
horizontal traceability
equivalence partitions
accuracy
anomalous events
7. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
coverage measurement tools
configuration management tools
backbone integration
multiple condition coverage
8. A set of conditions that a system needs to meet in order to be accepted by end users
IEEE incident report template
acceptance criteria
incremental testing
keyword-driven testing
9. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
waterfall model benefits
integration testing
action
multiple condition coverage
10. Special-purpose software used to simulate a component called by the component under test
IEEE test case specification template
stub
test log uses
configuration management tools
11. A document that records the description of each event that occurs during the testing process and that requires further investigation
inspection
incident report
business process-based testing
test implementation tasks
12. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
configuration management
decision testing
decision coverage
instrumentation
13. A table showing combinations of inputs and their associated actions.
business process-based testing
decision table
defect density
LCSAJ testing
14. The smallest software item that can be tested in isolation.
component
Incidents
coverage
Three main SW development models
15. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
action
system testing
boundary value analysis
16. Find defects in code while the software application being tested is running.
component testing
coverage
data-driven testing
dynamic analysis tools
17. Sequence in which instructions are executed through a component or system
control flow structure
configuration management
ad hoc integration
integration testing
18. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
component testing
acceptance criteria
resolution types
business process-based testing
19. All possible combinations of input values and preconditions are tested.
LCSAJ testing
conformance testing tools
exhaustive testing
defect density
20. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
component testing
interoperability
experience-based techniques
interoperability testing
21. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
test control Tasks
decision table testing
resolution types
22. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
Three main SW development models
interoperability testing
black-box testing
driver
23. Component - Integration - System - Acceptance
test levels
test management tool features
error
functional testing
24. The ratio between the number of defects found and the size of the component/system tested.
Incidents
conformance testing tools
defect density
test management tool features
25. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
environmental needs
horizontal traceability
system testing
documentation tools
26. A task of maintaining and controlling changes to all entities of a system.
incident description subheadings
experience-based techniques
configuration management
test management tool features
27. Process used to create a SW product from initial conception to public release
error guessing
beta testing
SW development model
test control Tasks
28. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
component testing
error
failure rate
Three main SW development models
29. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test tool deployment Success Factors
test analysis & design tasks
component
IEEE test case specification template
30. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
integration
maintainability testing
interoperability
incremental testing
31. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test log uses
test management tool features
IEEE incident report template
decision coverage
32. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
testing process phases
functional testing
alpha testing
conformance testing tools
33. Requirements that determine the functionality of a software system.
failure
load testing
functional requirements
decision table
34. A functional testing approach in which test cases are designed based on business processes.
component testing
LCSAJ
business process-based testing
agile software development model
35. Deviation of a software system from its expected delivery services or results
data flow structure
beta testing
iterative-incremental development models
failure
36. Testing software in its operational environment
operational testing
accuracy
inspection
horizontal traceability
37. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
functional requirements
exit criteria
inspection
COTS
38. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
informal review
coverage measurement tools
stub
condition coverage
39. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
incident report identifier
Three main SW development models
condition determination coverage
exploratory testing
40. Specific groups that represent a set of valid or invalid partitions for input conditions.
iterative-incremental development models
functional testing tool
equivalence partitions
exploratory testing
41. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect density
actual result
defect
cyclomatic complexity
42. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
multiple condition coverage
driver
debugging
functionality
43. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
cause-effect graphic testing
exit criteria
interoperability
stub
44. 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 execution tasks
test control Tasks
interoperability testing
decision testing
45. 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
conditions
conformance testing tools
horizontal traceability
test data preparation tools
46. Events that occurred during the testing process our investigation.
iterative-incremental development models
Incidents
failure rate
defect density
47. Measures amount of testing performed by a collection of test cases
horizontal traceability
coverage
IEEE test case specification template
incremental testing
48. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component
component integration testing
fault attack
SW development model
49. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
functional testing tool
instrumentation
test execution tasks
ad hoc integration
50. Record details of test cases executed Record order of execution record results
testing process phases
test log uses
system testing
experience-based techniques