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. 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
keyword-driven testing
configuration management tools
condition coverage
2. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
data flow structure
alpha testing
entry criteria
efficiency
3. An event or item that can be tested using one or more test cases
ad hoc integration
test condition
condition coverage
nonfunctional requirements
4. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
test implementation tasks
incident description subheadings
decision table
boundary value analysis
5. A functional testing approach in which test cases are designed based on business processes.
business process-based testing
LCSAJ testing
big-bang testing
Three main SW development models
6. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect
boundary value analysis
backbone integration
waterfall model benefits
7. Allows storage of test input and expected results in one or more central data sources or databases.
decision table testing
big-bang testing
resolution types
data-driven testing
8. 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.
interoperability
impact analysis
error guessing
inspection
9. Integration approach components or subsystems are combined all at once rather than in stages.
test levels
automation tools
big-bang testing
incremental testing
10. Events that occurred during the testing process our investigation.
defect density
test data preparation tools
data-driven testing
Incidents
11. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
iterative-incremental development models
conformance testing tools
error
independence of testing
12. Testing performed to determine whether the system meets acceptance criteria
SW development model
acceptance testing
monitor
test levels
13. Tools used to store and manage incidents return phone defects failures or anomalies.
Impact subheadings
agile software development model
LCSAJ
incident management tools
14. Process used to create a SW product from initial conception to public release
maintainability
test condition
conformance testing tools
SW development model
15. Calculates the number of executed branch outcomes in code.
test analysis & design tasks
decision coverage
system testing
incident life cycle phases
16. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
component
interoperability
bottom-up integration
17. Severity - Priority
automation tools
big-bang testing
Impact subheadings
IEEE test case specification template
18. Develop & proiroitize test cases Create groups of test cases Set up test environment
fault attack
system testing
conditions
test implementation tasks
19. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
integration testing
driver
data-driven testing
condition coverage
20. Requirements that determine the functionality of a software system.
incident report identifier
cause-effect graphic testing
experience-based techniques
functional requirements
21. A table showing combinations of inputs and their associated actions.
accuracy
test log uses
decision table
entry criteria
22. Separation of testing responsibilities which encourages the accomplishment of objective testing
conditions
test planning Tasks
independence of testing
maintenance testing
23. A review not based on a formal documented procedure
equivalence partitions
input specifications
data flow structure
informal review
24. A unique identifier for each incident report generated during test execution.
incident report identifier
impact analysis
accuracy
incremental testing
25. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
acceptance testing
functionality
operational testing
acceptance criteria
26. Black-box testing technique used to create groups of input conditions that create the same kind of output.
test planning Tasks
equivalence partitioning
inspection
instrumentation
27. Behavior or response of a software application that you observe when you execute the action steps in the test case.
impact analysis
actual result
load testing
LCSAJ testing
28. Occurrences that happen before and after an unexpected event
anomalous events
bottom-up integration
condition determination coverage
defect density
29. Waterfall iterative-incremental "V"
Three main SW development models
instrumentation
coverage
experience-based techniques
30. Response of the application to an input
action
test execution tasks
monitor
conditions
31. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
acceptance testing
system testing
coverage
32. 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
coverage
test execution tasks
integration testing
33. 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
load testing
debugging
waterfall model benefits
test control Tasks
34. White-box design technique used to design test cases for a software component using LCSAJ.
error
documentation tools
LCSAJ testing
bottom-up integration
35. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
input specifications
exhaustive testing
maintainability
integration management tools
36. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
configuration management
driver
cyclomatic complexity
multiple condition coverage
37. A document that provides the structure for writing test cases.
black-box testing
test log uses
exploratory testing
IEEE test case specification template
38. An analysis that determines the portion of code on software executed by a set of test cases
cyclomatic complexity
interoperability
big-bang testing
code coverage
39. Component - Integration - System - Acceptance
anomalous events
test levels
Impact subheadings
equivalence partitions
40. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
configuration management
instrumentation
functional testing
failure rate
41. A set of conditions that a system needs to meet in order to be accepted by end users
entry criteria
decision testing
acceptance criteria
Impact subheadings
42. Measures amount of testing performed by a collection of test cases
incident description subheadings
coverage
multiple condition coverage
functional testing
43. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
test planning Tasks
informal review
configuration management
44. Human action that generates an incorrect result.
acceptance criteria
error
SW development model
load testing
45. Input or combination of inputs required to test software.
decision coverage
conditions
action
operational testing
46. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
interoperability
defect masking
integration testing
47. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
cyclomatic complexity
incident description subheadings
incident report
backbone integration
48. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
actual result
condition determination coverage
risk-based testing
incident life cycle phases
49. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
conditions
independence of testing
keyword-driven testing
horizontal traceability
50. Software products or applications designed to automate manual testing tasks.
exhaustive testing
incident report
automation tools
code coverage