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. Behavior or response of a software application that you observe when you execute the action steps in the test case.
impact analysis
functional requirements
beta testing
actual result
2. Operational testing performed at an _external_ site without involvement of the developing organization.
test levels
beta testing
conformance testing tools
incremental testing
3. Testing software in its operational environment
automation tools
Three main SW development models
Incidents
operational testing
4. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
decision coverage
integration
COTS
component testing
5. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
ad hoc integration
defect
black-box testing
6. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
functional incremental integration
IEEE incident report template
black-box testing
configuration management tools
7. 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.
inspection
testing process phases
decision coverage
maintainability
8. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
beta testing
instrumentation
component integration testing
boundary value analysis
9. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
black-box testing
accuracy
nonfunctional requirements
control flow structure
10. Increased load (transations) used to test behavior of system under high volume.
impact analysis
load testing
debugging
maintainability
11. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
driver
defect
fault attack
12. A unique identifier for each incident report generated during test execution.
incident report identifier
instrumentation
debugging
documentation tools
13. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
coverage
defect density
iterative-incremental development models
driver
14. 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
LCSAJ
decision coverage
agile software development model
test management tool features
15. 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
inspection
LCSAJ testing
16. Sequence in which data items are accessed or modified by code.
test implementation tasks
incident management tools
data flow structure
agile software development model
17. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
decision table testing
maintainability
condition determination coverage
18. Actual inputs required to execute a test case
contract acceptance testing
horizontal traceability
LCSAJ testing
input specifications
19. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
dynamic analysis tools
black-box testing
conformance testing tools
fault attack
20. The smallest software item that can be tested in isolation.
component
horizontal traceability
data-driven testing
integration testing
21. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
incident life cycle phases
actual result
defect density
waterfall model phases
22. Integrate different kinds of tools to make test management more efficient and simple.
defect density
integration management tools
decision coverage
action
23. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
iterative-incremental development models
test data preparation tools
failure rate
error guessing
24. Response of the application to an input
error
equivalence partitions
alpha testing
action
25. A component of the incident report that determines the actual effect of the incident on the software and its users.
acceptance criteria
test execution tasks
impact analysis
impact
26. One defect prevents the detection of another.
SW development model
testing process phases
incident description subheadings
defect masking
27. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
interoperability
functional requirements
integration management tools
28. A review not based on a formal documented procedure
error
load testing
decision table testing
informal review
29. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test analysis & design tasks
IEEE test case specification template
test levels
monitor
30. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
exit criteria
inspection
boundary value analysis
impact analysis
31. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
COTS
boundary value analysis
alpha testing
coverage
32. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
horizontal traceability
test execution tasks
equivalence partitioning
33. Combining components or sytems into larger structural units or subsystems.
configuration management tools
system testing
integration
component testing
34. Testing software components that are separately testable. Also module program and unit testing.
configuration management
debugging
component testing
environmental needs
35. Record details of test cases executed Record order of execution record results
test data preparation tools
test log uses
exhaustive testing
code coverage
36. Components are combined and tested in the order in which basic functionalities start working
black-box testing
functional incremental integration
Impact subheadings
configuration management tools
37. Component - Integration - System - Acceptance
test levels
contract acceptance testing
ad hoc integration
stub
38. Incident Report - Identifier - Summary - Incident - Description - Impact
exploratory testing
inspection
IEEE incident report template
exit criteria
39. A technique used to improve testing coverage by deliberately introducing faults in code.
alpha testing
resolution types
fault attack
interoperability testing
40. A document that provides the structure for writing test cases.
IEEE incident report template
data flow structure
configuration management tools
IEEE test case specification template
41. Used to replace a component that calls another component.
incident report identifier
component testing
driver
coverage
42. Tools used to store and manage incidents return phone defects failures or anomalies.
resolution types
functionality
incident management tools
coverage
43. Requirements that determine the functionality of a software system.
decision testing
functional requirements
impact analysis
business process-based testing
44. Examine changes made to an operational system cause defects.
agile software development model
maintenance testing
incident management tools
automation tools
45. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
action
big-bang testing
defect density
incremental testing
46. Process used to create a SW product from initial conception to public release
SW development model
agile software development model
entry criteria
documentation tools
47. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
impact analysis
backbone integration
test control Tasks
integration management tools
48. All possible combinations of input values and preconditions are tested.
component integration testing
exhaustive testing
exploratory testing
LCSAJ testing
49. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
maintainability
resolution types
incident description subheadings
waterfall model benefits
50. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
maintenance testing
maintainability testing
IEEE test case specification template