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. Component - Integration - System - Acceptance
acceptance criteria
test levels
instrumentation
control flow structure
2. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
iterative-incremental development models
exit criteria
experience-based techniques
equivalence partitioning
3. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
decision testing
COTS
big-bang testing
test data preparation tools
4. Informal testing technique in which test planning and execution run in parallel
maintainability testing
exploratory testing
functional incremental integration
exit criteria
5. Tools used by developers to identify defects in programs.
debugging tools
keyword-driven testing
incremental testing
dynamic analysis tools
6. Calculates the number of executed branch outcomes in code.
cause-effect graphic testing
conditions
operational testing
decision coverage
7. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
error guessing
defect
fault attack
Three main SW development models
8. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
functional requirements
test levels
agile software development model
testing process phases
9. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
error
equivalence partitioning
IEEE test case specification template
multiple condition coverage
10. A unique identifier for each incident report generated during test execution.
contract acceptance testing
component integration testing
functionality
incident report identifier
11. Develop & proiroitize test cases Create groups of test cases Set up test environment
test levels
accuracy
test implementation tasks
maintainability testing
12. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
conditions
multiple condition coverage
instrumentation
13. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
integration testing
condition coverage
functionality
boundary value analysis
14. 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
experience-based techniques
stub
fault attack
test tool deployment Success Factors
15. A document that records the description of each event that occurs during the testing process and that requires further investigation
code coverage
dynamic analysis tools
operational testing
incident report
16. 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
data-driven testing
waterfall model benefits
efficiency
acceptance testing
17. Integrate different kinds of tools to make test management more efficient and simple.
impact analysis
integration management tools
inspection
LCSAJ
18. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
test planning Tasks
defect masking
incident description subheadings
black-box testing
19. 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).
entry criteria
monitor
configuration management tools
test condition
20. The ratio between the number of defects found and the size of the component/system tested.
defect density
entry criteria
impact
incremental testing
21. Separation of testing responsibilities which encourages the accomplishment of objective testing
integration management tools
IEEE test case specification template
defect
independence of testing
22. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
integration
alpha testing
data-driven testing
nonfunctional requirements
23. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
incremental testing
cyclomatic complexity
driver
decision table testing
24. Occurrences that happen before and after an unexpected event
anomalous events
IEEE test case specification template
code coverage
coverage measurement tools
25. 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.
failure
input specifications
bottom-up integration
configuration management tools
26. 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.
LCSAJ
integration testing
inspection
experience-based techniques
27. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
functional testing
keyword-driven testing
action
28. Sequence in which instructions are executed through a component or system
horizontal traceability
integration management tools
control flow structure
documentation tools
29. One defect prevents the detection of another.
bottom-up integration
defect masking
functional testing
debugging
30. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
acceptance testing
decision table testing
contract acceptance testing
31. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
driver
informal review
backbone integration
configuration management
32. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
maintenance testing
load testing
incident report
33. A document that provides the structure for writing test cases.
condition determination coverage
IEEE test case specification template
functional requirements
efficiency
34. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
LCSAJ testing
driver
driver
35. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
anomalous events
resolution types
test analysis & design tasks
36. Deviation of a software system from its expected delivery services or results
failure
code coverage
functional incremental integration
acceptance criteria
37. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
automation tools
waterfall model benefits
coverage
38. Tests interfaces between components and between integrated components and systems.
beta testing
integration testing
monitor
keyword-driven testing
39. Sequence in which data items are accessed or modified by code.
data flow structure
functionality
test management tool features
incident report identifier
40. Find defects in code while the software application being tested is running.
defect density
dynamic analysis tools
component testing
risk-based testing
41. Increased load (transations) used to test behavior of system under high volume.
risk-based testing
functionality
exhaustive testing
load testing
42. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
contract acceptance testing
boundary value analysis
test planning Tasks
equivalence partitions
43. Integration approach components or subsystems are combined all at once rather than in stages.
failure rate
big-bang testing
coverage
functional testing
44. Conditions required to begin testing activities.
entry criteria
functional incremental integration
Three main SW development models
defect masking
45. Components are integrated in the order in which they are developed
LCSAJ testing
stub
ad hoc integration
business process-based testing
46. Human action that generates an incorrect result.
Incidents
error
incident description subheadings
test control Tasks
47. Software products or applications designed to automate manual testing tasks.
incident report
coverage measurement tools
automation tools
Incidents
48. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
defect
monitor
Three main SW development models
test analysis & design tasks
49. Incident Report - Identifier - Summary - Incident - Description - Impact
acceptance testing
IEEE incident report template
exploratory testing
informal review
50. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
incident management tools
interoperability
inspection