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. A document that records the description of each event that occurs during the testing process and that requires further investigation
test implementation tasks
incident report
bottom-up integration
failure rate
2. A technique used to improve testing coverage by deliberately introducing faults in code.
decision coverage
fault attack
functional testing tool
entry criteria
3. An event or item that can be tested using one or more test cases
error
backbone integration
test condition
fault attack
4. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
experience-based techniques
documentation tools
keyword-driven testing
test log uses
5. Ability of software to provide appropriate performance relative to amount of resources used.
nonfunctional requirements
data-driven testing
coverage
efficiency
6. Waterfall iterative-incremental "V"
exhaustive testing
accuracy
Three main SW development models
functional requirements
7. Informal testing technique in which test planning and execution run in parallel
interoperability testing
exploratory testing
incremental testing
condition determination coverage
8. Combining components or sytems into larger structural units or subsystems.
integration
environmental needs
action
testing process phases
9. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
resolution types
boundary value analysis
test management tool features
10. Increased load (transations) used to test behavior of system under high volume.
business process-based testing
incremental testing
acceptance testing
load testing
11. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
component integration testing
incident description subheadings
condition determination coverage
environmental needs
12. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
independence of testing
maintainability testing
anomalous events
iterative-incremental development models
13. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
maintenance testing
conditions
SW development model
functionality
14. Black-box testing technique used to create groups of input conditions that create the same kind of output.
failure
informal review
equivalence partitioning
equivalence partitions
15. Testing software components that are separately testable. Also module program and unit testing.
incident description subheadings
component testing
waterfall model phases
SW development model
16. Based on analysis of functional specifications of a system.
informal review
conformance testing tools
functional testing
defect masking
17. A review not based on a formal documented procedure
informal review
condition coverage
ad hoc integration
automation tools
18. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
incident life cycle phases
maintenance testing
anomalous events
decision coverage
19. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
entry criteria
equivalence partitions
test management tool features
20. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
dynamic analysis tools
test analysis & design tasks
integration management tools
defect
21. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
anomalous events
test execution tasks
impact analysis
22. 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
COTS
environmental needs
IEEE incident report template
23. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
equivalence partitions
incident report
incident report identifier
24. A unique identifier for each incident report generated during test execution.
incident report identifier
defect
decision table
load testing
25. A table showing combinations of inputs and their associated actions.
inspection
decision table
waterfall model benefits
LCSAJ testing
26. Insertion of additional code in the existing program in order to count coverage items.
inspection
instrumentation
incremental testing
equivalence partitions
27. Sequence in which instructions are executed through a component or system
incident description subheadings
maintainability testing
anomalous events
control flow structure
28. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
experience-based techniques
contract acceptance testing
action
debugging
29. Actual inputs required to execute a test case
input specifications
Three main SW development models
anomalous events
conformance testing tools
30. Black-box test design technique - test cases are designed from a decision table.
data flow structure
decision table testing
experience-based techniques
coverage
31. Occurrences that happen before and after an unexpected event
incident report
test condition
anomalous events
conditions
32. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
test condition
incident report
bottom-up integration
33. Requirements that determine the functionality of a software system.
incident report identifier
Impact subheadings
business process-based testing
functional requirements
34. Testing performed to determine whether the system meets acceptance criteria
code coverage
incident description subheadings
acceptance testing
multiple condition coverage
35. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
conditions
COTS
test control Tasks
waterfall model phases
36. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
iterative-incremental development models
LCSAJ testing
failure
decision testing
37. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
action
coverage measurement tools
fault attack
38. Examine changes made to an operational system cause defects.
automation tools
ad hoc integration
load testing
maintenance testing
39. 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
coverage
conditions
interoperability
40. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
iterative-incremental development models
coverage
testing process phases
incident report identifier
41. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
acceptance testing
exit criteria
bottom-up integration
42. Software products or applications designed to automate manual testing tasks.
failure
action
automation tools
waterfall model benefits
43. Testing an integrated system to validate it meets requirements
system testing
documentation tools
test log uses
incremental testing
44. Events that occurred during the testing process our investigation.
COTS
Incidents
decision coverage
test control Tasks
45. Response of the application to an input
coverage
data-driven testing
test control Tasks
action
46. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
configuration management tools
defect
component
incident report identifier
47. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
component integration testing
waterfall model phases
defect
48. Record details of test cases executed Record order of execution record results
test log uses
beta testing
equivalence partitions
component
49. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
test implementation tasks
fault attack
component integration testing
alpha testing
50. Specific groups that represent a set of valid or invalid partitions for input conditions.
equivalence partitions
test implementation tasks
experience-based techniques
control flow structure