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. Deviation of a software system from its expected delivery services or results
failure
business process-based testing
functional incremental integration
fault attack
2. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
debugging
impact
decision testing
3. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
actual result
black-box testing
driver
condition coverage
4. 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.
acceptance testing
LCSAJ
bottom-up integration
fault attack
5. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
acceptance criteria
exploratory testing
testing process phases
COTS
6. Response of the application to an input
action
boundary value analysis
experience-based techniques
failure rate
7. Tools used by developers to identify defects in programs.
debugging tools
resolution types
functionality
IEEE incident report template
8. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
beta testing
multiple condition coverage
monitor
incident life cycle phases
9. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
integration
stub
horizontal traceability
10. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
inspection
LCSAJ
COTS
monitor
11. Input or combination of inputs required to test software.
fault attack
big-bang testing
conditions
COTS
12. 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
data flow structure
risk-based testing
efficiency
agile software development model
13. Process used to create a SW product from initial conception to public release
exhaustive testing
incident life cycle phases
inspection
SW development model
14. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
debugging
input specifications
data-driven testing
test control Tasks
15. 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
failure rate
cause-effect graphic testing
test data preparation tools
component
16. Conditions required to begin testing activities.
entry criteria
control flow structure
impact analysis
condition coverage
17. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
load testing
failure
exit criteria
interoperability
18. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
maintainability
cyclomatic complexity
documentation tools
anomalous events
19. A technique used to improve testing coverage by deliberately introducing faults in code.
instrumentation
component testing
configuration management
fault attack
20. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
anomalous events
IEEE incident report template
functionality
incident report
21. Specific groups that represent a set of valid or invalid partitions for input conditions.
defect masking
equivalence partitions
data-driven testing
driver
22. Testing software in its operational environment
error guessing
alpha testing
IEEE test case specification template
operational testing
23. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
configuration management tools
resolution types
Three main SW development models
conditions
24. All possible combinations of input values and preconditions are tested.
component testing
exhaustive testing
maintenance testing
functional incremental integration
25. A component of the incident report that determines the actual effect of the incident on the software and its users.
LCSAJ testing
impact
testing process phases
maintainability testing
26. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
inspection
horizontal traceability
component testing
configuration management tools
27. Special additions or changes to the environment required to run a test case.
environmental needs
automation tools
dynamic analysis tools
efficiency
28. Component - Integration - System - Acceptance
data-driven testing
load testing
test levels
agile software development model
29. Informal testing technique in which test planning and execution run in parallel
acceptance criteria
automation tools
exploratory testing
decision testing
30. Increased load (transations) used to test behavior of system under high volume.
configuration management
load testing
interoperability
Impact subheadings
31. Actual inputs required to execute a test case
input specifications
keyword-driven testing
acceptance criteria
COTS
32. An event or item that can be tested using one or more test cases
failure rate
test condition
condition coverage
failure
33. An analysis that determines the portion of code on software executed by a set of test cases
entry criteria
code coverage
Three main SW development models
dynamic analysis tools
34. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
acceptance testing
component testing
test data preparation tools
monitor
35. Requirements that determine the functionality of a software system.
backbone integration
big-bang testing
functional requirements
interoperability testing
36. Black-box test design technique - test cases are designed from a decision table.
test analysis & design tasks
decision table testing
decision table
defect
37. Testing performed to determine whether the system meets acceptance criteria
big-bang testing
test data preparation tools
dynamic analysis tools
acceptance testing
38. A functional testing approach in which test cases are designed based on business processes.
coverage measurement tools
business process-based testing
incident report identifier
incremental testing
39. Software products or applications designed to automate manual testing tasks.
Impact subheadings
automation tools
beta testing
backbone integration
40. Measures amount of testing performed by a collection of test cases
coverage
documentation tools
exit criteria
functional testing
41. Used to test the functionality of software as mentioned in software requirement specifications.
waterfall model phases
IEEE incident report template
integration testing
functional testing tool
42. Components are integrated in the order in which they are developed
ad hoc integration
backbone integration
maintainability testing
informal review
43. The process of finding analyzing and removing causes of failure in a software product.
equivalence partitions
data-driven testing
debugging
Three main SW development models
44. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
integration management tools
defect
LCSAJ
iterative-incremental development models
45. Integration approach components or subsystems are combined all at once rather than in stages.
maintainability
big-bang testing
component testing
cause-effect graphic testing
46. Human action that generates an incorrect result.
error
exploratory testing
functional testing tool
entry criteria
47. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
test log uses
test planning Tasks
maintainability
functional requirements
48. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
functional requirements
conditions
exit criteria
incremental testing
49. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test analysis & design tasks
code coverage
component integration testing
COTS
50. Sequence in which data items are accessed or modified by code.
data flow structure
incident management tools
debugging
nonfunctional requirements