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. Based on analysis of functional specifications of a system.
functional testing
incident management tools
integration testing
monitor
2. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
test control Tasks
failure rate
defect masking
waterfall model phases
3. Components are combined and tested in the order in which basic functionalities start working
risk-based testing
experience-based techniques
functional incremental integration
monitor
4. Human action that generates an incorrect result.
contract acceptance testing
multiple condition coverage
error
test data preparation tools
5. 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
actual result
functional incremental integration
interoperability
6. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
test management tool features
risk-based testing
conformance testing tools
cyclomatic complexity
7. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test control Tasks
conditions
incident management tools
cause-effect graphic testing
8. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
incident management tools
Three main SW development models
decision testing
system testing
9. Software products or applications designed to automate manual testing tasks.
incident life cycle phases
functional testing tool
automation tools
system testing
10. An event or item that can be tested using one or more test cases
resolution types
test condition
input specifications
entry criteria
11. Testing an integrated system to validate it meets requirements
conditions
system testing
IEEE incident report template
incident life cycle phases
12. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
data-driven testing
dynamic analysis tools
maintainability testing
horizontal traceability
13. Components are integrated in the order in which they are developed
beta testing
conformance testing tools
ad hoc integration
accuracy
14. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
decision table testing
backbone integration
incremental testing
functionality
15. Tests interfaces between components and between integrated components and systems.
data-driven testing
integration testing
control flow structure
resolution types
16. Response of the application to an input
incident life cycle phases
acceptance criteria
horizontal traceability
action
17. Integration approach components or subsystems are combined all at once rather than in stages.
action
incremental testing
actual result
big-bang testing
18. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
risk-based testing
defect masking
equivalence partitions
horizontal traceability
19. Requirements that determine the functionality of a software system.
functional requirements
functionality
LCSAJ
monitor
20. 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
component testing
beta testing
test planning Tasks
21. Tools used by developers to identify defects in programs.
debugging tools
maintainability
SW development model
integration
22. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
Incidents
maintainability
load testing
exhaustive testing
23. Informal testing technique in which test planning and execution run in parallel
driver
nonfunctional requirements
maintainability
exploratory testing
24. 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
functional incremental integration
test data preparation tools
bottom-up integration
test execution tasks
25. Testing software components that are separately testable. Also module program and unit testing.
inspection
test analysis & design tasks
instrumentation
component testing
26. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
environmental needs
functional testing
SW development model
27. 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.
maintainability
equivalence partitions
bottom-up integration
data flow structure
28. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
integration
inspection
testing process phases
29. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
functionality
SW development model
functional requirements
30. Tools used to identify and calculate coverage items in program code.
test log uses
nonfunctional requirements
debugging tools
coverage measurement tools
31. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
efficiency
waterfall model phases
maintainability testing
test management tool features
32. 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).
incident management tools
configuration management tools
code coverage
load testing
33. Record details of test cases executed Record order of execution record results
condition coverage
test planning Tasks
test log uses
Incidents
34. Specific groups that represent a set of valid or invalid partitions for input conditions.
COTS
impact analysis
equivalence partitions
configuration management
35. Black-box test design technique - test cases are designed from a decision table.
ad hoc integration
conformance testing tools
incident life cycle phases
decision table testing
36. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
IEEE incident report template
conditions
functionality
37. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
IEEE incident report template
stub
functionality
documentation tools
38. Behavior or response of a software application that you observe when you execute the action steps in the test case.
condition coverage
actual result
exit criteria
conditions
39. Combining components or sytems into larger structural units or subsystems.
integration
incremental testing
ad hoc integration
defect
40. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
decision coverage
testing process phases
resolution types
component integration testing
41. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
horizontal traceability
defect
inspection
beta testing
42. A review not based on a formal documented procedure
defect
informal review
defect masking
test management tool features
43. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
system testing
component
incident report identifier
iterative-incremental development models
44. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
contract acceptance testing
equivalence partitions
IEEE incident report template
45. Sequence in which data items are accessed or modified by code.
dynamic analysis tools
test log uses
automation tools
data flow structure
46. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
agile software development model
integration testing
nonfunctional requirements
47. Process used to create a SW product from initial conception to public release
configuration management
Impact subheadings
SW development model
condition coverage
48. 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
test tool deployment Success Factors
cause-effect graphic testing
waterfall model benefits
component
49. Occurrences that happen before and after an unexpected event
fault attack
anomalous events
component integration testing
incident description subheadings
50. Tools used to store and manage incidents return phone defects failures or anomalies.
exploratory testing
incident management tools
anomalous events
error guessing