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. Integrate different kinds of tools to make test management more efficient and simple.
driver
cyclomatic complexity
acceptance testing
integration management tools
2. Process used to create a SW product from initial conception to public release
component testing
SW development model
maintainability
component integration testing
3. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
SW development model
contract acceptance testing
error guessing
interoperability
4. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test analysis & design tasks
component
component testing
actual result
5. Used to replace a component that calls another component.
driver
error guessing
input specifications
defect masking
6. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
functional incremental integration
decision table testing
debugging tools
backbone integration
7. An event or item that can be tested using one or more test cases
component testing
test condition
system testing
error guessing
8. Tools used to identify and calculate coverage items in program code.
inspection
coverage measurement tools
waterfall model phases
acceptance criteria
9. Informal testing technique in which test planning and execution run in parallel
exploratory testing
nonfunctional requirements
contract acceptance testing
coverage measurement tools
10. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
agile software development model
resolution types
testing process phases
11. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
data flow structure
LCSAJ
functional testing tool
12. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
component
Impact subheadings
condition coverage
independence of testing
13. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
monitor
COTS
data-driven testing
conformance testing tools
14. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
control flow structure
documentation tools
actual result
configuration management tools
15. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
test implementation tasks
error guessing
bottom-up integration
16. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
integration
integration testing
exploratory testing
impact analysis
17. Based on analysis of functional specifications of a system.
functional testing
interoperability
test condition
code coverage
18. Integration approach components or subsystems are combined all at once rather than in stages.
exploratory testing
IEEE incident report template
big-bang testing
SW development model
19. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
error
testing process phases
condition coverage
load testing
20. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
driver
cyclomatic complexity
boundary value analysis
component
21. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
incident report identifier
functionality
load testing
condition coverage
22. The ratio between the number of defects found and the size of the component/system tested.
defect density
informal review
waterfall model benefits
error
23. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
Three main SW development models
iterative-incremental development models
equivalence partitioning
business process-based testing
24. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
accuracy
informal review
IEEE incident report template
component integration testing
25. Measures amount of testing performed by a collection of test cases
informal review
input specifications
coverage
inspection
26. Tests interfaces between components and between integrated components and systems.
condition determination coverage
decision table
integration testing
condition coverage
27. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
test tool deployment Success Factors
informal review
waterfall model benefits
defect
28. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
interoperability
maintenance testing
Impact subheadings
29. Testing performed to determine whether the system meets acceptance criteria
bottom-up integration
cyclomatic complexity
acceptance testing
waterfall model benefits
30. Special-purpose software used to simulate a component called by the component under test
horizontal traceability
experience-based techniques
stub
cause-effect graphic testing
31. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
COTS
waterfall model benefits
failure rate
waterfall model phases
32. White-box design technique used to design test cases for a software component using LCSAJ.
interoperability
test log uses
risk-based testing
LCSAJ testing
33. Record details of test cases executed Record order of execution record results
SW development model
test log uses
black-box testing
equivalence partitions
34. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
coverage measurement tools
contract acceptance testing
stub
35. A document that provides the structure for writing test cases.
maintainability testing
Incidents
IEEE test case specification template
condition coverage
36. A functional testing approach in which test cases are designed based on business processes.
business process-based testing
defect density
input specifications
driver
37. Component - Integration - System - Acceptance
decision table testing
alpha testing
Incidents
test levels
38. Requirements that determine the functionality of a software system.
functional requirements
test data preparation tools
fault attack
test analysis & design tasks
39. Events that occurred during the testing process our investigation.
test data preparation tools
Incidents
dynamic analysis tools
data-driven testing
40. Actual inputs required to execute a test case
incremental testing
driver
debugging tools
input specifications
41. Specific groups that represent a set of valid or invalid partitions for input conditions.
action
equivalence partitions
horizontal traceability
anomalous events
42. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
Impact subheadings
acceptance testing
instrumentation
43. Testing software in its operational environment
instrumentation
decision table
load testing
operational testing
44. A table showing combinations of inputs and their associated actions.
test data preparation tools
alpha testing
test tool deployment Success Factors
decision table
45. Black-box test design technique - test cases are designed from a decision table.
integration management tools
cyclomatic complexity
condition determination coverage
decision table testing
46. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
incident report identifier
documentation tools
horizontal traceability
contract acceptance testing
47. 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 flow structure
test log uses
error
waterfall model benefits
48. 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
impact
test data preparation tools
test control Tasks
maintenance testing
49. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
functional testing tool
experience-based techniques
test tool deployment Success Factors
agile software development model
50. Sequence in which instructions are executed through a component or system
control flow structure
Impact subheadings
equivalence partitions
cyclomatic complexity