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 functional testing approach in which test cases are designed based on business processes.
COTS
business process-based testing
acceptance criteria
incident report identifier
2. 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
maintenance testing
waterfall model benefits
acceptance testing
impact
3. Components are integrated in the order in which they are developed
data flow structure
ad hoc integration
defect masking
keyword-driven testing
4. Process used to create a SW product from initial conception to public release
SW development model
informal review
big-bang testing
efficiency
5. Increased load (transations) used to test behavior of system under high volume.
incident report
code coverage
incident description subheadings
load testing
6. Response of the application to an input
business process-based testing
action
test planning Tasks
Impact subheadings
7. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incremental testing
decision coverage
incident life cycle phases
anomalous events
8. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
maintainability testing
test analysis & design tasks
defect density
waterfall model benefits
9. White-box design technique used to design test cases for a software component using LCSAJ.
actual result
decision testing
fault attack
LCSAJ testing
10. Based on analysis of functional specifications of a system.
functional testing
test data preparation tools
driver
input specifications
11. Requirements that determine the functionality of a software system.
integration testing
functional requirements
incident description subheadings
maintainability
12. The process of finding analyzing and removing causes of failure in a software product.
acceptance testing
debugging
informal review
acceptance criteria
13. Special additions or changes to the environment required to run a test case.
independence of testing
environmental needs
condition coverage
load testing
14. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
monitor
test control Tasks
test execution tasks
COTS
15. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
independence of testing
contract acceptance testing
conformance testing tools
agile software development model
16. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
actual result
input specifications
test condition
17. Occurrences that happen before and after an unexpected event
fault attack
condition coverage
experience-based techniques
anomalous events
18. Special-purpose software used to simulate a component called by the component under test
decision testing
operational testing
stub
incremental testing
19. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
cyclomatic complexity
experience-based techniques
test implementation tasks
contract acceptance testing
20. Deviation of a software system from its expected delivery services or results
driver
dynamic analysis tools
failure
test tool deployment Success Factors
21. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
error
risk-based testing
beta testing
alpha testing
22. Software products or applications designed to automate manual testing tasks.
bottom-up integration
defect density
automation tools
system testing
23. The ratio between the number of defects found and the size of the component/system tested.
SW development model
defect density
incident report identifier
dynamic analysis tools
24. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
alpha testing
multiple condition coverage
stub
condition determination coverage
25. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
maintenance testing
functional testing
test management tool features
monitor
26. A table showing combinations of inputs and their associated actions.
incident life cycle phases
decision table
impact analysis
incident report identifier
27. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
dynamic analysis tools
keyword-driven testing
test tool deployment Success Factors
documentation tools
28. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations
agile software development model
environmental needs
functional requirements
waterfall model phases
29. Waterfall iterative-incremental "V"
conformance testing tools
entry criteria
Three main SW development models
test management tool features
30. Sequence in which instructions are executed through a component or system
control flow structure
Impact subheadings
Three main SW development models
informal review
31. A review not based on a formal documented procedure
informal review
ad hoc integration
actual result
iterative-incremental development models
32. 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
environmental needs
test tool deployment Success Factors
nonfunctional requirements
dynamic analysis tools
33. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
decision testing
waterfall model benefits
test log uses
34. Components are combined and tested in the order in which basic functionalities start working
impact analysis
integration
functional incremental integration
exhaustive testing
35. Separation of testing responsibilities which encourages the accomplishment of objective testing
functionality
failure rate
anomalous events
independence of testing
36. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
incremental testing
test tool deployment Success Factors
backbone integration
37. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
cause-effect graphic testing
test condition
IEEE test case specification template
iterative-incremental development models
38. Tests interfaces between components and between integrated components and systems.
maintainability testing
test log uses
condition coverage
integration testing
39. Events that occurred during the testing process our investigation.
condition coverage
incident report
load testing
Incidents
40. Integration approach components or subsystems are combined all at once rather than in stages.
horizontal traceability
failure rate
test management tool features
big-bang testing
41. Find defects in code while the software application being tested is running.
error
LCSAJ testing
equivalence partitioning
dynamic analysis tools
42. Conditions required to begin testing activities.
entry criteria
condition coverage
stub
impact
43. Calculates the number of executed branch outcomes in code.
code coverage
decision coverage
boundary value analysis
COTS
44. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
automation tools
system testing
condition determination coverage
test condition
45. All possible combinations of input values and preconditions are tested.
dynamic analysis tools
exhaustive testing
fault attack
test analysis & design tasks
46. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
backbone integration
error guessing
test execution tasks
efficiency
47. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
interoperability
stub
functionality
acceptance criteria
48. Specific groups that represent a set of valid or invalid partitions for input conditions.
decision table testing
equivalence partitions
waterfall model phases
incremental testing
49. Tools used by developers to identify defects in programs.
configuration management
debugging tools
independence of testing
component
50. Testing software components that are separately testable. Also module program and unit testing.
component testing
backbone integration
incident report identifier
stub