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. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
action
acceptance criteria
configuration management
test control Tasks
2. An analysis that determines the portion of code on software executed by a set of test cases
Impact subheadings
anomalous events
code coverage
IEEE test case specification template
3. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
monitor
test data preparation tools
cyclomatic complexity
multiple condition coverage
4. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
backbone integration
waterfall model phases
functionality
keyword-driven testing
5. Requirements that determine the functionality of a software system.
interoperability
functional requirements
keyword-driven testing
component testing
6. Informal testing technique in which test planning and execution run in parallel
configuration management
failure rate
exploratory testing
monitor
7. One defect prevents the detection of another.
acceptance testing
Three main SW development models
Incidents
defect masking
8. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
configuration management
LCSAJ testing
equivalence partitioning
9. The smallest software item that can be tested in isolation.
test analysis & design tasks
functionality
impact analysis
component
10. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
test management tool features
LCSAJ testing
experience-based techniques
11. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
decision table
functionality
incident life cycle phases
condition coverage
12. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
incremental testing
interoperability
SW development model
Incidents
13. Integrate different kinds of tools to make test management more efficient and simple.
operational testing
test execution tasks
impact analysis
integration management tools
14. 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
agile software development model
error
big-bang testing
interoperability
15. Component - Integration - System - Acceptance
test levels
actual result
incident report
test analysis & design tasks
16. Occurrences that happen before and after an unexpected event
decision table
anomalous events
SW development model
integration testing
17. Components are combined and tested in the order in which basic functionalities start working
risk-based testing
functional incremental integration
configuration management
business process-based testing
18. A table showing combinations of inputs and their associated actions.
error
coverage measurement tools
LCSAJ testing
decision table
19. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.
bottom-up integration
data flow structure
documentation tools
dynamic analysis tools
20. Linear Code Sequence and Jump.
ad hoc integration
LCSAJ
IEEE test case specification template
impact analysis
21. Combining components or sytems into larger structural units or subsystems.
waterfall model phases
test data preparation tools
integration
incident description subheadings
22. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
actual result
keyword-driven testing
test analysis & design tasks
incident description subheadings
23. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
functionality
interoperability testing
impact
24. Components are integrated in the order in which they are developed
IEEE incident report template
informal review
ad hoc integration
automation tools
25. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
big-bang testing
resolution types
incident management tools
monitor
26. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
black-box testing
COTS
input specifications
test analysis & design tasks
27. Human action that generates an incorrect result.
impact
functional testing tool
acceptance testing
error
28. Special-purpose software used to simulate a component called by the component under test
acceptance criteria
configuration management
inspection
stub
29. Operational testing performed at an _external_ site without involvement of the developing organization.
IEEE test case specification template
keyword-driven testing
COTS
beta testing
30. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
interoperability
decision testing
iterative-incremental development models
test control Tasks
31. Testing an integrated system to validate it meets requirements
system testing
independence of testing
experience-based techniques
contract acceptance testing
32. 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.
interoperability
inspection
waterfall model benefits
test tool deployment Success Factors
33. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
impact analysis
error guessing
control flow structure
exhaustive testing
34. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
functional incremental integration
big-bang testing
monitor
35. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
independence of testing
functional testing
incident description subheadings
decision table
36. All possible combinations of input values and preconditions are tested.
exhaustive testing
conformance testing tools
monitor
component testing
37. Severity - Priority
fault attack
Impact subheadings
big-bang testing
waterfall model phases
38. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
error
experience-based techniques
incident report
error guessing
39. 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
cause-effect graphic testing
LCSAJ testing
functional testing tool
test tool deployment Success Factors
40. Behavior or response of a software application that you observe when you execute the action steps in the test case.
actual result
conditions
informal review
test planning Tasks
41. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
horizontal traceability
boundary value analysis
LCSAJ
42. Testing performed to determine whether the system meets acceptance criteria
interoperability testing
acceptance testing
decision table testing
experience-based techniques
43. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
automation tools
keyword-driven testing
test management tool features
exit criteria
44. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
cause-effect graphic testing
condition determination coverage
big-bang testing
Three main SW development models
45. Based on analysis of functional specifications of a system.
failure
exit criteria
functional testing
iterative-incremental development models
46. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
incident management tools
data-driven testing
inspection
47. Tests interfaces between components and between integrated components and systems.
entry criteria
IEEE test case specification template
test planning Tasks
integration testing
48. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
Impact subheadings
maintenance testing
horizontal traceability
incident report identifier
49. The process of finding analyzing and removing causes of failure in a software product.
boundary value analysis
incident management tools
cyclomatic complexity
debugging
50. Special-purpose software used to simulate a component that calls the component under test
load testing
IEEE incident report template
driver
acceptance criteria