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. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
cause-effect graphic testing
load testing
risk-based testing
control flow structure
2. Severity - Priority
coverage
black-box testing
Impact subheadings
driver
3. Testing an integrated system to validate it meets requirements
dynamic analysis tools
test data preparation tools
contract acceptance testing
system testing
4. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
interoperability
bottom-up integration
test execution tasks
exploratory testing
5. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
waterfall model benefits
stub
defect masking
condition determination coverage
6. 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).
test analysis & design tasks
data flow structure
configuration management tools
beta testing
7. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
LCSAJ testing
coverage measurement tools
black-box testing
COTS
8. 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
impact analysis
acceptance criteria
waterfall model benefits
business process-based testing
9. An event or item that can be tested using one or more test cases
test condition
inspection
boundary value analysis
maintainability testing
10. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
boundary value analysis
accuracy
maintainability
entry criteria
11. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
LCSAJ testing
cause-effect graphic testing
maintainability
12. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
contract acceptance testing
SW development model
exit criteria
integration
13. Tests interfaces between components and between integrated components and systems.
horizontal traceability
inspection
conditions
integration testing
14. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
condition coverage
failure
system testing
decision testing
15. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
test control Tasks
acceptance testing
backbone integration
incident life cycle phases
16. Based on analysis of functional specifications of a system.
functional testing
data flow structure
functional testing tool
accuracy
17. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
decision testing
decision table testing
incident report
incremental testing
18. A functional testing approach in which test cases are designed based on business processes.
instrumentation
condition determination coverage
LCSAJ
business process-based testing
19. Actual inputs required to execute a test case
defect
input specifications
keyword-driven testing
test control Tasks
20. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test management tool features
informal review
configuration management
test control Tasks
21. Examine changes made to an operational system cause defects.
maintenance testing
acceptance testing
beta testing
decision coverage
22. Sequence in which data items are accessed or modified by code.
data flow structure
functional requirements
component integration testing
functional testing
23. A document that provides the structure for writing test cases.
exhaustive testing
IEEE test case specification template
coverage measurement tools
defect masking
24. Testing software components that are separately testable. Also module program and unit testing.
LCSAJ
component testing
Impact subheadings
equivalence partitions
25. Tools used by developers to identify defects in programs.
test control Tasks
failure
contract acceptance testing
debugging tools
26. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
informal review
failure rate
component
error guessing
27. The smallest software item that can be tested in isolation.
test execution tasks
component
acceptance testing
LCSAJ testing
28. Sequence in which instructions are executed through a component or system
ad hoc integration
integration testing
control flow structure
accuracy
29. The ratio between the number of defects found and the size of the component/system tested.
interoperability
defect density
condition determination coverage
control flow structure
30. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
Impact subheadings
driver
configuration management
31. Components are combined and tested in the order in which basic functionalities start working
integration management tools
test management tool features
error guessing
functional incremental integration
32. All possible combinations of input values and preconditions are tested.
testing process phases
alpha testing
exhaustive testing
maintainability
33. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
integration
defect
operational testing
functionality
34. The capability of a software product to provide agreed and correct output with the required degree of precision
failure rate
coverage measurement tools
experience-based techniques
accuracy
35. Testing software in its operational environment
automation tools
test control Tasks
operational testing
debugging tools
36. Behavior or response of a software application that you observe when you execute the action steps in the test case.
actual result
acceptance testing
failure rate
risk-based testing
37. 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.
multiple condition coverage
incident report identifier
inspection
integration management tools
38. Increased load (transations) used to test behavior of system under high volume.
impact
environmental needs
horizontal traceability
load testing
39. A component of the incident report that determines the actual effect of the incident on the software and its users.
test log uses
impact
SW development model
acceptance testing
40. The process of finding analyzing and removing causes of failure in a software product.
test data preparation tools
debugging
integration management tools
component
41. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
exit criteria
impact
bottom-up integration
alpha testing
42. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
stub
documentation tools
resolution types
incident life cycle phases
43. Components are integrated in the order in which they are developed
integration management tools
ad hoc integration
Incidents
configuration management
44. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
efficiency
defect masking
acceptance criteria
experience-based techniques
45. A document that records the description of each event that occurs during the testing process and that requires further investigation
driver
failure rate
incident report
incident management tools
46. Combining components or sytems into larger structural units or subsystems.
condition coverage
integration
test levels
LCSAJ
47. Black-box testing technique used to create groups of input conditions that create the same kind of output.
integration testing
debugging tools
functional requirements
equivalence partitioning
48. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
action
test levels
contract acceptance testing
cause-effect graphic testing
49. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
fault attack
Incidents
testing process phases
50. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
defect density
decision coverage
agile software development model