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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
test condition
boundary value analysis
input specifications
test analysis & design tasks
2. Integration approach components or subsystems are combined all at once rather than in stages.
business process-based testing
anomalous events
big-bang testing
acceptance criteria
3. Software products or applications designed to automate manual testing tasks.
automation tools
beta testing
maintenance testing
dynamic analysis tools
4. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
Incidents
conformance testing tools
component integration testing
equivalence partitioning
5. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
anomalous events
cyclomatic complexity
resolution types
6. Examine changes made to an operational system cause defects.
conformance testing tools
maintenance testing
exploratory testing
error guessing
7. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
cyclomatic complexity
conformance testing tools
documentation tools
alpha testing
8. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
automation tools
conformance testing tools
error guessing
condition determination coverage
9. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
decision table
incremental testing
horizontal traceability
driver
10. Actual inputs required to execute a test case
code coverage
cause-effect graphic testing
control flow structure
input specifications
11. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
debugging
contract acceptance testing
test planning Tasks
monitor
12. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
business process-based testing
condition coverage
risk-based testing
incident description subheadings
13. Special-purpose software used to simulate a component that calls the component under test
acceptance testing
iterative-incremental development models
driver
integration testing
14. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
code coverage
debugging
incident report identifier
alpha testing
15. 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
test execution tasks
dynamic analysis tools
equivalence partitioning
16. Special-purpose software used to simulate a component called by the component under test
environmental needs
equivalence partitioning
exhaustive testing
stub
17. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
Three main SW development models
exploratory testing
coverage
test analysis & design tasks
18. Tests interfaces between components and between integrated components and systems.
acceptance criteria
acceptance testing
horizontal traceability
integration testing
19. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
incident description subheadings
SW development model
action
20. Insertion of additional code in the existing program in order to count coverage items.
COTS
test analysis & design tasks
component
instrumentation
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
decision table testing
experience-based techniques
configuration management
22. Separation of testing responsibilities which encourages the accomplishment of objective testing
fault attack
Three main SW development models
independence of testing
incident description subheadings
23. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
control flow structure
incremental testing
actual result
functional incremental integration
24. Increased load (transations) used to test behavior of system under high volume.
load testing
efficiency
incident report identifier
defect density
25. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
impact analysis
functional requirements
alpha testing
26. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
debugging
incident management tools
waterfall model phases
horizontal traceability
27. A document that provides the structure for writing test cases.
defect density
incremental testing
IEEE test case specification template
iterative-incremental development models
28. Black-box testing technique used to create groups of input conditions that create the same kind of output.
error guessing
equivalence partitioning
LCSAJ testing
component testing
29. Process used to create a SW product from initial conception to public release
SW development model
business process-based testing
resolution types
multiple condition coverage
30. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
cyclomatic complexity
interoperability testing
impact
incident life cycle phases
31. Occurrences that happen before and after an unexpected event
functionality
maintainability testing
operational testing
anomalous events
32. A unique identifier for each incident report generated during test execution.
exit criteria
incident report identifier
functional incremental integration
driver
33. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
inspection
equivalence partitions
incident report identifier
34. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
actual result
test analysis & design tasks
big-bang testing
35. 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
system testing
waterfall model phases
anomalous events
36. Conditions required to begin testing activities.
test control Tasks
entry criteria
code coverage
decision coverage
37. Incident Report - Identifier - Summary - Incident - Description - Impact
acceptance criteria
IEEE incident report template
monitor
multiple condition coverage
38. A review not based on a formal documented procedure
risk-based testing
data flow structure
informal review
debugging tools
39. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
documentation tools
keyword-driven testing
multiple condition coverage
action
40. Informal testing technique in which test planning and execution run in parallel
documentation tools
exploratory testing
maintainability
cause-effect graphic testing
41. Combining components or sytems into larger structural units or subsystems.
documentation tools
integration testing
integration
automation tools
42. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
independence of testing
test management tool features
informal review
43. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
functional incremental integration
coverage
actual result
44. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
decision table
cause-effect graphic testing
test analysis & design tasks
actual result
45. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
alpha testing
functional incremental integration
decision table
46. Linear Code Sequence and Jump.
SW development model
LCSAJ
cyclomatic complexity
test management tool features
47. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
fault attack
functionality
efficiency
iterative-incremental development models
48. A task of maintaining and controlling changes to all entities of a system.
component testing
test planning Tasks
exhaustive testing
configuration management
49. Develop & proiroitize test cases Create groups of test cases Set up test environment
decision coverage
resolution types
functional incremental integration
test implementation tasks
50. The process of finding analyzing and removing causes of failure in a software product.
debugging
incident management tools
anomalous events
error guessing