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. Special-purpose software used to simulate a component called by the component under test
decision table
big-bang testing
stub
Incidents
2. Testing an integrated system to validate it meets requirements
big-bang testing
condition coverage
inspection
system testing
3. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
stub
failure rate
test tool deployment Success Factors
operational testing
4. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
failure rate
maintenance testing
test log uses
5. Tests interfaces between components and between integrated components and systems.
failure
failure rate
fault attack
integration testing
6. Special-purpose software used to simulate a component that calls the component under test
anomalous events
black-box testing
test levels
driver
7. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
experience-based techniques
incident report
informal review
decision testing
8. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
ad hoc integration
big-bang testing
resolution types
informal review
9. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
configuration management tools
horizontal traceability
test levels
IEEE incident report template
10. Response of the application to an input
action
anomalous events
instrumentation
test planning Tasks
11. Specific groups that represent a set of valid or invalid partitions for input conditions.
documentation tools
equivalence partitions
data flow structure
defect
12. Conditions required to begin testing activities.
test control Tasks
condition coverage
entry criteria
environmental needs
13. 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.
SW development model
test log uses
inspection
debugging tools
14. An event or item that can be tested using one or more test cases
test condition
condition determination coverage
integration
maintainability testing
15. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
exit criteria
Incidents
test analysis & design tasks
driver
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
test planning Tasks
informal review
cyclomatic complexity
Impact subheadings
17. Used to replace a component that calls another component.
Three main SW development models
boundary value analysis
ad hoc integration
driver
18. Software products or applications designed to automate manual testing tasks.
iterative-incremental development models
stub
automation tools
test implementation tasks
19. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
incident report identifier
error guessing
test levels
decision table
20. Components are combined and tested in the order in which basic functionalities start working
bottom-up integration
driver
experience-based techniques
functional incremental integration
21. A document that provides the structure for writing test cases.
impact
test log uses
IEEE test case specification template
configuration management
22. Testing performed to determine whether the system meets acceptance criteria
incident description subheadings
iterative-incremental development models
acceptance testing
boundary value analysis
23. The process of finding analyzing and removing causes of failure in a software product.
business process-based testing
functional requirements
debugging
exploratory testing
24. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
stub
COTS
black-box testing
automation tools
25. Integration approach components or subsystems are combined all at once rather than in stages.
business process-based testing
incident management tools
big-bang testing
incident life cycle phases
26. Input or combination of inputs required to test software.
experience-based techniques
condition determination coverage
conditions
load testing
27. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
driver
Impact subheadings
conditions
monitor
28. 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).
resolution types
ad hoc integration
waterfall model phases
configuration management tools
29. Measures amount of testing performed by a collection of test cases
iterative-incremental development models
decision table
coverage
cause-effect graphic testing
30. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
Incidents
interoperability testing
monitor
condition determination coverage
31. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
integration management tools
agile software development model
driver
32. 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
defect density
test tool deployment Success Factors
efficiency
instrumentation
33. Integrate different kinds of tools to make test management more efficient and simple.
beta testing
integration management tools
inspection
documentation tools
34. Special additions or changes to the environment required to run a test case.
risk-based testing
conformance testing tools
multiple condition coverage
environmental needs
35. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
stub
alpha testing
LCSAJ
accuracy
36. A unique identifier for each incident report generated during test execution.
incident life cycle phases
test implementation tasks
test condition
incident report identifier
37. A review not based on a formal documented procedure
informal review
test condition
incident management tools
defect density
38. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
nonfunctional requirements
test analysis & design tasks
waterfall model benefits
condition coverage
39. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
interoperability
informal review
Three main SW development models
40. Used to test the functionality of software as mentioned in software requirement specifications.
equivalence partitioning
control flow structure
functional testing tool
action
41. 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.
bottom-up integration
test implementation tasks
error
risk-based testing
42. Severity - Priority
control flow structure
system testing
Impact subheadings
experience-based techniques
43. Record details of test cases executed Record order of execution record results
environmental needs
agile software development model
maintainability
test log uses
44. One defect prevents the detection of another.
defect masking
data-driven testing
failure rate
functional testing tool
45. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
risk-based testing
maintenance testing
load testing
iterative-incremental development models
46. The smallest software item that can be tested in isolation.
monitor
component
waterfall model benefits
IEEE incident report template
47. Develop & proiroitize test cases Create groups of test cases Set up test environment
debugging tools
test implementation tasks
error guessing
independence of testing
48. Human action that generates an incorrect result.
ad hoc integration
error
instrumentation
exhaustive testing
49. Increased load (transations) used to test behavior of system under high volume.
boundary value analysis
load testing
LCSAJ testing
equivalence partitioning
50. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
maintenance testing
condition determination coverage
exit criteria