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. Special additions or changes to the environment required to run a test case.
environmental needs
incident life cycle phases
test planning Tasks
defect density
2. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
component integration testing
conformance testing tools
testing process phases
LCSAJ
3. Waterfall iterative-incremental "V"
Three main SW development models
bottom-up integration
functionality
equivalence partitions
4. An event or item that can be tested using one or more test cases
functional testing tool
test condition
independence of testing
condition coverage
5. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
LCSAJ
input specifications
failure
incident description subheadings
6. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
integration testing
functional testing tool
instrumentation
functionality
7. Software products or applications designed to automate manual testing tasks.
integration
agile software development model
automation tools
defect masking
8. 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
error guessing
acceptance criteria
test planning Tasks
functionality
9. Testing an integrated system to validate it meets requirements
incident life cycle phases
test management tool features
system testing
multiple condition coverage
10. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
business process-based testing
backbone integration
interoperability
test log uses
11. The capability of a software product to provide agreed and correct output with the required degree of precision
Impact subheadings
accuracy
iterative-incremental development models
operational testing
12. One defect prevents the detection of another.
test condition
defect masking
decision testing
failure rate
13. 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 control Tasks
action
cause-effect graphic testing
data flow structure
14. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
conditions
component
test log uses
boundary value analysis
15. Special-purpose software used to simulate a component called by the component under test
LCSAJ testing
stub
documentation tools
test control Tasks
16. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
black-box testing
code coverage
impact
condition coverage
17. Based on analysis of functional specifications of a system.
impact analysis
error
Three main SW development models
functional testing
18. A functional testing approach in which test cases are designed based on business processes.
debugging
business process-based testing
iterative-incremental development models
big-bang testing
19. Deviation of a software system from its expected delivery services or results
failure
functional requirements
Three main SW development models
failure rate
20. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
condition coverage
anomalous events
maintainability testing
alpha testing
21. 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.
test execution tasks
inspection
condition determination coverage
nonfunctional requirements
22. Severity - Priority
test data preparation tools
cyclomatic complexity
Impact subheadings
monitor
23. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
fault attack
test implementation tasks
integration testing
24. Specific groups that represent a set of valid or invalid partitions for input conditions.
test analysis & design tasks
equivalence partitions
beta testing
incident report
25. Used to test the functionality of software as mentioned in software requirement specifications.
test tool deployment Success Factors
functional testing tool
resolution types
agile software development model
26. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
beta testing
data-driven testing
error
component integration testing
27. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
data flow structure
incremental testing
risk-based testing
28. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
cause-effect graphic testing
informal review
exit criteria
iterative-incremental development models
29. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
incident report
condition coverage
ad hoc integration
cyclomatic complexity
30. Develop & proiroitize test cases Create groups of test cases Set up test environment
monitor
test implementation tasks
error
waterfall model phases
31. Human action that generates an incorrect result.
impact analysis
component testing
resolution types
error
32. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
incident life cycle phases
Incidents
boundary value analysis
condition determination coverage
33. Tools used to store and manage incidents return phone defects failures or anomalies.
nonfunctional requirements
incident management tools
component integration testing
black-box testing
34. 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
exploratory testing
integration management tools
test tool deployment Success Factors
incident description subheadings
35. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
COTS
efficiency
big-bang testing
36. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
acceptance criteria
test management tool features
action
integration testing
37. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
waterfall model benefits
incremental testing
decision table testing
test analysis & design tasks
38. White-box design technique used to design test cases for a software component using LCSAJ.
failure
backbone integration
LCSAJ testing
maintenance testing
39. A unique identifier for each incident report generated during test execution.
LCSAJ testing
incident report identifier
decision testing
integration management tools
40. Testing software components that are separately testable. Also module program and unit testing.
incident report identifier
component testing
error guessing
test levels
41. Input or combination of inputs required to test software.
acceptance testing
SW development model
black-box testing
conditions
42. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
instrumentation
nonfunctional requirements
defect masking
cause-effect graphic testing
43. An analysis that determines the portion of code on software executed by a set of test cases
Incidents
code coverage
independence of testing
experience-based techniques
44. Insertion of additional code in the existing program in order to count coverage items.
error guessing
instrumentation
Impact subheadings
integration management tools
45. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
load testing
functional requirements
integration
impact analysis
46. Operational testing performed at an _external_ site without involvement of the developing organization.
agile software development model
maintainability
conditions
beta testing
47. Component - Integration - System - Acceptance
exhaustive testing
integration testing
equivalence partitioning
test levels
48. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
test tool deployment Success Factors
exit criteria
decision table testing
stub
49. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
incident description subheadings
condition determination coverage
efficiency
fault attack
50. Ability of software to provide appropriate performance relative to amount of resources used.
functionality
condition determination coverage
efficiency
anomalous events