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. 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
independence of testing
anomalous events
test management tool features
2. Develop & proiroitize test cases Create groups of test cases Set up test environment
fault attack
control flow structure
test levels
test implementation tasks
3. Testing software components that are separately testable. Also module program and unit testing.
defect masking
component testing
failure
Three main SW development models
4. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
Three main SW development models
defect masking
COTS
5. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
functional testing
code coverage
decision coverage
6. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
test levels
LCSAJ testing
waterfall model benefits
7. Integration approach components or subsystems are combined all at once rather than in stages.
incident report identifier
equivalence partitioning
big-bang testing
interoperability testing
8. Waterfall iterative-incremental "V"
contract acceptance testing
testing process phases
Three main SW development models
alpha testing
9. Component - Integration - System - Acceptance
test levels
integration testing
debugging tools
contract acceptance testing
10. The capability of a software product to provide agreed and correct output with the required degree of precision
error
resolution types
boundary value analysis
accuracy
11. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test data preparation tools
equivalence partitions
test analysis & design tasks
debugging
12. Based on analysis of functional specifications of a system.
conformance testing tools
cyclomatic complexity
functional testing tool
functional testing
13. 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
agile software development model
exploratory testing
driver
14. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
informal review
control flow structure
test control Tasks
component
15. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
configuration management
inspection
cyclomatic complexity
decision table testing
16. Operational testing performed at an _external_ site without involvement of the developing organization.
component testing
informal review
business process-based testing
beta testing
17. A task of maintaining and controlling changes to all entities of a system.
decision table testing
acceptance criteria
action
configuration management
18. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
IEEE incident report template
conditions
condition coverage
action
19. One defect prevents the detection of another.
environmental needs
functional testing
defect masking
decision table
20. Allows storage of test input and expected results in one or more central data sources or databases.
functional incremental integration
error
data flow structure
data-driven testing
21. 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
waterfall model benefits
keyword-driven testing
efficiency
actual result
22. Testing an integrated system to validate it meets requirements
interoperability testing
resolution types
system testing
testing process phases
23. Record details of test cases executed Record order of execution record results
functional requirements
test log uses
keyword-driven testing
multiple condition coverage
24. Used to test the functionality of software as mentioned in software requirement specifications.
accuracy
functional testing
operational testing
functional testing tool
25. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
test condition
incident management tools
bottom-up integration
exit criteria
26. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
test planning Tasks
maintainability
cyclomatic complexity
27. 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
horizontal traceability
testing process phases
failure rate
28. Combining components or sytems into larger structural units or subsystems.
black-box testing
automation tools
integration
configuration management
29. Tools used to identify and calculate coverage items in program code.
driver
coverage
configuration management tools
coverage measurement tools
30. Testing performed to determine whether the system meets acceptance criteria
functionality
component integration testing
entry criteria
acceptance testing
31. A component of the incident report that determines the actual effect of the incident on the software and its users.
equivalence partitions
impact
test analysis & design tasks
decision testing
32. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
test levels
condition determination coverage
LCSAJ
ad hoc integration
33. An event or item that can be tested using one or more test cases
test condition
incident report
coverage measurement tools
functional requirements
34. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
input specifications
documentation tools
conditions
accuracy
35. 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
acceptance testing
test data preparation tools
monitor
decision testing
36. 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
ad hoc integration
IEEE incident report template
interoperability testing
agile software development model
37. Deviation of a software system from its expected delivery services or results
test levels
functionality
contract acceptance testing
failure
38. Behavior or response of a software application that you observe when you execute the action steps in the test case.
component testing
acceptance criteria
actual result
alpha testing
39. A set of conditions that a system needs to meet in order to be accepted by end users
testing process phases
test control Tasks
acceptance criteria
conditions
40. Measures amount of testing performed by a collection of test cases
condition coverage
alpha testing
coverage
boundary value analysis
41. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
maintenance testing
test execution tasks
test log uses
42. Events that occurred during the testing process our investigation.
keyword-driven testing
exhaustive testing
decision table
Incidents
43. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
driver
input specifications
boundary value analysis
decision table testing
44. Informal testing technique in which test planning and execution run in parallel
test implementation tasks
cyclomatic complexity
integration
exploratory testing
45. Severity - Priority
code coverage
Impact subheadings
test log uses
test management tool features
46. Tools used by developers to identify defects in programs.
condition determination coverage
debugging tools
operational testing
defect
47. The process of finding analyzing and removing causes of failure in a software product.
debugging
input specifications
SW development model
test management tool features
48. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
waterfall model benefits
decision table testing
agile software development model
49. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
conformance testing tools
interoperability
operational testing
failure rate
50. All possible combinations of input values and preconditions are tested.
code coverage
exhaustive testing
defect density
exploratory testing