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. Find defects in code while the software application being tested is running.
dynamic analysis tools
equivalence partitioning
Incidents
coverage measurement tools
2. 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
inspection
test analysis & design tasks
IEEE incident report template
3. One defect prevents the detection of another.
defect masking
interoperability testing
Three main SW development models
accuracy
4. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
functional incremental integration
documentation tools
interoperability
independence of testing
5. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities
test planning Tasks
debugging tools
component
dynamic analysis tools
6. Used to replace a component that calls another component.
control flow structure
input specifications
COTS
driver
7. Informal testing technique in which test planning and execution run in parallel
exploratory testing
conditions
Three main SW development models
debugging
8. A document that records the description of each event that occurs during the testing process and that requires further investigation
impact analysis
incident report
boundary value analysis
cyclomatic complexity
9. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
integration testing
agile software development model
coverage
10. Conditions required to begin testing activities.
horizontal traceability
COTS
decision testing
entry criteria
11. Special additions or changes to the environment required to run a test case.
environmental needs
configuration management
automation tools
functional testing tool
12. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
dynamic analysis tools
entry criteria
business process-based testing
incident description subheadings
13. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
incident management tools
component integration testing
impact analysis
load testing
14. Increased load (transations) used to test behavior of system under high volume.
load testing
defect masking
error
equivalence partitioning
15. Allows storage of test input and expected results in one or more central data sources or databases.
functional testing
data-driven testing
operational testing
conformance testing tools
16. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
maintainability testing
test management tool features
system testing
17. Tools used by developers to identify defects in programs.
debugging tools
business process-based testing
incident management tools
COTS
18. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
equivalence partitioning
test log uses
data flow structure
19. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
nonfunctional requirements
informal review
defect
20. Black-box testing technique used to create groups of input conditions that create the same kind of output.
accuracy
stub
equivalence partitioning
defect masking
21. Based on analysis of functional specifications of a system.
test condition
equivalence partitioning
functional testing
Incidents
22. 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
horizontal traceability
decision coverage
failure rate
23. Software products or applications designed to automate manual testing tasks.
accuracy
automation tools
bottom-up integration
SW development model
24. Record details of test cases executed Record order of execution record results
integration testing
test log uses
configuration management tools
beta testing
25. Special-purpose software used to simulate a component that calls the component under test
resolution types
driver
cause-effect graphic testing
test analysis & design tasks
26. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test management tool features
test control Tasks
environmental needs
conformance testing tools
27. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
impact
maintainability
horizontal traceability
accuracy
28. Component - Integration - System - Acceptance
waterfall model phases
documentation tools
test levels
driver
29. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
incident report identifier
automation tools
incident life cycle phases
30. Black-box test design technique - test cases are designed from a decision table.
entry criteria
stub
dynamic analysis tools
decision table testing
31. The capability of a software product to provide agreed and correct output with the required degree of precision
inspection
equivalence partitions
accuracy
error guessing
32. Response of the application to an input
data flow structure
big-bang testing
action
defect
33. A technique used to improve testing coverage by deliberately introducing faults in code.
exploratory testing
alpha testing
informal review
fault attack
34. Integration approach components or subsystems are combined all at once rather than in stages.
incident report identifier
SW development model
big-bang testing
COTS
35. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
incremental testing
waterfall model phases
multiple condition coverage
incident description subheadings
36. A task of maintaining and controlling changes to all entities of a system.
instrumentation
IEEE incident report template
incident report identifier
configuration management
37. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
system testing
configuration management
functionality
test management tool features
38. Components are integrated in the order in which they are developed
conformance testing tools
ad hoc integration
decision table testing
beta testing
39. A table showing combinations of inputs and their associated actions.
exploratory testing
decision table
LCSAJ
inspection
40. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
integration testing
incremental testing
equivalence partitions
Incidents
41. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
acceptance criteria
cause-effect graphic testing
decision table
test management tool features
42. A functional testing approach in which test cases are designed based on business processes.
test control Tasks
exploratory testing
coverage measurement tools
business process-based testing
43. Deviation of a software system from its expected delivery services or results
stub
resolution types
failure
informal review
44. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
functional testing tool
documentation tools
decision coverage
bottom-up integration
45. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
failure rate
resolution types
test control Tasks
46. Testing software in its operational environment
business process-based testing
operational testing
data flow structure
multiple condition coverage
47. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
debugging tools
fault attack
nonfunctional requirements
functionality
48. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
acceptance testing
exploratory testing
incident report
alpha testing
49. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
maintenance testing
equivalence partitioning
error guessing
defect density
50. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
test management tool features
backbone integration
entry criteria