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. One defect prevents the detection of another.
decision testing
LCSAJ
bottom-up integration
defect masking
2. Examine changes made to an operational system cause defects.
COTS
multiple condition coverage
input specifications
maintenance testing
3. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
maintainability
beta testing
integration testing
impact analysis
4. Occurrences that happen before and after an unexpected event
failure rate
SW development model
decision testing
anomalous events
5. Response of the application to an input
debugging tools
defect masking
system testing
action
6. The ratio between the number of defects found and the size of the component/system tested.
defect density
efficiency
interoperability testing
component testing
7. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
coverage
debugging tools
interoperability testing
horizontal traceability
8. Linear Code Sequence and Jump.
test condition
LCSAJ
integration testing
test implementation tasks
9. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
entry criteria
maintainability testing
test data preparation tools
functionality
10. Integration approach components or subsystems are combined all at once rather than in stages.
maintainability
decision table testing
big-bang testing
Impact subheadings
11. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
functional incremental integration
decision table
Incidents
12. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
incident description subheadings
multiple condition coverage
monitor
documentation tools
13. Calculates the number of executed branch outcomes in code.
alpha testing
Incidents
decision coverage
functional incremental integration
14. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
configuration management
nonfunctional requirements
fault attack
condition coverage
15. Measures amount of testing performed by a collection of test cases
coverage
incident description subheadings
LCSAJ testing
failure rate
16. 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.
waterfall model benefits
bottom-up integration
resolution types
system testing
17. 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.
iterative-incremental development models
test execution tasks
inspection
test control Tasks
18. Ability of software to provide appropriate performance relative to amount of resources used.
code coverage
efficiency
debugging tools
test data preparation tools
19. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
decision testing
acceptance criteria
data-driven testing
20. Operational testing performed at an _external_ site without involvement of the developing organization.
fault attack
coverage
beta testing
defect
21. Tools used by developers to identify defects in programs.
nonfunctional requirements
debugging tools
test management tool features
exploratory testing
22. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
conformance testing tools
waterfall model benefits
integration management tools
alpha testing
23. Conditions required to begin testing activities.
test control Tasks
maintenance testing
entry criteria
multiple condition coverage
24. A component of the incident report that determines the actual effect of the incident on the software and its users.
test data preparation tools
impact
error guessing
condition coverage
25. Based on analysis of functional specifications of a system.
component testing
exit criteria
input specifications
functional testing
26. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
decision coverage
waterfall model phases
exploratory testing
experience-based techniques
27. Informal testing technique in which test planning and execution run in parallel
Three main SW development models
fault attack
exploratory testing
incident management tools
28. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
decision testing
testing process phases
IEEE test case specification template
29. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
beta testing
cyclomatic complexity
waterfall model benefits
error guessing
30. Input or combination of inputs required to test software.
SW development model
conditions
experience-based techniques
driver
31. Combining components or sytems into larger structural units or subsystems.
anomalous events
test data preparation tools
driver
integration
32. 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
agile software development model
test execution tasks
IEEE incident report template
configuration management tools
33. Sequence in which instructions are executed through a component or system
control flow structure
input specifications
incident management tools
cyclomatic complexity
34. Specific groups that represent a set of valid or invalid partitions for input conditions.
COTS
equivalence partitions
business process-based testing
integration management tools
35. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
maintainability testing
exhaustive testing
automation tools
36. Waterfall iterative-incremental "V"
system testing
contract acceptance testing
dynamic analysis tools
Three main SW development models
37. White-box design technique used to design test cases for a software component using LCSAJ.
driver
independence of testing
LCSAJ testing
big-bang testing
38. Human action that generates an incorrect result.
input specifications
equivalence partitioning
error
impact
39. 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
input specifications
SW development model
cause-effect graphic testing
40. Sequence in which data items are accessed or modified by code.
data flow structure
impact analysis
input specifications
nonfunctional requirements
41. Special-purpose software used to simulate a component called by the component under test
decision coverage
alpha testing
automation tools
stub
42. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
test condition
horizontal traceability
error
43. Used to replace a component that calls another component.
failure
driver
big-bang testing
bottom-up integration
44. Increased load (transations) used to test behavior of system under high volume.
impact analysis
load testing
big-bang testing
environmental needs
45. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
automation tools
incident report
configuration management
46. Requirements that determine the functionality of a software system.
incident management tools
decision table testing
conditions
functional requirements
47. A review not based on a formal documented procedure
defect density
test management tool features
dynamic analysis tools
informal review
48. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
stub
decision testing
failure
automation tools
49. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
component integration testing
monitor
incident description subheadings
50. An analysis that determines the portion of code on software executed by a set of test cases
component testing
equivalence partitioning
incident management tools
code coverage