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. An event or item that can be tested using one or more test cases
condition coverage
test condition
driver
waterfall model phases
2. Black-box test design technique - test cases are designed from a decision table.
test log uses
input specifications
decision table testing
functional incremental integration
3. Measures amount of testing performed by a collection of test cases
test planning Tasks
coverage measurement tools
debugging tools
coverage
4. Sequence in which data items are accessed or modified by code.
data flow structure
fault attack
IEEE test case specification template
anomalous events
5. Deviation of a software system from its expected delivery services or results
impact
failure
configuration management
test execution tasks
6. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
decision table testing
test tool deployment Success Factors
exit criteria
coverage measurement tools
7. Requirements that determine the functionality of a software system.
informal review
functional requirements
acceptance testing
decision testing
8. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
integration testing
test implementation tasks
input specifications
9. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model benefits
waterfall model phases
coverage measurement tools
business process-based testing
10. Testing software components that are separately testable. Also module program and unit testing.
component testing
component integration testing
maintainability testing
driver
11. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
backbone integration
ad hoc integration
test management tool features
defect masking
12. A task of maintaining and controlling changes to all entities of a system.
interoperability
test planning Tasks
business process-based testing
configuration management
13. Occurrences that happen before and after an unexpected event
test planning Tasks
test execution tasks
incremental testing
anomalous events
14. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
nonfunctional requirements
iterative-incremental development models
keyword-driven testing
dynamic analysis tools
15. Record details of test cases executed Record order of execution record results
coverage measurement tools
control flow structure
test log uses
informal review
16. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
operational testing
agile software development model
boundary value analysis
big-bang testing
17. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
Impact subheadings
error guessing
functionality
18. Informal testing technique in which test planning and execution run in parallel
conformance testing tools
exploratory testing
functionality
acceptance criteria
19. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
inspection
maintainability testing
data-driven testing
incident report identifier
20. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
horizontal traceability
interoperability testing
impact analysis
test control Tasks
21. Process used to create a SW product from initial conception to public release
interoperability
decision testing
test condition
SW development model
22. Tools used to identify and calculate coverage items in program code.
maintainability testing
coverage measurement tools
component integration testing
entry criteria
23. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
condition determination coverage
COTS
functional requirements
cyclomatic complexity
24. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
decision coverage
functionality
nonfunctional requirements
test control Tasks
25. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
functional testing tool
integration management tools
backbone integration
entry criteria
26. A unique identifier for each incident report generated during test execution.
test management tool features
incident report identifier
incident life cycle phases
driver
27. Used to replace a component that calls another component.
driver
COTS
failure rate
test execution tasks
28. A document that records the description of each event that occurs during the testing process and that requires further investigation
driver
incident report
resolution types
condition coverage
29. 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
test control Tasks
incident life cycle phases
incident description subheadings
30. Increased load (transations) used to test behavior of system under high volume.
test execution tasks
load testing
component
defect
31. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect
entry criteria
resolution types
control flow structure
32. Testing an integrated system to validate it meets requirements
system testing
incident management tools
environmental needs
dynamic analysis tools
33. Software products or applications designed to automate manual testing tasks.
testing process phases
big-bang testing
automation tools
incident description subheadings
34. Separation of testing responsibilities which encourages the accomplishment of objective testing
incident report
independence of testing
integration testing
Impact subheadings
35. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
boundary value analysis
backbone integration
inspection
36. 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.
LCSAJ testing
component integration testing
condition coverage
bottom-up integration
37. Tools used to store and manage incidents return phone defects failures or anomalies.
acceptance criteria
Impact subheadings
condition coverage
incident management tools
38. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
black-box testing
documentation tools
stub
39. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
defect density
incident life cycle phases
beta testing
incident report identifier
40. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
test log uses
maintenance testing
impact analysis
integration management tools
41. 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 table
test planning Tasks
decision testing
test implementation tasks
42. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
alpha testing
keyword-driven testing
business process-based testing
instrumentation
43. Black-box testing technique used to create groups of input conditions that create the same kind of output.
black-box testing
equivalence partitioning
Incidents
failure rate
44. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
testing process phases
cyclomatic complexity
instrumentation
nonfunctional requirements
45. White-box design technique used to design test cases for a software component using LCSAJ.
conformance testing tools
agile software development model
black-box testing
LCSAJ testing
46. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
functional incremental integration
defect density
cause-effect graphic testing
decision table testing
47. Ability of software to provide appropriate performance relative to amount of resources used.
debugging
efficiency
cause-effect graphic testing
fault attack
48. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functional requirements
black-box testing
big-bang testing
functionality
49. Components are integrated in the order in which they are developed
test log uses
ad hoc integration
component
decision table testing
50. A document that provides the structure for writing test cases.
operational testing
coverage measurement tools
horizontal traceability
IEEE test case specification template