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 table showing combinations of inputs and their associated actions.
decision table
load testing
failure rate
multiple condition coverage
2. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
decision coverage
impact analysis
testing process phases
condition coverage
3. 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
test tool deployment Success Factors
accuracy
keyword-driven testing
4. Occurrences that happen before and after an unexpected event
component integration testing
anomalous events
condition coverage
functionality
5. Used to replace a component that calls another component.
functionality
integration
operational testing
driver
6. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
inspection
experience-based techniques
debugging tools
exhaustive testing
7. A document that provides the structure for writing test cases.
system testing
IEEE test case specification template
Impact subheadings
accuracy
8. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
LCSAJ testing
COTS
contract acceptance testing
accuracy
9. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
COTS
impact
test analysis & design tasks
equivalence partitions
10. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
impact analysis
cause-effect graphic testing
functional testing tool
incident report identifier
11. Software products or applications designed to automate manual testing tasks.
exit criteria
coverage measurement tools
bottom-up integration
automation tools
12. Component - Integration - System - Acceptance
test levels
data flow structure
integration testing
condition determination coverage
13. Black-box test design technique - test cases are designed from a decision table.
IEEE test case specification template
decision testing
decision table testing
test analysis & design tasks
14. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
multiple condition coverage
black-box testing
functional testing
test execution tasks
15. Sequence in which data items are accessed or modified by code.
functional incremental integration
data flow structure
Incidents
test analysis & design tasks
16. Integrate different kinds of tools to make test management more efficient and simple.
component testing
integration management tools
control flow structure
equivalence partitioning
17. 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
backbone integration
cyclomatic complexity
incident report identifier
18. The ratio between the number of defects found and the size of the component/system tested.
decision table
defect density
decision testing
cause-effect graphic testing
19. Input or combination of inputs required to test software.
conditions
test condition
fault attack
functional requirements
20. Response of the application to an input
dynamic analysis tools
functional testing
action
COTS
21. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
conformance testing tools
data-driven testing
Impact subheadings
22. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
incremental testing
condition coverage
configuration management tools
resolution types
23. Combining components or sytems into larger structural units or subsystems.
COTS
integration
code coverage
incident description subheadings
24. Increased load (transations) used to test behavior of system under high volume.
load testing
integration testing
data-driven testing
coverage measurement tools
25. A functional testing approach in which test cases are designed based on business processes.
component testing
business process-based testing
integration management tools
conformance testing tools
26. Measures amount of testing performed by a collection of test cases
boundary value analysis
maintainability testing
impact analysis
coverage
27. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
interoperability testing
nonfunctional requirements
debugging tools
impact
28. A set of conditions that a system needs to meet in order to be accepted by end users
black-box testing
business process-based testing
test implementation tasks
acceptance criteria
29. Allows storage of test input and expected results in one or more central data sources or databases.
anomalous events
cause-effect graphic testing
data-driven testing
COTS
30. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
action
SW development model
failure rate
equivalence partitioning
31. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
business process-based testing
contract acceptance testing
waterfall model phases
32. Sequence in which instructions are executed through a component or system
Incidents
functional requirements
control flow structure
condition coverage
33. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
instrumentation
decision coverage
exploratory testing
34. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
Three main SW development models
interoperability
iterative-incremental development models
alpha testing
35. Waterfall iterative-incremental "V"
Three main SW development models
functional requirements
debugging tools
waterfall model phases
36. Record details of test cases executed Record order of execution record results
actual result
entry criteria
test log uses
integration
37. Develop & proiroitize test cases Create groups of test cases Set up test environment
test implementation tasks
exhaustive testing
horizontal traceability
automation tools
38. Deviation of a software system from its expected delivery services or results
beta testing
iterative-incremental development models
efficiency
failure
39. 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
data-driven testing
fault attack
waterfall model benefits
40. Tools used to store and manage incidents return phone defects failures or anomalies.
cyclomatic complexity
incident management tools
condition coverage
iterative-incremental development models
41. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
anomalous events
test execution tasks
independence of testing
bottom-up integration
42. 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
informal review
exhaustive testing
data-driven testing
43. 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.
inspection
LCSAJ
load testing
incident life cycle phases
44. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
decision table
testing process phases
backbone integration
experience-based techniques
45. 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
actual result
ad hoc integration
exit criteria
46. An event or item that can be tested using one or more test cases
test condition
integration management tools
actual result
COTS
47. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
informal review
test control Tasks
exhaustive testing
impact analysis
48. Testing an integrated system to validate it meets requirements
decision table testing
resolution types
input specifications
system testing
49. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
driver
interoperability testing
impact
test execution tasks
50. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
exit criteria
conformance testing tools
test control Tasks
incident report