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. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
testing process phases
equivalence partitioning
functional incremental integration
2. An analysis that determines the portion of code on software executed by a set of test cases
cause-effect graphic testing
code coverage
decision table
equivalence partitions
3. Informal testing technique in which test planning and execution run in parallel
test log uses
test levels
data-driven testing
exploratory testing
4. Increased load (transations) used to test behavior of system under high volume.
equivalence partitioning
component integration testing
load testing
test log uses
5. Find defects in code while the software application being tested is running.
stub
dynamic analysis tools
incident report identifier
business process-based testing
6. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
input specifications
SW development model
load testing
7. Occurrences that happen before and after an unexpected event
conformance testing tools
decision coverage
anomalous events
maintainability testing
8. Tools used by developers to identify defects in programs.
debugging tools
cyclomatic complexity
condition coverage
iterative-incremental development models
9. Black-box test design technique - test cases are designed from a decision table.
acceptance criteria
incident life cycle phases
equivalence partitions
decision table testing
10. Conditions required to begin testing activities.
interoperability testing
environmental needs
conformance testing tools
entry criteria
11. A component of the incident report that determines the actual effect of the incident on the software and its users.
failure rate
impact
ad hoc integration
equivalence partitioning
12. Incident Report - Identifier - Summary - Incident - Description - Impact
test data preparation tools
incident report identifier
IEEE test case specification template
IEEE incident report template
13. 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
nonfunctional requirements
system testing
conditions
14. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
impact analysis
resolution types
integration
functional incremental integration
15. A table showing combinations of inputs and their associated actions.
environmental needs
experience-based techniques
debugging
decision table
16. Tools used to identify and calculate coverage items in program code.
Three main SW development models
coverage measurement tools
interoperability testing
failure
17. Special additions or changes to the environment required to run a test case.
failure rate
cyclomatic complexity
functional requirements
environmental needs
18. 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
incremental testing
waterfall model benefits
Incidents
decision table testing
19. A functional testing approach in which test cases are designed based on business processes.
failure rate
test implementation tasks
test analysis & design tasks
business process-based testing
20. Events that occurred during the testing process our investigation.
Incidents
cyclomatic complexity
entry criteria
actual result
21. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
maintainability
failure rate
accuracy
conditions
22. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
nonfunctional requirements
test condition
component
23. Process used to create a SW product from initial conception to public release
SW development model
LCSAJ testing
test analysis & design tasks
decision coverage
24. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
failure
conditions
nonfunctional requirements
25. Examine changes made to an operational system cause defects.
action
incident life cycle phases
maintenance testing
SW development model
26. Linear Code Sequence and Jump.
functional incremental integration
LCSAJ
anomalous events
test analysis & design tasks
27. Used to test the functionality of software as mentioned in software requirement specifications.
equivalence partitions
instrumentation
informal review
functional testing tool
28. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
fault attack
cyclomatic complexity
environmental needs
exploratory testing
29. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
horizontal traceability
acceptance criteria
exploratory testing
incident description subheadings
30. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
configuration management tools
waterfall model phases
functional testing
alpha testing
31. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
test data preparation tools
defect
functional testing
acceptance criteria
32. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
test execution tasks
integration management tools
decision table
interoperability testing
33. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
accuracy
IEEE incident report template
horizontal traceability
34. Input or combination of inputs required to test software.
data-driven testing
SW development model
defect density
conditions
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
acceptance criteria
functional requirements
driver
test control Tasks
36. A set of conditions that a system needs to meet in order to be accepted by end users
dynamic analysis tools
inspection
acceptance criteria
alpha testing
37. A review not based on a formal documented procedure
waterfall model benefits
testing process phases
informal review
test levels
38. Components are combined and tested in the order in which basic functionalities start working
functionality
debugging
data flow structure
functional incremental integration
39. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
horizontal traceability
incremental testing
control flow structure
coverage
40. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
error
configuration management
COTS
41. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
acceptance criteria
informal review
keyword-driven testing
boundary value analysis
42. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
documentation tools
test control Tasks
conformance testing tools
43. Human action that generates an incorrect result.
IEEE test case specification template
error
test control Tasks
multiple condition coverage
44. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
component integration testing
iterative-incremental development models
code coverage
acceptance criteria
45. Record details of test cases executed Record order of execution record results
component testing
test analysis & design tasks
test log uses
debugging
46. The ratio between the number of defects found and the size of the component/system tested.
beta testing
incremental testing
load testing
defect density
47. 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
condition determination coverage
agile software development model
load testing
defect density
48. Used to replace a component that calls another component.
bottom-up integration
driver
debugging tools
SW development model
49. White-box design technique used to design test cases for a software component using LCSAJ.
coverage
backbone integration
environmental needs
LCSAJ testing
50. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
beta testing
incident report identifier
decision testing
fault attack