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. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
resolution types
failure
documentation tools
2. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
alpha testing
error
maintainability
monitor
3. A component of the incident report that determines the actual effect of the incident on the software and its users.
contract acceptance testing
cause-effect graphic testing
Impact subheadings
impact
4. Measures amount of testing performed by a collection of test cases
coverage
incident description subheadings
conditions
test analysis & design tasks
5. 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
functional incremental integration
boundary value analysis
driver
6. Response of the application to an input
incident report identifier
test execution tasks
condition determination coverage
action
7. A functional testing approach in which test cases are designed based on business processes.
test levels
business process-based testing
decision testing
test implementation tasks
8. Requirements that determine the functionality of a software system.
environmental needs
functional requirements
fault attack
dynamic analysis tools
9. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
test analysis & design tasks
impact
exit criteria
multiple condition coverage
10. The smallest software item that can be tested in isolation.
component
integration testing
functional testing tool
COTS
11. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
LCSAJ
integration testing
coverage measurement tools
test execution tasks
12. Integrate different kinds of tools to make test management more efficient and simple.
risk-based testing
integration management tools
decision table testing
acceptance criteria
13. Component - Integration - System - Acceptance
exhaustive testing
contract acceptance testing
incident report
test levels
14. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
risk-based testing
condition determination coverage
failure rate
test implementation tasks
15. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
backbone integration
coverage
interoperability testing
stub
16. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
documentation tools
Incidents
conformance testing tools
error guessing
17. Conditions required to begin testing activities.
entry criteria
condition coverage
contract acceptance testing
code coverage
18. Testing software components that are separately testable. Also module program and unit testing.
accuracy
functional testing
component testing
conformance testing tools
19. A document that records the description of each event that occurs during the testing process and that requires further investigation
driver
risk-based testing
functional incremental integration
incident report
20. A table showing combinations of inputs and their associated actions.
test control Tasks
exploratory testing
acceptance criteria
decision table
21. Input or combination of inputs required to test software.
conditions
debugging tools
backbone integration
nonfunctional requirements
22. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
IEEE test case specification template
control flow structure
black-box testing
alpha testing
23. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
contract acceptance testing
acceptance criteria
impact analysis
alpha testing
24. Actual inputs required to execute a test case
maintainability
functional requirements
driver
input specifications
25. Severity - Priority
Impact subheadings
business process-based testing
exit criteria
component testing
26. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
data-driven testing
keyword-driven testing
cause-effect graphic testing
business process-based testing
27. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
keyword-driven testing
impact
failure rate
28. Sequence in which instructions are executed through a component or system
decision table testing
Three main SW development models
control flow structure
impact analysis
29. 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.
input specifications
configuration management
operational testing
inspection
30. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
maintainability
backbone integration
failure rate
decision coverage
31. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
exploratory testing
conformance testing tools
incident life cycle phases
component testing
32. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
keyword-driven testing
resolution types
exhaustive testing
33. Occurrences that happen before and after an unexpected event
Incidents
functional testing
anomalous events
integration testing
34. The ratio between the number of defects found and the size of the component/system tested.
defect
impact
defect density
component testing
35. Special-purpose software used to simulate a component called by the component under test
stub
big-bang testing
equivalence partitions
integration testing
36. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
integration
functional incremental integration
dynamic analysis tools
37. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
cyclomatic complexity
dynamic analysis tools
test execution tasks
38. 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
Impact subheadings
maintenance testing
functional incremental integration
39. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
Incidents
Three main SW development models
configuration management tools
cyclomatic complexity
40. Behavior or response of a software application that you observe when you execute the action steps in the test case.
acceptance testing
actual result
bottom-up integration
test levels
41. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
acceptance testing
experience-based techniques
informal review
integration testing
42. Specific groups that represent a set of valid or invalid partitions for input conditions.
integration management tools
equivalence partitions
functional testing
failure rate
43. A set of conditions that a system needs to meet in order to be accepted by end users
component
acceptance criteria
equivalence partitioning
acceptance testing
44. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
data flow structure
component
decision coverage
45. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
impact analysis
cyclomatic complexity
iterative-incremental development models
test management tool features
46. A unique identifier for each incident report generated during test execution.
decision coverage
condition coverage
incident report identifier
bottom-up integration
47. Used to test the functionality of software as mentioned in software requirement specifications.
test control Tasks
documentation tools
functional testing tool
agile software development model
48. Increased load (transations) used to test behavior of system under high volume.
interoperability testing
condition coverage
SW development model
load testing
49. Tests interfaces between components and between integrated components and systems.
resolution types
integration testing
functional testing tool
coverage
50. 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).
efficiency
data flow structure
configuration management tools
documentation tools