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. Combining components or sytems into larger structural units or subsystems.
test execution tasks
integration
horizontal traceability
test tool deployment Success Factors
2. Integration approach components or subsystems are combined all at once rather than in stages.
decision coverage
test execution tasks
multiple condition coverage
big-bang testing
3. The capability of a software product to provide agreed and correct output with the required degree of precision
exhaustive testing
cyclomatic complexity
maintainability testing
accuracy
4. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
failure
impact analysis
instrumentation
automation tools
5. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
backbone integration
component integration testing
conformance testing tools
condition coverage
6. Events that occurred during the testing process our investigation.
Incidents
keyword-driven testing
multiple condition coverage
decision coverage
7. Allows storage of test input and expected results in one or more central data sources or databases.
coverage
failure
exit criteria
data-driven testing
8. Actual inputs required to execute a test case
incident description subheadings
decision table
incident report identifier
input specifications
9. A unique identifier for each incident report generated during test execution.
interoperability
test log uses
business process-based testing
incident report identifier
10. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
functional testing
functional incremental integration
interoperability
boundary value analysis
11. Severity - Priority
Impact subheadings
instrumentation
data-driven testing
decision table testing
12. Black-box testing technique used to create groups of input conditions that create the same kind of output.
data flow structure
equivalence partitioning
test log uses
independence of testing
13. All possible combinations of input values and preconditions are tested.
test condition
decision coverage
exhaustive testing
multiple condition coverage
14. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
accuracy
defect masking
IEEE test case specification template
documentation tools
15. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
functionality
test management tool features
risk-based testing
test implementation tasks
16. A table showing combinations of inputs and their associated actions.
failure
test condition
risk-based testing
decision table
17. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
Three main SW development models
cause-effect graphic testing
incident description subheadings
18. Component - Integration - System - Acceptance
risk-based testing
test planning Tasks
component testing
test levels
19. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
test tool deployment Success Factors
LCSAJ
component integration testing
failure
20. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
incident management tools
business process-based testing
coverage
21. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
test control Tasks
cyclomatic complexity
integration management tools
22. Software products or applications designed to automate manual testing tasks.
automation tools
Incidents
test condition
debugging
23. 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 tool deployment Success Factors
test data preparation tools
test levels
environmental needs
24. One defect prevents the detection of another.
defect masking
configuration management
test planning Tasks
incident management tools
25. Deviation of a software system from its expected delivery services or results
system testing
incident report identifier
input specifications
failure
26. Testing software components that are separately testable. Also module program and unit testing.
component testing
control flow structure
efficiency
error
27. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
big-bang testing
exit criteria
waterfall model phases
28. Black-box test design technique - test cases are designed from a decision table.
test implementation tasks
incident report identifier
decision table testing
test data preparation tools
29. Measures amount of testing performed by a collection of test cases
condition determination coverage
maintainability
waterfall model benefits
coverage
30. A document that provides the structure for writing test cases.
inspection
IEEE test case specification template
agile software development model
condition coverage
31. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
efficiency
functional incremental integration
testing process phases
IEEE incident report template
32. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
acceptance criteria
entry criteria
alpha testing
decision table testing
33. Incident Report - Identifier - Summary - Incident - Description - Impact
decision table
IEEE incident report template
waterfall model benefits
equivalence partitions
34. A functional testing approach in which test cases are designed based on business processes.
Three main SW development models
keyword-driven testing
exit criteria
business process-based testing
35. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
incident management tools
experience-based techniques
waterfall model phases
cause-effect graphic testing
36. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
exhaustive testing
test execution tasks
incident management tools
LCSAJ
37. A review not based on a formal documented procedure
functionality
informal review
testing process phases
test planning Tasks
38. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
test log uses
debugging tools
keyword-driven testing
beta testing
39. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables
test execution tasks
waterfall model benefits
failure rate
stub
40. Calculates the number of executed branch outcomes in code.
conformance testing tools
boundary value analysis
decision coverage
interoperability testing
41. Requirements that determine the functionality of a software system.
anomalous events
failure rate
functional requirements
coverage measurement tools
42. Input or combination of inputs required to test software.
test condition
boundary value analysis
integration management tools
conditions
43. 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).
entry criteria
backbone integration
functionality
configuration management tools
44. Tools used to store and manage incidents return phone defects failures or anomalies.
incident report identifier
incident management tools
integration
acceptance testing
45. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
error guessing
code coverage
experience-based techniques
backbone integration
46. Specific groups that represent a set of valid or invalid partitions for input conditions.
dynamic analysis tools
equivalence partitions
environmental needs
debugging
47. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
actual result
horizontal traceability
integration management tools
environmental needs
48. Find defects in code while the software application being tested is running.
dynamic analysis tools
test condition
debugging tools
input specifications
49. Based on analysis of functional specifications of a system.
resolution types
functional testing
cyclomatic complexity
test control Tasks
50. Increased load (transations) used to test behavior of system under high volume.
load testing
error guessing
control flow structure
debugging