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. Black-box test design technique - test cases are designed from a decision table.
stub
incident life cycle phases
decision table testing
acceptance testing
2. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities
input specifications
test management tool features
iterative-incremental development models
test planning Tasks
3. Insertion of additional code in the existing program in order to count coverage items.
iterative-incremental development models
informal review
instrumentation
COTS
4. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
waterfall model benefits
cause-effect graphic testing
driver
test analysis & design tasks
5. Integrate different kinds of tools to make test management more efficient and simple.
input specifications
coverage measurement tools
incident life cycle phases
integration management tools
6. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
boundary value analysis
impact analysis
functional testing tool
test levels
7. Used to replace a component that calls another component.
contract acceptance testing
driver
incident management tools
conditions
8. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
configuration management tools
COTS
interoperability
incident report
9. A document that records the description of each event that occurs during the testing process and that requires further investigation
acceptance testing
stub
incident report
functional incremental integration
10. Linear Code Sequence and Jump.
LCSAJ
fault attack
big-bang testing
error
11. Input or combination of inputs required to test software.
incident report
documentation tools
conditions
black-box testing
12. 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
load testing
maintainability
waterfall model benefits
driver
13. Actual inputs required to execute a test case
configuration management tools
input specifications
conditions
actual result
14. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
waterfall model benefits
test analysis & design tasks
control flow structure
backbone integration
15. Increased load (transations) used to test behavior of system under high volume.
business process-based testing
load testing
integration
boundary value analysis
16. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
environmental needs
decision testing
integration testing
operational testing
17. Process used to create a SW product from initial conception to public release
load testing
driver
SW development model
ad hoc integration
18. Software products or applications designed to automate manual testing tasks.
automation tools
LCSAJ testing
driver
acceptance criteria
19. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
debugging tools
maintenance testing
cause-effect graphic testing
20. Specific groups that represent a set of valid or invalid partitions for input conditions.
contract acceptance testing
component testing
equivalence partitions
condition coverage
21. Record details of test cases executed Record order of execution record results
functional requirements
code coverage
waterfall model phases
test log uses
22. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
component testing
experience-based techniques
Three main SW development models
component integration testing
23. Testing performed to determine whether the system meets acceptance criteria
test condition
load testing
acceptance testing
code coverage
24. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
incident management tools
horizontal traceability
exit criteria
decision table testing
25. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
big-bang testing
incident management tools
interoperability testing
test control Tasks
26. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
maintenance testing
functional incremental integration
conformance testing tools
27. Components are combined and tested in the order in which basic functionalities start working
coverage measurement tools
functional testing tool
configuration management tools
functional incremental integration
28. A table showing combinations of inputs and their associated actions.
coverage
fault attack
boundary value analysis
decision table
29. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
incident report identifier
data-driven testing
black-box testing
SW development model
30. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
Incidents
test tool deployment Success Factors
nonfunctional requirements
test analysis & design tasks
31. Combining components or sytems into larger structural units or subsystems.
integration
error guessing
data flow structure
integration testing
32. Special additions or changes to the environment required to run a test case.
stub
test data preparation tools
conformance testing tools
environmental needs
33. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
functional testing
business process-based testing
test control Tasks
34. A review not based on a formal documented procedure
informal review
exit criteria
SW development model
test implementation tasks
35. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
configuration management tools
test condition
agile software development model
36. Severity - Priority
component testing
incident report
Impact subheadings
nonfunctional requirements
37. A set of conditions that a system needs to meet in order to be accepted by end users
exhaustive testing
acceptance criteria
inspection
test implementation tasks
38. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
instrumentation
conformance testing tools
incremental testing
39. Find defects in code while the software application being tested is running.
incident management tools
dynamic analysis tools
waterfall model benefits
test data preparation tools
40. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
integration testing
anomalous events
impact
41. Conditions required to begin testing activities.
interoperability
condition determination coverage
entry criteria
functionality
42. One defect prevents the detection of another.
data-driven testing
incremental testing
integration management tools
defect masking
43. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
incident life cycle phases
alpha testing
multiple condition coverage
exploratory testing
44. Black-box testing technique used to create groups of input conditions that create the same kind of output.
code coverage
debugging tools
COTS
equivalence partitioning
45. Requirements that determine the functionality of a software system.
incident report
functional requirements
actual result
test execution tasks
46. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
LCSAJ
action
SW development model
47. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
conditions
condition determination coverage
incident life cycle phases
condition coverage
48. Deviation of a software system from its expected delivery services or results
defect masking
failure
impact
defect
49. Informal testing technique in which test planning and execution run in parallel
test analysis & design tasks
exploratory testing
environmental needs
integration
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).
LCSAJ
coverage measurement tools
configuration management tools
incident report identifier