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. Human action that generates an incorrect result.
coverage
configuration management
horizontal traceability
error
2. Testing performed to determine whether the system meets acceptance criteria
test execution tasks
test control Tasks
error
acceptance testing
3. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
testing process phases
driver
integration testing
keyword-driven testing
4. 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
resolution types
incident life cycle phases
test tool deployment Success Factors
inspection
5. All possible combinations of input values and preconditions are tested.
component testing
Impact subheadings
boundary value analysis
exhaustive testing
6. 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).
configuration management tools
test levels
condition coverage
test log uses
7. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
risk-based testing
agile software development model
test analysis & design tasks
8. Combining components or sytems into larger structural units or subsystems.
fault attack
configuration management
Impact subheadings
integration
9. An analysis that determines the portion of code on software executed by a set of test cases
test analysis & design tasks
functional testing
condition coverage
code coverage
10. Sequence in which data items are accessed or modified by code.
component integration testing
data flow structure
test tool deployment Success Factors
inspection
11. Behavior or response of a software application that you observe when you execute the action steps in the test case.
impact
independence of testing
actual result
decision table
12. Calculates the number of executed branch outcomes in code.
defect masking
test condition
decision coverage
exploratory testing
13. 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
accuracy
Three main SW development models
maintenance testing
14. 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
test tool deployment Success Factors
risk-based testing
IEEE incident report template
waterfall model benefits
15. White-box design technique used to design test cases for a software component using LCSAJ.
integration testing
error guessing
LCSAJ testing
configuration management tools
16. Allows storage of test input and expected results in one or more central data sources or databases.
fault attack
data-driven testing
SW development model
backbone integration
17. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
incident life cycle phases
failure rate
condition determination coverage
acceptance criteria
18. Ability of software to provide appropriate performance relative to amount of resources used.
beta testing
efficiency
control flow structure
alpha testing
19. Actual inputs required to execute a test case
test analysis & design tasks
input specifications
functional testing tool
maintainability
20. Examine changes made to an operational system cause defects.
debugging
equivalence partitions
functional testing
maintenance testing
21. 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
error guessing
entry criteria
decision table
22. Software products or applications designed to automate manual testing tasks.
business process-based testing
automation tools
error
test control Tasks
23. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
operational testing
monitor
interoperability testing
defect masking
24. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
black-box testing
driver
component
functionality
25. 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
IEEE incident report template
acceptance testing
SW development model
26. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
dynamic analysis tools
test analysis & design tasks
accuracy
27. The process of finding analyzing and removing causes of failure in a software product.
debugging
condition coverage
entry criteria
error guessing
28. Increased load (transations) used to test behavior of system under high volume.
accuracy
defect masking
load testing
experience-based techniques
29. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
test planning Tasks
operational testing
load testing
30. Components are combined and tested in the order in which basic functionalities start working
agile software development model
functional incremental integration
defect masking
keyword-driven testing
31. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
impact analysis
test analysis & design tasks
test levels
automation tools
32. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
functional testing
error
backbone integration
iterative-incremental development models
33. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
SW development model
iterative-incremental development models
efficiency
34. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
boundary value analysis
test control Tasks
cyclomatic complexity
35. An event or item that can be tested using one or more test cases
test condition
integration testing
stub
Impact subheadings
36. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
error
efficiency
risk-based testing
IEEE incident report template
37. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
anomalous events
acceptance criteria
beta testing
decision testing
38. Response of the application to an input
equivalence partitions
decision coverage
action
failure rate
39. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
boundary value analysis
debugging
impact analysis
incremental testing
40. Tools used by developers to identify defects in programs.
action
debugging tools
equivalence partitioning
multiple condition coverage
41. Specific groups that represent a set of valid or invalid partitions for input conditions.
conformance testing tools
driver
keyword-driven testing
equivalence partitions
42. Incident Report - Identifier - Summary - Incident - Description - Impact
driver
independence of testing
risk-based testing
IEEE incident report template
43. 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
test condition
horizontal traceability
incident description subheadings
44. Special-purpose software used to simulate a component called by the component under test
incident report identifier
stub
documentation tools
impact analysis
45. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
stub
multiple condition coverage
incident description subheadings
Three main SW development models
46. The smallest software item that can be tested in isolation.
coverage
business process-based testing
component
incident management tools
47. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
test planning Tasks
test analysis & design tasks
multiple condition coverage
automation tools
48. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
instrumentation
test planning Tasks
test analysis & design tasks
component integration testing
49. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
failure rate
maintainability
coverage
50. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
component
test control Tasks
exit criteria
incident description subheadings