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. 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
decision table testing
test data preparation tools
condition determination coverage
error
2. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
data-driven testing
test control Tasks
accuracy
equivalence partitions
3. Human action that generates an incorrect result.
waterfall model benefits
equivalence partitioning
test log uses
error
4. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
acceptance testing
condition coverage
cyclomatic complexity
test execution tasks
5. Black-box test design technique - test cases are designed from a decision table.
maintainability testing
IEEE incident report template
COTS
decision table testing
6. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
debugging
risk-based testing
interoperability
Incidents
7. Operational testing performed at an _external_ site without involvement of the developing organization.
IEEE incident report template
business process-based testing
beta testing
test execution tasks
8. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
impact
actual result
dynamic analysis tools
nonfunctional requirements
9. The ratio between the number of defects found and the size of the component/system tested.
horizontal traceability
COTS
defect density
impact analysis
10. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
backbone integration
LCSAJ
component integration testing
11. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
decision testing
testing process phases
alpha testing
exit criteria
12. Informal testing technique in which test planning and execution run in parallel
failure
failure rate
exploratory testing
beta testing
13. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
black-box testing
multiple condition coverage
COTS
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
waterfall model benefits
monitor
coverage measurement tools
anomalous events
15. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
beta testing
documentation tools
test management tool features
functional testing tool
16. A task of maintaining and controlling changes to all entities of a system.
test log uses
keyword-driven testing
maintainability testing
configuration management
17. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
acceptance testing
equivalence partitioning
decision testing
COTS
18. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
component integration testing
incident description subheadings
coverage measurement tools
cyclomatic complexity
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
condition coverage
defect
integration
test planning Tasks
20. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
data-driven testing
actual result
cause-effect graphic testing
21. 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
keyword-driven testing
impact analysis
risk-based testing
22. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
exhaustive testing
SW development model
defect
23. Process used to create a SW product from initial conception to public release
Three main SW development models
component
SW development model
equivalence partitioning
24. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
testing process phases
maintainability
driver
configuration management
25. A document that provides the structure for writing test cases.
integration testing
alpha testing
incident management tools
IEEE test case specification template
26. Testing performed to determine whether the system meets acceptance criteria
LCSAJ testing
acceptance testing
equivalence partitioning
Incidents
27. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
maintainability
agile software development model
test management tool features
boundary value analysis
28. Waterfall iterative-incremental "V"
Three main SW development models
anomalous events
action
IEEE incident report template
29. Develop & proiroitize test cases Create groups of test cases Set up test environment
business process-based testing
test implementation tasks
coverage
maintainability testing
30. Special-purpose software used to simulate a component called by the component under test
configuration management
action
stub
code coverage
31. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
incremental testing
backbone integration
code coverage
informal review
32. Integrate different kinds of tools to make test management more efficient and simple.
debugging tools
waterfall model phases
cyclomatic complexity
integration management tools
33. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
testing process phases
equivalence partitioning
incident management tools
34. Find defects in code while the software application being tested is running.
dynamic analysis tools
incident life cycle phases
test execution tasks
interoperability
35. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
business process-based testing
environmental needs
inspection
36. An event or item that can be tested using one or more test cases
conformance testing tools
alpha testing
black-box testing
test condition
37. Behavior or response of a software application that you observe when you execute the action steps in the test case.
exit criteria
decision table testing
accuracy
actual result
38. A functional testing approach in which test cases are designed based on business processes.
failure
business process-based testing
risk-based testing
decision table testing
39. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
cyclomatic complexity
configuration management
decision coverage
code coverage
40. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
Incidents
risk-based testing
action
41. An analysis that determines the portion of code on software executed by a set of test cases
waterfall model phases
code coverage
interoperability
incident report identifier
42. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
accuracy
resolution types
configuration management tools
43. Occurrences that happen before and after an unexpected event
anomalous events
impact analysis
resolution types
conformance testing tools
44. Used to test the functionality of software as mentioned in software requirement specifications.
driver
integration
functional testing tool
environmental needs
45. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
maintainability testing
Impact subheadings
COTS
46. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
input specifications
accuracy
test levels
47. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
cause-effect graphic testing
experience-based techniques
conformance testing tools
error guessing
48. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
test condition
error guessing
defect density
49. 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
test tool deployment Success Factors
SW development model
cyclomatic complexity
iterative-incremental development models
50. A review not based on a formal documented procedure
informal review
test log uses
exploratory testing
anomalous events