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. The ratio between the number of defects found and the size of the component/system tested.
actual result
integration
test condition
defect density
2. Waterfall iterative-incremental "V"
impact
bottom-up integration
LCSAJ testing
Three main SW development models
3. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
test data preparation tools
COTS
iterative-incremental development models
impact analysis
4. Deviation of a software system from its expected delivery services or results
coverage
failure
integration management tools
control flow structure
5. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
action
test log uses
test management tool features
component
6. A document that records the description of each event that occurs during the testing process and that requires further investigation
business process-based testing
incident report
interoperability
Incidents
7. Testing software components that are separately testable. Also module program and unit testing.
exploratory testing
component testing
Impact subheadings
documentation tools
8. Informal testing technique in which test planning and execution run in parallel
incident report
exploratory testing
functionality
risk-based testing
9. Calculates the number of executed branch outcomes in code.
decision coverage
big-bang testing
decision testing
control flow structure
10. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
data-driven testing
functional requirements
incident description subheadings
resolution types
11. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
configuration management
beta testing
alpha testing
functionality
12. One defect prevents the detection of another.
test implementation tasks
exploratory testing
defect masking
entry criteria
13. Severity - Priority
data-driven testing
Impact subheadings
exploratory testing
debugging
14. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
COTS
bottom-up integration
data-driven testing
15. The process of finding analyzing and removing causes of failure in a software product.
impact
impact analysis
test planning Tasks
debugging
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
waterfall model benefits
integration management tools
horizontal traceability
maintainability
17. The capability of a software product to provide agreed and correct output with the required degree of precision
stub
Impact subheadings
interoperability
accuracy
18. A document that provides the structure for writing test cases.
alpha testing
business process-based testing
maintainability
IEEE test case specification template
19. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
contract acceptance testing
test log uses
business process-based testing
iterative-incremental development models
20. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
decision table testing
test condition
test tool deployment Success Factors
21. Testing performed to determine whether the system meets acceptance criteria
equivalence partitioning
incremental testing
documentation tools
acceptance testing
22. Tests interfaces between components and between integrated components and systems.
integration testing
condition coverage
debugging
interoperability testing
23. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
control flow structure
LCSAJ testing
interoperability
maintainability
24. Special-purpose software used to simulate a component that calls the component under test
fault attack
component integration testing
SW development model
driver
25. Combining components or sytems into larger structural units or subsystems.
integration
bottom-up integration
test levels
alpha testing
26. A functional testing approach in which test cases are designed based on business processes.
test log uses
business process-based testing
failure
accuracy
27. Tools used to identify and calculate coverage items in program code.
cyclomatic complexity
test condition
coverage measurement tools
functional requirements
28. A task of maintaining and controlling changes to all entities of a system.
configuration management
defect masking
data-driven testing
test control Tasks
29. The smallest software item that can be tested in isolation.
component
stub
interoperability
maintainability
30. 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
decision coverage
test tool deployment Success Factors
business process-based testing
conformance testing tools
31. Response of the application to an input
cause-effect graphic testing
decision coverage
action
test data preparation tools
32. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
incident life cycle phases
environmental needs
control flow structure
action
33. 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.
acceptance criteria
test tool deployment Success Factors
inspection
beta testing
34. Special additions or changes to the environment required to run a test case.
maintainability testing
environmental needs
IEEE incident report template
entry criteria
35. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
test management tool features
maintainability
instrumentation
36. Events that occurred during the testing process our investigation.
SW development model
Incidents
test levels
acceptance testing
37. Component - Integration - System - Acceptance
boundary value analysis
LCSAJ
test levels
acceptance testing
38. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
incremental testing
maintainability
anomalous events
condition coverage
39. Record details of test cases executed Record order of execution record results
test implementation tasks
test log uses
operational testing
data-driven testing
40. Actual inputs required to execute a test case
test tool deployment Success Factors
multiple condition coverage
input specifications
decision testing
41. Develop & proiroitize test cases Create groups of test cases Set up test environment
documentation tools
bottom-up integration
alpha testing
test implementation tasks
42. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
entry criteria
test analysis & design tasks
efficiency
43. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
cyclomatic complexity
LCSAJ testing
actual result
exploratory testing
44. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test analysis & design tasks
conformance testing tools
actual result
keyword-driven testing
45. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
input specifications
horizontal traceability
coverage
46. Allows storage of test input and expected results in one or more central data sources or databases.
maintainability
boundary value analysis
data-driven testing
error
47. Measures amount of testing performed by a collection of test cases
exit criteria
coverage
functional testing
data-driven testing
48. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
decision table testing
fault attack
maintenance testing
49. 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).
configuration management tools
LCSAJ
beta testing
test analysis & design tasks
50. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
decision table testing
action
failure rate
Incidents