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. A table showing combinations of inputs and their associated actions.
test planning Tasks
functional testing tool
functional requirements
decision table
2. A review not based on a formal documented procedure
informal review
configuration management tools
multiple condition coverage
driver
3. A component of the incident report that determines the actual effect of the incident on the software and its users.
input specifications
LCSAJ
cyclomatic complexity
impact
4. Occurrences that happen before and after an unexpected event
iterative-incremental development models
anomalous events
informal review
condition determination coverage
5. Process used to create a SW product from initial conception to public release
SW development model
testing process phases
COTS
error
6. Testing software in its operational environment
LCSAJ testing
operational testing
incident description subheadings
decision testing
7. Human action that generates an incorrect result.
Impact subheadings
error
incident report
horizontal traceability
8. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
alpha testing
test tool deployment Success Factors
maintainability
agile software development model
9. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
dynamic analysis tools
experience-based techniques
test planning Tasks
test execution tasks
10. The capability of a software product to provide agreed and correct output with the required degree of precision
exploratory testing
backbone integration
LCSAJ
accuracy
11. Software products or applications designed to automate manual testing tasks.
automation tools
test levels
conformance testing tools
documentation tools
12. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
Incidents
testing process phases
keyword-driven testing
SW development model
13. 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
test data preparation tools
functional incremental integration
experience-based techniques
integration management tools
14. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
incident life cycle phases
component
efficiency
decision table testing
15. A document that records the description of each event that occurs during the testing process and that requires further investigation
functional testing
defect density
test analysis & design tasks
incident report
16. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
SW development model
failure
decision table
cyclomatic complexity
17. Components are integrated in the order in which they are developed
incident report
functional testing tool
LCSAJ
ad hoc integration
18. Integrate different kinds of tools to make test management more efficient and simple.
horizontal traceability
integration management tools
coverage measurement tools
business process-based testing
19. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
interoperability testing
iterative-incremental development models
defect
code coverage
20. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
condition coverage
stub
configuration management tools
risk-based testing
21. Combining components or sytems into larger structural units or subsystems.
integration
impact
testing process phases
incident life cycle phases
22. Tools used by developers to identify defects in programs.
debugging tools
COTS
instrumentation
exploratory testing
23. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
cause-effect graphic testing
black-box testing
load testing
24. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
waterfall model phases
conformance testing tools
anomalous events
keyword-driven testing
25. The process of finding analyzing and removing causes of failure in a software product.
debugging
dynamic analysis tools
resolution types
nonfunctional requirements
26. Actual inputs required to execute a test case
cyclomatic complexity
IEEE incident report template
input specifications
independence of testing
27. Insertion of additional code in the existing program in order to count coverage items.
defect
data-driven testing
conditions
instrumentation
28. Integration approach components or subsystems are combined all at once rather than in stages.
test condition
big-bang testing
condition determination coverage
test analysis & design tasks
29. Allows storage of test input and expected results in one or more central data sources or databases.
functional testing tool
instrumentation
waterfall model phases
data-driven testing
30. Waterfall iterative-incremental "V"
test execution tasks
functional requirements
Three main SW development models
cyclomatic complexity
31. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
beta testing
interoperability
maintainability testing
Three main SW development models
32. Tests interfaces between components and between integrated components and systems.
integration testing
horizontal traceability
test log uses
functional incremental integration
33. Special-purpose software used to simulate a component that calls the component under test
driver
test tool deployment Success Factors
risk-based testing
system testing
34. Events that occurred during the testing process our investigation.
debugging
exploratory testing
Incidents
bottom-up integration
35. Components are combined and tested in the order in which basic functionalities start working
component
defect density
functional incremental integration
test tool deployment Success Factors
36. 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
Incidents
impact
functional testing tool
waterfall model benefits
37. Sequence in which data items are accessed or modified by code.
exit criteria
data flow structure
agile software development model
keyword-driven testing
38. Sequence in which instructions are executed through a component or system
control flow structure
IEEE incident report template
black-box testing
test implementation tasks
39. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
incident report identifier
decision coverage
exit criteria
40. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
accuracy
backbone integration
test condition
big-bang testing
41. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
incident management tools
interoperability testing
exhaustive testing
boundary value analysis
42. All possible combinations of input values and preconditions are tested.
exhaustive testing
monitor
system testing
independence of testing
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.
dynamic analysis tools
decision testing
load testing
boundary value analysis
44. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
accuracy
horizontal traceability
integration
integration management tools
45. Ability of software to provide appropriate performance relative to amount of resources used.
horizontal traceability
monitor
efficiency
component testing
46. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
load testing
COTS
big-bang testing
47. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
functional requirements
test control Tasks
LCSAJ
iterative-incremental development models
48. Measures amount of testing performed by a collection of test cases
acceptance testing
coverage
test levels
condition coverage
49. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
LCSAJ
experience-based techniques
cause-effect graphic testing
multiple condition coverage
50. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
SW development model
bottom-up integration
failure rate