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. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
test execution tasks
multiple condition coverage
component integration testing
equivalence partitioning
2. A review not based on a formal documented procedure
test condition
functionality
code coverage
informal review
3. 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
testing process phases
boundary value analysis
test tool deployment Success Factors
stub
4. Specific groups that represent a set of valid or invalid partitions for input conditions.
test execution tasks
boundary value analysis
conformance testing tools
equivalence partitions
5. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
horizontal traceability
decision coverage
action
6. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
test levels
conditions
test execution tasks
IEEE incident report template
7. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
coverage measurement tools
functional testing
test tool deployment Success Factors
8. Increased load (transations) used to test behavior of system under high volume.
big-bang testing
failure
load testing
action
9. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
stub
defect
condition coverage
driver
10. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
cause-effect graphic testing
acceptance testing
test tool deployment Success Factors
11. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
decision testing
component
incident description subheadings
data-driven testing
12. Combining components or sytems into larger structural units or subsystems.
incident management tools
decision table
integration
Incidents
13. Special-purpose software used to simulate a component that calls the component under test
incident life cycle phases
stub
incident report
driver
14. White-box design technique used to design test cases for a software component using LCSAJ.
bottom-up integration
testing process phases
LCSAJ testing
operational testing
15. Requirements that determine the functionality of a software system.
driver
test condition
functional requirements
monitor
16. Allows storage of test input and expected results in one or more central data sources or databases.
test planning Tasks
data-driven testing
equivalence partitions
defect
17. Insertion of additional code in the existing program in order to count coverage items.
black-box testing
code coverage
instrumentation
test control Tasks
18. Tests interfaces between components and between integrated components and systems.
integration testing
test management tool features
functional testing tool
resolution types
19. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
horizontal traceability
multiple condition coverage
configuration management
action
20. Calculates the number of executed branch outcomes in code.
equivalence partitions
impact
load testing
decision coverage
21. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
component integration testing
COTS
incident report identifier
black-box testing
22. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
agile software development model
boundary value analysis
configuration management tools
LCSAJ testing
23. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
acceptance criteria
instrumentation
defect masking
24. Find defects in code while the software application being tested is running.
informal review
equivalence partitions
bottom-up integration
dynamic analysis tools
25. Used to replace a component that calls another component.
functional incremental integration
system testing
decision testing
driver
26. The capability of a software product to provide agreed and correct output with the required degree of precision
conformance testing tools
accuracy
IEEE test case specification template
risk-based testing
27. Tools used by developers to identify defects in programs.
action
debugging tools
functional requirements
alpha testing
28. The ratio between the number of defects found and the size of the component/system tested.
waterfall model benefits
SW development model
defect density
configuration management
29. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functional testing tool
functionality
maintainability
equivalence partitions
30. Deviation of a software system from its expected delivery services or results
debugging tools
Three main SW development models
coverage
failure
31. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
resolution types
input specifications
alpha testing
32. Testing performed to determine whether the system meets acceptance criteria
condition determination coverage
waterfall model phases
condition coverage
acceptance testing
33. Process used to create a SW product from initial conception to public release
data-driven testing
SW development model
bottom-up integration
impact analysis
34. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
error
interoperability testing
documentation tools
environmental needs
35. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
accuracy
integration testing
action
risk-based testing
36. Conditions required to begin testing activities.
entry criteria
impact analysis
test implementation tasks
conditions
37. Components are integrated in the order in which they are developed
ad hoc integration
informal review
incident description subheadings
component testing
38. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
acceptance testing
decision testing
condition coverage
horizontal traceability
39. Response of the application to an input
action
ad hoc integration
incident description subheadings
business process-based testing
40. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
incident life cycle phases
incident report identifier
interoperability
41. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
impact analysis
iterative-incremental development models
waterfall model benefits
42. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
bottom-up integration
data-driven testing
independence of testing
43. Special additions or changes to the environment required to run a test case.
environmental needs
test management tool features
bottom-up integration
load testing
44. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
test tool deployment Success Factors
horizontal traceability
waterfall model phases
action
45. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
condition coverage
driver
cause-effect graphic testing
46. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
control flow structure
entry criteria
incremental testing
condition coverage
47. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
integration testing
impact analysis
incident management tools
resolution types
48. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
test implementation tasks
debugging
documentation tools
cause-effect graphic testing
49. One defect prevents the detection of another.
accuracy
test analysis & design tasks
defect masking
waterfall model benefits
50. Ability of software to provide appropriate performance relative to amount of resources used.
conditions
decision table
efficiency
test log uses