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 set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
environmental needs
incident report identifier
test execution tasks
2. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
beta testing
failure
coverage measurement tools
3. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
load testing
efficiency
waterfall model benefits
4. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
configuration management tools
action
Incidents
5. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
impact
backbone integration
ad hoc integration
exhaustive testing
6. A review not based on a formal documented procedure
exploratory testing
driver
multiple condition coverage
informal review
7. 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
condition coverage
contract acceptance testing
acceptance criteria
8. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
incident management tools
incremental testing
risk-based testing
maintainability testing
9. A unique identifier for each incident report generated during test execution.
component integration testing
cause-effect graphic testing
incident report identifier
accuracy
10. Increased load (transations) used to test behavior of system under high volume.
beta testing
conditions
load testing
incident description subheadings
11. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
monitor
SW development model
incident report identifier
12. Find defects in code while the software application being tested is running.
dynamic analysis tools
coverage
keyword-driven testing
waterfall model phases
13. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
defect
maintainability
entry criteria
maintainability testing
14. Special-purpose software used to simulate a component that calls the component under test
big-bang testing
driver
conditions
defect masking
15. Special-purpose software used to simulate a component called by the component under test
stub
test execution tasks
COTS
test data preparation tools
16. Software products or applications designed to automate manual testing tasks.
control flow structure
automation tools
driver
test control Tasks
17. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
test control Tasks
system testing
component integration testing
beta testing
18. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
component testing
black-box testing
debugging tools
functionality
19. 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.
condition coverage
bottom-up integration
action
ad hoc integration
20. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
informal review
monitor
keyword-driven testing
failure
21. 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
defect
acceptance criteria
backbone integration
test tool deployment Success Factors
22. A functional testing approach in which test cases are designed based on business processes.
defect masking
business process-based testing
component
incremental testing
23. Combining components or sytems into larger structural units or subsystems.
condition coverage
integration
code coverage
exit criteria
24. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test analysis & design tasks
defect masking
error
keyword-driven testing
25. Behavior or response of a software application that you observe when you execute the action steps in the test case.
monitor
actual result
COTS
component
26. Occurrences that happen before and after an unexpected event
testing process phases
debugging
anomalous events
bottom-up integration
27. Response of the application to an input
decision table
incremental testing
action
functional incremental integration
28. 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 levels
action
inspection
independence of testing
29. Sequence in which instructions are executed through a component or system
test condition
conformance testing tools
black-box testing
control flow structure
30. Testing software components that are separately testable. Also module program and unit testing.
component testing
incident management tools
test analysis & design tasks
actual result
31. Linear Code Sequence and Jump.
test levels
LCSAJ
data-driven testing
informal review
32. Special additions or changes to the environment required to run a test case.
conformance testing tools
incident life cycle phases
environmental needs
test management tool features
33. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
error guessing
contract acceptance testing
alpha testing
component
34. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
failure
test log uses
condition determination coverage
inspection
35. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
decision testing
beta testing
fault attack
exit criteria
36. Integrate different kinds of tools to make test management more efficient and simple.
load testing
Impact subheadings
integration management tools
COTS
37. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
input specifications
incident life cycle phases
nonfunctional requirements
incident description subheadings
38. Black-box test design technique - test cases are designed from a decision table.
decision table testing
component testing
dynamic analysis tools
code coverage
39. Components are combined and tested in the order in which basic functionalities start working
incremental testing
functional incremental integration
acceptance criteria
integration management tools
40. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
informal review
decision table testing
alpha testing
condition determination coverage
41. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
ad hoc integration
load testing
dynamic analysis tools
42. Examine changes made to an operational system cause defects.
maintenance testing
entry criteria
acceptance testing
decision table
43. Tests interfaces between components and between integrated components and systems.
accuracy
integration testing
efficiency
debugging tools
44. The ratio between the number of defects found and the size of the component/system tested.
defect density
component
efficiency
Three main SW development models
45. Components are integrated in the order in which they are developed
ad hoc integration
equivalence partitioning
functionality
COTS
46. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
test implementation tasks
beta testing
experience-based techniques
functional requirements
47. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
exhaustive testing
condition determination coverage
decision testing
monitor
48. Insertion of additional code in the existing program in order to count coverage items.
functionality
instrumentation
debugging tools
test planning Tasks
49. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
decision testing
Incidents
inspection
50. The process of finding analyzing and removing causes of failure in a software product.
debugging
instrumentation
functional requirements
exploratory testing