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. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
incremental testing
nonfunctional requirements
debugging
incident management tools
2. A set of conditions that a system needs to meet in order to be accepted by end users
actual result
acceptance criteria
agile software development model
input specifications
3. Combining components or sytems into larger structural units or subsystems.
condition coverage
failure rate
integration
functional incremental integration
4. Black-box test design technique - test cases are designed from a decision table.
equivalence partitioning
exhaustive testing
decision table testing
input specifications
5. Occurrences that happen before and after an unexpected event
fault attack
anomalous events
exhaustive testing
SW development model
6. 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.
cyclomatic complexity
inspection
decision table
waterfall model benefits
7. A document that records the description of each event that occurs during the testing process and that requires further investigation
failure
COTS
incremental testing
incident report
8. 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
risk-based testing
action
incremental testing
9. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
LCSAJ
test implementation tasks
functionality
resolution types
10. Testing software in its operational environment
exit criteria
operational testing
failure
component testing
11. Allows storage of test input and expected results in one or more central data sources or databases.
test analysis & design tasks
data-driven testing
big-bang testing
Three main SW development models
12. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
fault attack
test planning Tasks
horizontal traceability
system testing
13. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).
integration
configuration management tools
waterfall model benefits
efficiency
14. Conditions required to begin testing activities.
incremental testing
operational testing
control flow structure
entry criteria
15. Tools used to store and manage incidents return phone defects failures or anomalies.
black-box testing
incident management tools
conditions
independence of testing
16. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
component testing
component integration testing
defect
functionality
17. Based on analysis of functional specifications of a system.
functional requirements
interoperability
test levels
functional testing
18. The smallest software item that can be tested in isolation.
component
exit criteria
efficiency
incident description subheadings
19. A review not based on a formal documented procedure
integration testing
informal review
anomalous events
coverage measurement tools
20. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
debugging
control flow structure
configuration management tools
21. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incident report identifier
bottom-up integration
incremental testing
exhaustive testing
22. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities
test planning Tasks
defect masking
efficiency
test management tool features
23. A table showing combinations of inputs and their associated actions.
decision table
instrumentation
automation tools
maintainability testing
24. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
nonfunctional requirements
boundary value analysis
failure rate
testing process phases
25. Informal testing technique in which test planning and execution run in parallel
system testing
impact
ad hoc integration
exploratory testing
26. Human action that generates an incorrect result.
Impact subheadings
error
incident management tools
integration testing
27. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
interoperability
backbone integration
risk-based testing
COTS
28. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
incident management tools
black-box testing
test control Tasks
maintainability testing
29. Special additions or changes to the environment required to run a test case.
IEEE test case specification template
environmental needs
backbone integration
documentation tools
30. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
business process-based testing
waterfall model phases
waterfall model benefits
stub
31. Process used to create a SW product from initial conception to public release
coverage measurement tools
operational testing
multiple condition coverage
SW development model
32. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
interoperability testing
big-bang testing
incident life cycle phases
debugging
33. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
experience-based techniques
integration
test execution tasks
load testing
34. Record details of test cases executed Record order of execution record results
decision coverage
LCSAJ
test log uses
incident report
35. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
maintainability
test levels
IEEE test case specification template
test control Tasks
36. Events that occurred during the testing process our investigation.
driver
LCSAJ
defect masking
Incidents
37. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
entry criteria
iterative-incremental development models
test management tool features
anomalous events
38. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
documentation tools
nonfunctional requirements
failure rate
39. Testing software components that are separately testable. Also module program and unit testing.
decision testing
component testing
resolution types
experience-based techniques
40. Special-purpose software used to simulate a component called by the component under test
data-driven testing
equivalence partitions
stub
exhaustive testing
41. Waterfall iterative-incremental "V"
test log uses
coverage
Three main SW development models
exit criteria
42. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
entry criteria
test log uses
exit criteria
beta testing
43. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
component testing
equivalence partitioning
functional incremental integration
44. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
testing process phases
driver
boundary value analysis
input specifications
45. Software products or applications designed to automate manual testing tasks.
action
automation tools
multiple condition coverage
coverage measurement tools
46. Used to test the functionality of software as mentioned in software requirement specifications.
debugging
exploratory testing
functional testing tool
coverage
47. One defect prevents the detection of another.
acceptance testing
defect masking
actual result
system testing
48. Behavior or response of a software application that you observe when you execute the action steps in the test case.
waterfall model benefits
exploratory testing
test log uses
actual result
49. Increased load (transations) used to test behavior of system under high volume.
test implementation tasks
accuracy
load testing
multiple condition coverage
50. All possible combinations of input values and preconditions are tested.
risk-based testing
exhaustive testing
multiple condition coverage
experience-based techniques