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. Process used to create a SW product from initial conception to public release
agile software development model
SW development model
testing process phases
LCSAJ
2. Occurrences that happen before and after an unexpected event
COTS
functional testing tool
failure rate
anomalous events
3. Based on analysis of functional specifications of a system.
test analysis & design tasks
automation tools
functional testing
alpha testing
4. Incident Report - Identifier - Summary - Incident - Description - Impact
resolution types
IEEE incident report template
system testing
condition coverage
5. One defect prevents the detection of another.
test implementation tasks
defect density
defect masking
ad hoc integration
6. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
multiple condition coverage
acceptance testing
component testing
monitor
7. Develop & proiroitize test cases Create groups of test cases Set up test environment
IEEE incident report template
alpha testing
iterative-incremental development models
test implementation tasks
8. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
decision coverage
incremental testing
interoperability testing
component integration testing
9. 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.
bottom-up integration
defect
conformance testing tools
component
10. Integrate different kinds of tools to make test management more efficient and simple.
functional incremental integration
big-bang testing
action
integration management tools
11. Increased load (transations) used to test behavior of system under high volume.
input specifications
acceptance testing
interoperability
load testing
12. Tools used by developers to identify defects in programs.
debugging tools
exhaustive testing
impact
backbone integration
13. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
load testing
agile software development model
horizontal traceability
contract acceptance testing
14. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
beta testing
equivalence partitioning
impact analysis
Incidents
15. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
multiple condition coverage
test control Tasks
decision testing
COTS
16. An analysis that determines the portion of code on software executed by a set of test cases
condition coverage
code coverage
cause-effect graphic testing
Three main SW development models
17. Find defects in code while the software application being tested is running.
dynamic analysis tools
instrumentation
failure rate
conformance testing tools
18. Used to test the functionality of software as mentioned in software requirement specifications.
test levels
functional testing tool
data flow structure
conditions
19. Testing software components that are separately testable. Also module program and unit testing.
test condition
component testing
SW development model
defect masking
20. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
driver
interoperability testing
maintainability
fault attack
21. Special-purpose software used to simulate a component that calls the component under test
defect density
backbone integration
exit criteria
driver
22. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
IEEE test case specification template
backbone integration
alpha testing
multiple condition coverage
23. Black-box testing technique used to create groups of input conditions that create the same kind of output.
maintenance testing
impact
resolution types
equivalence partitioning
24. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
waterfall model phases
interoperability
failure
component testing
25. Record details of test cases executed Record order of execution record results
exit criteria
test data preparation tools
interoperability
test log uses
26. Response of the application to an input
test analysis & design tasks
data-driven testing
action
impact
27. 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
beta testing
test planning Tasks
agile software development model
28. Sequence in which data items are accessed or modified by code.
data flow structure
test management tool features
incident management tools
decision table testing
29. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
interoperability
functional testing
nonfunctional requirements
30. Components are combined and tested in the order in which basic functionalities start working
functional requirements
functional incremental integration
failure
configuration management tools
31. 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
IEEE test case specification template
incident report identifier
control flow structure
32. Testing performed to determine whether the system meets acceptance criteria
coverage
defect density
fault attack
acceptance testing
33. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
incident management tools
test data preparation tools
inspection
cyclomatic complexity
34. Events that occurred during the testing process our investigation.
conformance testing tools
test analysis & design tasks
Incidents
inspection
35. Software products or applications designed to automate manual testing tasks.
automation tools
testing process phases
functional testing tool
component integration testing
36. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
integration testing
integration management tools
actual result
37. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
big-bang testing
testing process phases
iterative-incremental development models
test tool deployment Success Factors
38. Linear Code Sequence and Jump.
test data preparation tools
LCSAJ
LCSAJ testing
test management tool features
39. 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
IEEE incident report template
black-box testing
risk-based testing
agile software development model
40. 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
contract acceptance testing
impact analysis
test tool deployment Success Factors
risk-based testing
41. Allows storage of test input and expected results in one or more central data sources or databases.
load testing
data-driven testing
code coverage
backbone integration
42. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
incident life cycle phases
backbone integration
acceptance testing
integration
43. Informal testing technique in which test planning and execution run in parallel
data-driven testing
defect density
exploratory testing
configuration management
44. Tools used to identify and calculate coverage items in program code.
Incidents
conformance testing tools
coverage measurement tools
fault attack
45. Conditions required to begin testing activities.
input specifications
integration management tools
test data preparation tools
entry criteria
46. All possible combinations of input values and preconditions are tested.
exhaustive testing
efficiency
exit criteria
test levels
47. Human action that generates an incorrect result.
IEEE incident report template
error
experience-based techniques
dynamic analysis tools
48. A document that records the description of each event that occurs during the testing process and that requires further investigation
error guessing
incident report
Impact subheadings
functional testing tool
49. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
component integration testing
operational testing
test condition
50. The process of finding analyzing and removing causes of failure in a software product.
test log uses
debugging
test levels
action