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. Sequence in which instructions are executed through a component or system
equivalence partitions
accuracy
functional incremental integration
control flow structure
2. Integrate different kinds of tools to make test management more efficient and simple.
interoperability testing
waterfall model benefits
integration management tools
component integration testing
3. Conditions required to begin testing activities.
test execution tasks
driver
entry criteria
maintainability testing
4. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.
conditions
IEEE test case specification template
bottom-up integration
exploratory testing
5. White-box design technique used to design test cases for a software component using LCSAJ.
cyclomatic complexity
agile software development model
LCSAJ testing
environmental needs
6. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintainability testing
operational testing
test log uses
control flow structure
7. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
test log uses
incident life cycle phases
defect masking
8. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
iterative-incremental development models
alpha testing
IEEE incident report template
environmental needs
9. Severity - Priority
data flow structure
Impact subheadings
risk-based testing
multiple condition coverage
10. A component of the incident report that determines the actual effect of the incident on the software and its users.
test control Tasks
cause-effect graphic testing
impact
operational testing
11. Component - Integration - System - Acceptance
operational testing
test levels
test planning Tasks
cause-effect graphic testing
12. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
system testing
resolution types
test control Tasks
data flow structure
13. A table showing combinations of inputs and their associated actions.
decision table
component
error
backbone integration
14. Waterfall iterative-incremental "V"
actual result
decision testing
Three main SW development models
business process-based testing
15. Ability of software to provide appropriate performance relative to amount of resources used.
fault attack
IEEE test case specification template
efficiency
test data preparation tools
16. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities
fault attack
waterfall model phases
boundary value analysis
test planning Tasks
17. Record details of test cases executed Record order of execution record results
error
component
test log uses
input specifications
18. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
automation tools
test log uses
big-bang testing
interoperability
19. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
acceptance criteria
error
equivalence partitioning
black-box testing
20. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
business process-based testing
condition determination coverage
dynamic analysis tools
exhaustive testing
21. 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.
error guessing
defect masking
inspection
business process-based testing
22. Testing software components that are separately testable. Also module program and unit testing.
IEEE incident report template
incident report identifier
integration testing
component testing
23. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
fault attack
independence of testing
maintenance testing
test execution tasks
24. Based on analysis of functional specifications of a system.
test management tool features
maintainability
functional testing
ad hoc integration
25. Behavior or response of a software application that you observe when you execute the action steps in the test case.
defect density
test condition
incident management tools
actual result
26. Find defects in code while the software application being tested is running.
decision table testing
configuration management
error guessing
dynamic analysis tools
27. Linear Code Sequence and Jump.
waterfall model phases
load testing
LCSAJ
test execution tasks
28. 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
integration management tools
waterfall model benefits
maintainability testing
operational testing
29. 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
test tool deployment Success Factors
incremental testing
maintainability
30. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
black-box testing
incident life cycle phases
defect
test implementation tasks
31. Sequence in which data items are accessed or modified by code.
decision table testing
black-box testing
control flow structure
data flow structure
32. Specific groups that represent a set of valid or invalid partitions for input conditions.
equivalence partitions
cause-effect graphic testing
decision testing
test condition
33. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
debugging
risk-based testing
impact
acceptance testing
34. A review not based on a formal documented procedure
incremental testing
maintainability
multiple condition coverage
informal review
35. An analysis that determines the portion of code on software executed by a set of test cases
actual result
operational testing
code coverage
condition coverage
36. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
test analysis & design tasks
error guessing
test planning Tasks
incident life cycle phases
37. Calculates the number of executed branch outcomes in code.
test implementation tasks
Incidents
decision coverage
inspection
38. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
black-box testing
nonfunctional requirements
maintenance testing
component
39. A unique identifier for each incident report generated during test execution.
incident report identifier
boundary value analysis
big-bang testing
defect
40. Integration approach components or subsystems are combined all at once rather than in stages.
integration
coverage
component integration testing
big-bang testing
41. Deviation of a software system from its expected delivery services or results
multiple condition coverage
maintainability
failure
efficiency
42. Tools used by developers to identify defects in programs.
debugging tools
incident report identifier
coverage measurement tools
operational testing
43. Testing an integrated system to validate it meets requirements
system testing
acceptance testing
iterative-incremental development models
interoperability
44. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
action
failure rate
input specifications
independence of testing
45. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
big-bang testing
keyword-driven testing
functional requirements
dynamic analysis tools
46. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
inspection
impact analysis
risk-based testing
nonfunctional requirements
47. Incident Report - Identifier - Summary - Incident - Description - Impact
driver
inspection
IEEE test case specification template
IEEE incident report template
48. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
Incidents
defect
decision table
maintainability
49. Tools used to identify and calculate coverage items in program code.
impact
coverage measurement tools
incremental testing
nonfunctional requirements
50. Operational testing performed at an _external_ site without involvement of the developing organization.
actual result
bottom-up integration
beta testing
data flow structure