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. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
error guessing
cyclomatic complexity
anomalous events
keyword-driven testing
2. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
integration management tools
fault attack
backbone integration
error guessing
3. 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
anomalous events
test implementation tasks
functional incremental integration
agile software development model
4. Integrate different kinds of tools to make test management more efficient and simple.
test implementation tasks
informal review
documentation tools
integration management tools
5. Requirements that determine the functionality of a software system.
failure
conditions
Impact subheadings
functional requirements
6. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
equivalence partitioning
LCSAJ
anomalous events
7. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
acceptance testing
independence of testing
agile software development model
8. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
maintainability testing
exploratory testing
system testing
impact analysis
9. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
efficiency
exit criteria
test tool deployment Success Factors
10. Testing an integrated system to validate it meets requirements
integration testing
system testing
component
COTS
11. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
test analysis & design tasks
decision testing
monitor
backbone integration
12. 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.
inspection
input specifications
automation tools
waterfall model phases
13. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
test planning Tasks
actual result
equivalence partitions
14. Component - Integration - System - Acceptance
test levels
fault attack
test log uses
incident report
15. Testing performed to determine whether the system meets acceptance criteria
acceptance testing
black-box testing
nonfunctional requirements
contract acceptance testing
16. Behavior or response of a software application that you observe when you execute the action steps in the test case.
actual result
dynamic analysis tools
boundary value analysis
defect density
17. Incident Report - Identifier - Summary - Incident - Description - Impact
debugging tools
IEEE incident report template
test implementation tasks
component integration testing
18. Examine changes made to an operational system cause defects.
driver
component testing
maintenance testing
Three main SW development models
19. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
test tool deployment Success Factors
decision coverage
component testing
alpha testing
20. Waterfall iterative-incremental "V"
control flow structure
system testing
Three main SW development models
Incidents
21. An event or item that can be tested using one or more test cases
contract acceptance testing
keyword-driven testing
equivalence partitioning
test condition
22. Black-box test design technique - test cases are designed from a decision table.
error guessing
decision table testing
documentation tools
actual result
23. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
acceptance criteria
waterfall model benefits
SW development model
24. Combining components or sytems into larger structural units or subsystems.
keyword-driven testing
bottom-up integration
integration
maintainability testing
25. Severity - Priority
Impact subheadings
system testing
anomalous events
impact
26. A set of conditions that a system needs to meet in order to be accepted by end users
system testing
acceptance criteria
big-bang testing
driver
27. Software products or applications designed to automate manual testing tasks.
LCSAJ
decision table testing
maintenance testing
automation tools
28. Actual inputs required to execute a test case
LCSAJ testing
input specifications
inspection
actual result
29. The ratio between the number of defects found and the size of the component/system tested.
incident description subheadings
defect density
integration
functional testing
30. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
IEEE incident report template
black-box testing
debugging
31. One defect prevents the detection of another.
cause-effect graphic testing
maintenance testing
impact analysis
defect masking
32. Tools used to identify and calculate coverage items in program code.
big-bang testing
test implementation tasks
exit criteria
coverage measurement tools
33. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
monitor
anomalous events
experience-based techniques
functional testing
34. Find defects in code while the software application being tested is running.
dynamic analysis tools
beta testing
decision table testing
monitor
35. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
agile software development model
interoperability
operational testing
exit criteria
36. Record details of test cases executed Record order of execution record results
experience-based techniques
big-bang testing
test log uses
accuracy
37. Integration approach components or subsystems are combined all at once rather than in stages.
interoperability testing
maintenance testing
configuration management tools
big-bang testing
38. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
condition coverage
COTS
functional incremental integration
configuration management tools
39. Testing software in its operational environment
operational testing
decision testing
waterfall model phases
environmental needs
40. Operational testing performed at an _external_ site without involvement of the developing organization.
decision table
beta testing
actual result
data-driven testing
41. Measures amount of testing performed by a collection of test cases
COTS
maintainability
coverage
test planning Tasks
42. Sequence in which data items are accessed or modified by code.
maintenance testing
debugging
decision table
data flow structure
43. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
debugging
decision testing
Three main SW development models
coverage measurement tools
44. Calculates the number of executed branch outcomes in code.
interoperability testing
beta testing
decision coverage
equivalence partitions
45. The smallest software item that can be tested in isolation.
equivalence partitioning
component
impact
integration testing
46. Testing software components that are separately testable. Also module program and unit testing.
bottom-up integration
component testing
waterfall model benefits
exhaustive testing
47. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template
inspection
test control Tasks
test data preparation tools
anomalous events
48. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
test implementation tasks
conditions
Three main SW development models
horizontal traceability
49. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
boundary value analysis
coverage measurement tools
test condition
test control Tasks
50. All possible combinations of input values and preconditions are tested.
defect masking
exhaustive testing
error
test levels