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. All possible combinations of input values and preconditions are tested.
informal review
dynamic analysis tools
exhaustive testing
conformance testing tools
2. Components are combined and tested in the order in which basic functionalities start working
action
inspection
functional incremental integration
decision coverage
3. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
coverage
iterative-incremental development models
action
black-box testing
4. Special-purpose software used to simulate a component that calls the component under test
incremental testing
incident description subheadings
driver
multiple condition coverage
5. Integration approach components or subsystems are combined all at once rather than in stages.
maintainability
IEEE incident report template
big-bang testing
SW development model
6. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
functional incremental integration
functionality
maintenance testing
7. One defect prevents the detection of another.
cause-effect graphic testing
defect masking
boundary value analysis
functional testing
8. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
IEEE incident report template
backbone integration
defect masking
data flow structure
9. 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
configuration management tools
nonfunctional requirements
ad hoc integration
10. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).
error
test log uses
configuration management tools
test implementation tasks
11. White-box design technique used to design test cases for a software component using LCSAJ.
defect
impact analysis
LCSAJ testing
instrumentation
12. An analysis that determines the portion of code on software executed by a set of test cases
control flow structure
decision table
code coverage
test analysis & design tasks
13. An event or item that can be tested using one or more test cases
exit criteria
test condition
test control Tasks
functional testing tool
14. 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 levels
documentation tools
test data preparation tools
black-box testing
15. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
component testing
functionality
testing process phases
actual result
16. Response of the application to an input
test log uses
alpha testing
action
error
17. Black-box test design technique - test cases are designed from a decision table.
error
decision table testing
impact analysis
component integration testing
18. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
incremental testing
IEEE test case specification template
maintainability
impact analysis
19. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
incident management tools
waterfall model phases
debugging tools
IEEE incident report template
20. Based on analysis of functional specifications of a system.
independence of testing
functional testing
coverage measurement tools
defect
21. 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.
inspection
test planning Tasks
exit criteria
decision table
22. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
defect
condition determination coverage
incident report
control flow structure
23. Actual inputs required to execute a test case
error guessing
input specifications
decision coverage
bottom-up integration
24. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
test data preparation tools
iterative-incremental development models
input specifications
functionality
25. A unique identifier for each incident report generated during test execution.
incident report identifier
error guessing
component testing
driver
26. A component of the incident report that determines the actual effect of the incident on the software and its users.
operational testing
condition determination coverage
backbone integration
impact
27. The ratio between the number of defects found and the size of the component/system tested.
test control Tasks
component integration testing
defect density
IEEE test case specification template
28. The process of finding analyzing and removing causes of failure in a software product.
debugging
dynamic analysis tools
maintainability testing
actual result
29. Severity - Priority
driver
monitor
driver
Impact subheadings
30. Find defects in code while the software application being tested is running.
dynamic analysis tools
test tool deployment Success Factors
test data preparation tools
cause-effect graphic testing
31. Special-purpose software used to simulate a component called by the component under test
stub
equivalence partitions
entry criteria
maintainability
32. Measures amount of testing performed by a collection of test cases
coverage
interoperability
inspection
SW development model
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.
actual result
exit criteria
cyclomatic complexity
test planning Tasks
34. Used to test the functionality of software as mentioned in software requirement specifications.
actual result
efficiency
test condition
functional testing tool
35. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
horizontal traceability
error guessing
integration management tools
36. Software products or applications designed to automate manual testing tasks.
acceptance criteria
waterfall model phases
horizontal traceability
automation tools
37. Testing software in its operational environment
failure
operational testing
component testing
system testing
38. A document that provides the structure for writing test cases.
IEEE test case specification template
action
Impact subheadings
component
39. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
test data preparation tools
driver
nonfunctional requirements
informal review
40. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
incident report
environmental needs
conformance testing tools
functional requirements
41. Allows storage of test input and expected results in one or more central data sources or databases.
defect
cyclomatic complexity
dynamic analysis tools
data-driven testing
42. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
IEEE test case specification template
debugging tools
exit criteria
LCSAJ testing
43. Tests interfaces between components and between integrated components and systems.
decision table testing
fault attack
black-box testing
integration testing
44. 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 tool deployment Success Factors
horizontal traceability
error
action
45. Examine changes made to an operational system cause defects.
multiple condition coverage
waterfall model phases
maintenance testing
business process-based testing
46. Tools used to identify and calculate coverage items in program code.
data flow structure
coverage
contract acceptance testing
coverage measurement tools
47. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
exploratory testing
actual result
test analysis & design tasks
fault attack
48. Specific groups that represent a set of valid or invalid partitions for input conditions.
defect density
LCSAJ testing
IEEE test case specification template
equivalence partitions
49. Process used to create a SW product from initial conception to public release
resolution types
data flow structure
SW development model
action
50. 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
failure
environmental needs
component testing