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. 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
integration
waterfall model benefits
defect masking
IEEE incident report template
2. The smallest software item that can be tested in isolation.
integration management tools
component
maintenance testing
dynamic analysis tools
3. Sequence in which data items are accessed or modified by code.
informal review
system testing
Incidents
data flow structure
4. 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
debugging
agile software development model
iterative-incremental development models
system testing
5. The process of finding analyzing and removing causes of failure in a software product.
automation tools
debugging
system testing
bottom-up integration
6. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
functional incremental integration
IEEE test case specification template
nonfunctional requirements
7. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
decision table
condition determination coverage
incident life cycle phases
8. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
risk-based testing
inspection
condition determination coverage
9. Severity - Priority
exit criteria
Impact subheadings
configuration management
impact analysis
10. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
IEEE test case specification template
incremental testing
coverage
11. A table showing combinations of inputs and their associated actions.
decision table
risk-based testing
inspection
incident report
12. 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
functionality
anomalous events
inspection
13. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
data-driven testing
functionality
boundary value analysis
debugging tools
14. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
boundary value analysis
ad hoc integration
anomalous events
keyword-driven testing
15. Tools used to identify and calculate coverage items in program code.
functional requirements
coverage measurement tools
conditions
decision coverage
16. Process used to create a SW product from initial conception to public release
SW development model
condition determination coverage
anomalous events
component testing
17. Testing software in its operational environment
configuration management tools
operational testing
input specifications
actual result
18. Behavior or response of a software application that you observe when you execute the action steps in the test case.
dynamic analysis tools
actual result
incident life cycle phases
exhaustive testing
19. All possible combinations of input values and preconditions are tested.
alpha testing
exhaustive testing
component
exploratory testing
20. 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
test data preparation tools
incident report identifier
conformance testing tools
21. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
defect
maintenance testing
incremental testing
test execution tasks
22. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
contract acceptance testing
documentation tools
error guessing
IEEE test case specification template
23. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
equivalence partitions
system testing
COTS
test analysis & design tasks
24. Tools used by developers to identify defects in programs.
error
multiple condition coverage
debugging tools
boundary value analysis
25. Find defects in code while the software application being tested is running.
input specifications
business process-based testing
impact
dynamic analysis tools
26. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
debugging tools
IEEE test case specification template
resolution types
failure rate
27. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
Three main SW development models
conditions
test planning Tasks
28. Sequence in which instructions are executed through a component or system
decision testing
test log uses
debugging tools
control flow structure
29. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
horizontal traceability
alpha testing
condition determination coverage
30. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
LCSAJ
black-box testing
documentation tools
IEEE test case specification template
31. Software products or applications designed to automate manual testing tasks.
conformance testing tools
beta testing
coverage measurement tools
automation tools
32. Events that occurred during the testing process our investigation.
Incidents
monitor
IEEE test case specification template
condition determination coverage
33. Deviation of a software system from its expected delivery services or results
waterfall model benefits
test tool deployment Success Factors
dynamic analysis tools
failure
34. Input or combination of inputs required to test software.
efficiency
incident life cycle phases
decision table
conditions
35. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
incident report
error guessing
defect density
36. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
backbone integration
integration management tools
action
37. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
integration management tools
system testing
ad hoc integration
38. A review not based on a formal documented procedure
acceptance testing
informal review
black-box testing
condition coverage
39. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintainability testing
monitor
functional requirements
debugging tools
40. A document that provides the structure for writing test cases.
IEEE test case specification template
decision table testing
SW development model
business process-based testing
41. 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).
keyword-driven testing
nonfunctional requirements
configuration management tools
functional testing
42. A document that records the description of each event that occurs during the testing process and that requires further investigation
input specifications
maintainability testing
SW development model
incident report
43. Conditions required to begin testing activities.
load testing
entry criteria
acceptance criteria
decision table testing
44. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
decision testing
nonfunctional requirements
multiple condition coverage
exit criteria
45. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
COTS
debugging
incremental testing
monitor
46. 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
incremental testing
decision coverage
bottom-up integration
test data preparation tools
47. Occurrences that happen before and after an unexpected event
stub
COTS
action
anomalous events
48. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
big-bang testing
condition coverage
functionality
action
49. Operational testing performed at an _external_ site without involvement of the developing organization.
data-driven testing
horizontal traceability
beta testing
iterative-incremental development models
50. Ability of software to provide appropriate performance relative to amount of resources used.
impact analysis
efficiency
test tool deployment Success Factors
data flow structure