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. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
equivalence partitions
component integration testing
backbone integration
data-driven testing
2. Black-box test design technique - test cases are designed from a decision table.
acceptance testing
incremental testing
decision table testing
coverage
3. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
control flow structure
IEEE test case specification template
coverage
impact analysis
4. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
code coverage
coverage
keyword-driven testing
exit criteria
5. 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
boundary value analysis
driver
agile software development model
6. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
informal review
maintainability testing
resolution types
monitor
7. Special-purpose software used to simulate a component that calls the component under test
incremental testing
driver
integration
defect masking
8. 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.
Incidents
bottom-up integration
incremental testing
Impact subheadings
9. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
debugging tools
decision table testing
incremental testing
exploratory testing
10. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
test execution tasks
exhaustive testing
decision table testing
acceptance criteria
11. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
equivalence partitioning
integration testing
test control Tasks
load testing
12. Insertion of additional code in the existing program in order to count coverage items.
functionality
instrumentation
component testing
driver
13. Occurrences that happen before and after an unexpected event
boundary value analysis
multiple condition coverage
equivalence partitions
anomalous events
14. The capability of a software product to provide agreed and correct output with the required degree of precision
error
incident report
accuracy
data-driven testing
15. Sequence in which data items are accessed or modified by code.
data flow structure
coverage
LCSAJ testing
test tool deployment Success Factors
16. Behavior or response of a software application that you observe when you execute the action steps in the test case.
coverage measurement tools
functionality
actual result
incident report
17. A component of the incident report that determines the actual effect of the incident on the software and its users.
boundary value analysis
functional testing
input specifications
impact
18. White-box design technique used to design test cases for a software component using LCSAJ.
load testing
LCSAJ testing
big-bang testing
interoperability
19. Requirements that determine the functionality of a software system.
functional requirements
LCSAJ
control flow structure
cyclomatic complexity
20. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
multiple condition coverage
Three main SW development models
informal review
nonfunctional requirements
21. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
LCSAJ
independence of testing
inspection
cyclomatic complexity
22. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
alpha testing
ad hoc integration
integration management tools
test log uses
23. Combining components or sytems into larger structural units or subsystems.
incident description subheadings
incremental testing
integration
documentation tools
24. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
decision testing
test tool deployment Success Factors
bottom-up integration
condition determination coverage
25. Testing software in its operational environment
risk-based testing
incident management tools
operational testing
instrumentation
26. Examine changes made to an operational system cause defects.
cause-effect graphic testing
decision table testing
maintenance testing
Three main SW development models
27. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
cause-effect graphic testing
incident description subheadings
monitor
maintainability testing
28. A review not based on a formal documented procedure
functionality
maintenance testing
action
informal review
29. Components are integrated in the order in which they are developed
functional requirements
ad hoc integration
contract acceptance testing
informal review
30. A document that provides the structure for writing test cases.
IEEE test case specification template
system testing
incident description subheadings
error
31. A unique identifier for each incident report generated during test execution.
business process-based testing
failure
incident report identifier
big-bang testing
32. Black-box testing technique used to create groups of input conditions that create the same kind of output.
incident report
equivalence partitioning
integration management tools
coverage
33. An analysis that determines the portion of code on software executed by a set of test cases
coverage
component
code coverage
IEEE test case specification template
34. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
inspection
configuration management
test tool deployment Success Factors
35. Testing performed to determine whether the system meets acceptance criteria
waterfall model benefits
waterfall model phases
fault attack
acceptance testing
36. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident management tools
waterfall model benefits
incident report
integration management tools
37. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
component
maintainability
entry criteria
business process-based testing
38. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
IEEE test case specification template
COTS
failure
waterfall model phases
39. Tools used to identify and calculate coverage items in program code.
agile software development model
acceptance testing
beta testing
coverage measurement tools
40. Operational testing performed at an _external_ site without involvement of the developing organization.
keyword-driven testing
actual result
code coverage
beta testing
41. A table showing combinations of inputs and their associated actions.
decision table
fault attack
condition coverage
configuration management
42. 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
test planning Tasks
impact analysis
test tool deployment Success Factors
defect
43. Special additions or changes to the environment required to run a test case.
waterfall model phases
decision coverage
incident report identifier
environmental needs
44. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
exploratory testing
component integration testing
defect
integration management tools
45. Sequence in which instructions are executed through a component or system
debugging
control flow structure
maintenance testing
decision coverage
46. Increased load (transations) used to test behavior of system under high volume.
functional requirements
bottom-up integration
test analysis & design tasks
load testing
47. Testing an integrated system to validate it meets requirements
interoperability testing
system testing
defect masking
automation tools
48. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
stub
entry criteria
interoperability
49. 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
test data preparation tools
integration
condition coverage
test implementation tasks
50. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
maintainability
test implementation tasks
incident description subheadings
experience-based techniques