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. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
maintainability
iterative-incremental development models
configuration management tools
2. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
fault attack
horizontal traceability
IEEE test case specification template
3. Human action that generates an incorrect result.
environmental needs
testing process phases
system testing
error
4. 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
integration testing
driver
waterfall model benefits
5. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
failure
monitor
Incidents
impact
6. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
impact analysis
test execution tasks
nonfunctional requirements
incident life cycle phases
7. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
equivalence partitioning
anomalous events
waterfall model benefits
8. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
experience-based techniques
incident life cycle phases
documentation tools
9. Response of the application to an input
system testing
data-driven testing
action
LCSAJ testing
10. Testing performed to determine whether the system meets acceptance criteria
incident description subheadings
acceptance testing
test planning Tasks
debugging tools
11. Tools used by developers to identify defects in programs.
environmental needs
test control Tasks
debugging tools
input specifications
12. Actual inputs required to execute a test case
input specifications
configuration management
test execution tasks
defect
13. The ratio between the number of defects found and the size of the component/system tested.
beta testing
acceptance criteria
defect density
test execution tasks
14. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
fault attack
system testing
keyword-driven testing
15. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.
equivalence partitioning
bottom-up integration
failure rate
condition coverage
16. A task of maintaining and controlling changes to all entities of a system.
agile software development model
failure rate
configuration management
bottom-up integration
17. All possible combinations of input values and preconditions are tested.
automation tools
anomalous events
alpha testing
exhaustive testing
18. Separation of testing responsibilities which encourages the accomplishment of objective testing
decision coverage
functional testing tool
independence of testing
functional requirements
19. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
load testing
incremental testing
interoperability testing
conformance testing tools
20. Occurrences that happen before and after an unexpected event
functional testing
COTS
anomalous events
bottom-up integration
21. Testing software in its operational environment
test tool deployment Success Factors
agile software development model
operational testing
data-driven testing
22. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
system testing
acceptance testing
dynamic analysis tools
23. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
independence of testing
decision table testing
test levels
impact analysis
24. Behavior or response of a software application that you observe when you execute the action steps in the test case.
test management tool features
coverage measurement tools
COTS
actual result
25. 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).
control flow structure
configuration management tools
driver
maintainability testing
26. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
entry criteria
decision table testing
interoperability testing
risk-based testing
27. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
integration
agile software development model
driver
28. Sequence in which instructions are executed through a component or system
test tool deployment Success Factors
exploratory testing
control flow structure
coverage measurement tools
29. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
action
debugging
failure
black-box testing
30. Specific groups that represent a set of valid or invalid partitions for input conditions.
acceptance criteria
functional testing
data flow structure
equivalence partitions
31. Conditions required to begin testing activities.
entry criteria
risk-based testing
acceptance criteria
maintenance testing
32. Increased load (transations) used to test behavior of system under high volume.
actual result
boundary value analysis
test implementation tasks
load testing
33. A technique used to improve testing coverage by deliberately introducing faults in code.
instrumentation
fault attack
Three main SW development models
big-bang testing
34. Special additions or changes to the environment required to run a test case.
environmental needs
test execution tasks
coverage
defect
35. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
cyclomatic complexity
LCSAJ
stub
36. Special-purpose software used to simulate a component called by the component under test
defect
integration management tools
stub
test tool deployment Success Factors
37. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
big-bang testing
defect
integration management tools
test execution tasks
38. Used to test the functionality of software as mentioned in software requirement specifications.
efficiency
functional testing tool
resolution types
test management tool features
39. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
interoperability
incident management tools
integration management tools
40. The smallest software item that can be tested in isolation.
component
ad hoc integration
condition determination coverage
monitor
41. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
data-driven testing
entry criteria
component integration testing
42. Find defects in code while the software application being tested is running.
decision table
dynamic analysis tools
integration management tools
alpha testing
43. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
debugging tools
component integration testing
horizontal traceability
44. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
failure rate
maintainability
informal review
Three main SW development models
45. Develop & proiroitize test cases Create groups of test cases Set up test environment
test implementation tasks
component testing
anomalous events
impact
46. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
driver
functional testing tool
contract acceptance testing
code coverage
47. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
instrumentation
error guessing
LCSAJ
decision testing
48. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
exploratory testing
incremental testing
alpha testing
acceptance testing
49. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
decision table
iterative-incremental development models
informal review
alpha testing
50. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.
component
Impact subheadings
inspection
impact analysis