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. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
debugging
impact
horizontal traceability
cause-effect graphic testing
2. The smallest software item that can be tested in isolation.
beta testing
decision table testing
fault attack
component
3. Components are integrated in the order in which they are developed
maintainability
ad hoc integration
functional incremental integration
test control Tasks
4. An event or item that can be tested using one or more test cases
test condition
documentation tools
configuration management tools
Three main SW development models
5. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
black-box testing
experience-based techniques
waterfall model benefits
6. Tests interfaces between components and between integrated components and systems.
integration management tools
configuration management
big-bang testing
integration testing
7. Conditions required to begin testing activities.
waterfall model benefits
entry criteria
component integration testing
alpha testing
8. 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
SW development model
test data preparation tools
data-driven testing
incremental testing
9. Examine changes made to an operational system cause defects.
integration testing
informal review
operational testing
maintenance testing
10. Testing software components that are separately testable. Also module program and unit testing.
SW development model
LCSAJ testing
component testing
test execution tasks
11. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
bottom-up integration
equivalence partitioning
nonfunctional requirements
12. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
contract acceptance testing
inspection
exhaustive testing
13. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
waterfall model phases
functional requirements
input specifications
experience-based techniques
14. Informal testing technique in which test planning and execution run in parallel
operational testing
waterfall model phases
exploratory testing
condition determination coverage
15. Integration approach components or subsystems are combined all at once rather than in stages.
exit criteria
big-bang testing
defect
IEEE incident report template
16. White-box design technique used to design test cases for a software component using LCSAJ.
test control Tasks
LCSAJ testing
decision table testing
maintainability testing
17. A component of the incident report that determines the actual effect of the incident on the software and its users.
test control Tasks
acceptance testing
impact
decision table
18. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
backbone integration
debugging tools
control flow structure
19. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
conformance testing tools
COTS
black-box testing
integration testing
20. Develop & proiroitize test cases Create groups of test cases Set up test environment
condition determination coverage
IEEE incident report template
test implementation tasks
multiple condition coverage
21. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
configuration management
defect
condition determination coverage
cause-effect graphic testing
22. Black-box test design technique - test cases are designed from a decision table.
decision table testing
maintainability
defect
defect density
23. Requirements that determine the functionality of a software system.
functional requirements
system testing
test levels
condition coverage
24. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
Incidents
acceptance criteria
condition coverage
25. Find defects in code while the software application being tested is running.
SW development model
dynamic analysis tools
integration management tools
equivalence partitioning
26. A unique identifier for each incident report generated during test execution.
incident report identifier
multiple condition coverage
acceptance testing
instrumentation
27. Record details of test cases executed Record order of execution record results
COTS
test log uses
configuration management
acceptance testing
28. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
test planning Tasks
test log uses
IEEE test case specification template
monitor
29. 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
condition determination coverage
coverage
test data preparation tools
test tool deployment Success Factors
30. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
IEEE incident report template
test data preparation tools
incident management tools
conformance testing tools
31. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
agile software development model
IEEE incident report template
failure rate
alpha testing
32. A document that provides the structure for writing test cases.
decision table testing
keyword-driven testing
IEEE test case specification template
impact analysis
33. 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
maintainability
Incidents
test data preparation tools
34. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
anomalous events
efficiency
LCSAJ
incident life cycle phases
35. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
coverage measurement tools
keyword-driven testing
condition determination coverage
IEEE test case specification template
36. Operational testing performed at an _external_ site without involvement of the developing organization.
functionality
functional testing
beta testing
documentation tools
37. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
bottom-up integration
acceptance criteria
test condition
boundary value analysis
38. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
interoperability testing
horizontal traceability
LCSAJ
risk-based testing
39. Special-purpose software used to simulate a component that calls the component under test
waterfall model phases
driver
incident management tools
acceptance testing
40. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
test analysis & design tasks
entry criteria
agile software development model
cyclomatic complexity
41. A review not based on a formal documented procedure
incremental testing
cause-effect graphic testing
informal review
code coverage
42. 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
boundary value analysis
entry criteria
alpha testing
43. Sequence in which data items are accessed or modified by code.
functional testing
maintainability
defect masking
data flow structure
44. Calculates the number of executed branch outcomes in code.
decision coverage
monitor
component testing
black-box testing
45. Measures amount of testing performed by a collection of test cases
integration
cyclomatic complexity
coverage
LCSAJ
46. Occurrences that happen before and after an unexpected event
business process-based testing
impact analysis
entry criteria
anomalous events
47. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
resolution types
operational testing
interoperability
Incidents
48. A task of maintaining and controlling changes to all entities of a system.
independence of testing
test management tool features
functional testing
configuration management
49. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
agile software development model
driver
test analysis & design tasks
50. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
failure rate
impact
experience-based techniques
test analysis & design tasks