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. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
control flow structure
contract acceptance testing
test condition
2. Testing an integrated system to validate it meets requirements
component integration testing
data flow structure
system testing
experience-based techniques
3. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
driver
exit criteria
configuration management tools
4. Occurrences that happen before and after an unexpected event
test management tool features
test data preparation tools
anomalous events
COTS
5. A component of the incident report that determines the actual effect of the incident on the software and its users.
coverage measurement tools
integration management tools
equivalence partitioning
impact
6. A document that provides the structure for writing test cases.
instrumentation
configuration management
IEEE test case specification template
debugging tools
7. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
error
test execution tasks
informal review
testing process phases
8. Record details of test cases executed Record order of execution record results
condition determination coverage
test log uses
incident report identifier
keyword-driven testing
9. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
maintainability testing
functional incremental integration
incident description subheadings
contract acceptance testing
10. Sequence in which instructions are executed through a component or system
control flow structure
equivalence partitions
IEEE test case specification template
defect density
11. Testing software in its operational environment
boundary value analysis
actual result
operational testing
resolution types
12. Informal testing technique in which test planning and execution run in parallel
exploratory testing
beta testing
Three main SW development models
LCSAJ
13. Components are integrated in the order in which they are developed
condition determination coverage
ad hoc integration
efficiency
configuration management
14. Testing performed to determine whether the system meets acceptance criteria
acceptance testing
failure
inspection
waterfall model benefits
15. A task of maintaining and controlling changes to all entities of a system.
configuration management
IEEE incident report template
efficiency
documentation tools
16. Used to replace a component that calls another component.
driver
decision coverage
testing process phases
incremental testing
17. An event or item that can be tested using one or more test cases
horizontal traceability
conditions
anomalous events
test condition
18. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
multiple condition coverage
experience-based techniques
acceptance testing
iterative-incremental development models
19. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
IEEE test case specification template
interoperability testing
defect density
20. All possible combinations of input values and preconditions are tested.
agile software development model
black-box testing
exhaustive testing
waterfall model benefits
21. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
decision testing
incident life cycle phases
Three main SW development models
decision table
22. 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 flow structure
defect
control flow structure
23. Response of the application to an input
action
test implementation tasks
debugging tools
multiple condition coverage
24. Special-purpose software used to simulate a component that calls the component under test
incremental testing
driver
functional incremental integration
test condition
25. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
cyclomatic complexity
incremental testing
horizontal traceability
condition determination coverage
26. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
alpha testing
experience-based techniques
acceptance testing
keyword-driven testing
27. Software products or applications designed to automate manual testing tasks.
automation tools
action
agile software development model
integration
28. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
functional incremental integration
Impact subheadings
condition coverage
failure rate
29. Input or combination of inputs required to test software.
conditions
impact analysis
IEEE incident report template
input specifications
30. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
test execution tasks
incident report
multiple condition coverage
black-box testing
31. Component - Integration - System - Acceptance
risk-based testing
test levels
documentation tools
test condition
32. Find defects in code while the software application being tested is running.
dynamic analysis tools
configuration management tools
testing process phases
actual result
33. 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
test control Tasks
coverage
incident description subheadings
34. Testing software components that are separately testable. Also module program and unit testing.
component testing
waterfall model benefits
incident report
independence of testing
35. Combining components or sytems into larger structural units or subsystems.
integration
LCSAJ
component integration testing
cause-effect graphic testing
36. The capability of a software product to provide agreed and correct output with the required degree of precision
debugging tools
accuracy
component integration testing
maintainability
37. Requirements that determine the functionality of a software system.
interoperability testing
functional requirements
COTS
boundary value analysis
38. 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
control flow structure
contract acceptance testing
COTS
39. Waterfall iterative-incremental "V"
IEEE test case specification template
maintainability
Three main SW development models
monitor
40. Process used to create a SW product from initial conception to public release
Impact subheadings
SW development model
failure rate
debugging tools
41. A table showing combinations of inputs and their associated actions.
condition coverage
IEEE incident report template
Three main SW development models
decision table
42. A unique identifier for each incident report generated during test execution.
test execution tasks
incident report identifier
functionality
SW development model
43. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
exit criteria
informal review
interoperability testing
condition determination coverage
44. Actual inputs required to execute a test case
component testing
input specifications
exploratory testing
contract acceptance testing
45. One defect prevents the detection of another.
defect masking
test levels
action
incident description subheadings
46. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
resolution types
exit criteria
alpha testing
nonfunctional requirements
47. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
test control Tasks
iterative-incremental development models
maintainability
fault attack
48. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
big-bang testing
component testing
control flow structure
49. A set of conditions that a system needs to meet in order to be accepted by end users
ad hoc integration
acceptance criteria
cyclomatic complexity
impact analysis
50. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
integration management tools
data-driven testing
monitor
risk-based testing