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. 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 data preparation tools
test planning Tasks
Three main SW development models
big-bang testing
2. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
component testing
maintainability testing
operational testing
inspection
3. Testing an integrated system to validate it meets requirements
system testing
defect density
stub
maintenance testing
4. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
functional incremental integration
test implementation tasks
black-box testing
5. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
functional testing tool
acceptance testing
waterfall model phases
maintainability testing
6. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
component testing
waterfall model phases
test data preparation tools
7. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
actual result
defect
functional testing tool
entry criteria
8. Operational testing performed at an _external_ site without involvement of the developing organization.
integration
beta testing
incident life cycle phases
contract acceptance testing
9. Sequence in which data items are accessed or modified by code.
beta testing
data flow structure
maintainability testing
efficiency
10. White-box design technique used to design test cases for a software component using LCSAJ.
incident life cycle phases
configuration management
impact analysis
LCSAJ testing
11. One defect prevents the detection of another.
defect
inspection
defect masking
error
12. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
Impact subheadings
acceptance testing
error
13. A document that provides the structure for writing test cases.
iterative-incremental development models
defect density
IEEE test case specification template
LCSAJ testing
14. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
iterative-incremental development models
conformance testing tools
fault attack
incident management tools
15. Used to replace a component that calls another component.
alpha testing
horizontal traceability
driver
data flow structure
16. The ratio between the number of defects found and the size of the component/system tested.
automation tools
exhaustive testing
black-box testing
defect density
17. Tests interfaces between components and between integrated components and systems.
code coverage
integration testing
condition determination coverage
resolution types
18. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
documentation tools
ad hoc integration
condition determination coverage
maintainability
19. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
contract acceptance testing
multiple condition coverage
coverage measurement tools
backbone integration
20. Occurrences that happen before and after an unexpected event
data-driven testing
anomalous events
independence of testing
documentation tools
21. A table showing combinations of inputs and their associated actions.
functional requirements
decision table
failure
multiple condition coverage
22. Tools used to store and manage incidents return phone defects failures or anomalies.
component testing
contract acceptance testing
incident management tools
condition determination coverage
23. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
conformance testing tools
testing process phases
test levels
driver
24. Separation of testing responsibilities which encourages the accomplishment of objective testing
instrumentation
interoperability testing
inspection
independence of testing
25. Specific groups that represent a set of valid or invalid partitions for input conditions.
test control Tasks
data flow structure
exploratory testing
equivalence partitions
26. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
test execution tasks
testing process phases
nonfunctional requirements
experience-based techniques
27. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
IEEE test case specification template
big-bang testing
test planning Tasks
28. Calculates the number of executed branch outcomes in code.
iterative-incremental development models
decision coverage
component
test implementation tasks
29. Tools used to identify and calculate coverage items in program code.
integration management tools
coverage measurement tools
defect masking
load testing
30. Testing software components that are separately testable. Also module program and unit testing.
component testing
decision table testing
failure rate
driver
31. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
boundary value analysis
test tool deployment Success Factors
iterative-incremental development models
integration
32. Input or combination of inputs required to test software.
conditions
resolution types
integration
test log uses
33. Events that occurred during the testing process our investigation.
failure rate
test tool deployment Success Factors
Incidents
test planning Tasks
34. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
risk-based testing
exit criteria
documentation tools
efficiency
35. Measures amount of testing performed by a collection of test cases
debugging
IEEE test case specification template
testing process phases
coverage
36. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident life cycle phases
horizontal traceability
incident report
testing process phases
37. Special-purpose software used to simulate a component that calls the component under test
driver
black-box testing
documentation tools
component integration testing
38. Used to test the functionality of software as mentioned in software requirement specifications.
cyclomatic complexity
COTS
functional testing tool
impact
39. A set of conditions that a system needs to meet in order to be accepted by end users
test analysis & design tasks
acceptance criteria
contract acceptance testing
component
40. Sequence in which instructions are executed through a component or system
bottom-up integration
control flow structure
decision testing
decision table testing
41. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
functionality
alpha testing
component integration testing
functional requirements
42. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
operational testing
contract acceptance testing
code coverage
43. Informal testing technique in which test planning and execution run in parallel
stub
exploratory testing
test levels
maintenance testing
44. An event or item that can be tested using one or more test cases
exploratory testing
test condition
monitor
actual result
45. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
Incidents
interoperability testing
inspection
failure rate
46. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
driver
incident report
interoperability testing
47. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
LCSAJ
operational testing
decision table testing
48. Tools used by developers to identify defects in programs.
test tool deployment Success Factors
integration management tools
debugging tools
acceptance criteria
49. Conditions required to begin testing activities.
entry criteria
configuration management
test implementation tasks
interoperability testing
50. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
multiple condition coverage
code coverage
test analysis & design tasks
defect masking