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. Based on analysis of functional specifications of a system.
functional testing
COTS
driver
incident report
2. Testing software in its operational environment
integration testing
debugging tools
interoperability testing
operational testing
3. Events that occurred during the testing process our investigation.
test management tool features
equivalence partitions
incident description subheadings
Incidents
4. Requirements that determine the functionality of a software system.
test planning Tasks
exit criteria
functional requirements
coverage measurement tools
5. Examine changes made to an operational system cause defects.
incident management tools
maintenance testing
code coverage
condition determination coverage
6. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
boundary value analysis
component testing
exploratory testing
test control Tasks
7. Special-purpose software used to simulate a component that calls the component under test
stub
driver
test control Tasks
cyclomatic complexity
8. A document that records the description of each event that occurs during the testing process and that requires further investigation
multiple condition coverage
testing process phases
Three main SW development models
incident report
9. A unique identifier for each incident report generated during test execution.
functionality
incident report identifier
monitor
beta testing
10. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
automation tools
component integration testing
beta testing
backbone integration
11. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
documentation tools
impact
maintainability testing
accuracy
12. 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).
test implementation tasks
big-bang testing
condition coverage
configuration management tools
13. Measures amount of testing performed by a collection of test cases
accuracy
Impact subheadings
nonfunctional requirements
coverage
14. Calculates the number of executed branch outcomes in code.
Incidents
decision coverage
acceptance criteria
IEEE test case specification template
15. Special-purpose software used to simulate a component called by the component under test
condition determination coverage
stub
driver
conditions
16. Incident Report - Identifier - Summary - Incident - Description - Impact
risk-based testing
defect
IEEE incident report template
impact
17. Tools used to identify and calculate coverage items in program code.
waterfall model phases
coverage measurement tools
interoperability testing
horizontal traceability
18. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
functional testing tool
beta testing
condition coverage
documentation tools
19. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
monitor
contract acceptance testing
condition coverage
Incidents
20. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
informal review
input specifications
cyclomatic complexity
inspection
21. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
incident report identifier
test planning Tasks
IEEE incident report template
test execution tasks
22. Used to replace a component that calls another component.
test levels
black-box testing
LCSAJ testing
driver
23. Sequence in which instructions are executed through a component or system
driver
control flow structure
decision table
beta testing
24. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
Three main SW development models
interoperability
functionality
defect masking
25. Testing an integrated system to validate it meets requirements
test management tool features
system testing
instrumentation
waterfall model benefits
26. 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
alpha testing
waterfall model benefits
entry criteria
IEEE test case specification template
27. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
component
test levels
entry criteria
incident description subheadings
28. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
decision coverage
environmental needs
keyword-driven testing
acceptance criteria
29. A document that provides the structure for writing test cases.
debugging
condition coverage
condition determination coverage
IEEE test case specification template
30. 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
error
independence of testing
test log uses
test planning Tasks
31. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
test implementation tasks
maintainability testing
decision table
cause-effect graphic testing
32. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
integration
fault attack
contract acceptance testing
inspection
33. A review not based on a formal documented procedure
coverage measurement tools
informal review
component testing
test data preparation tools
34. Conditions required to begin testing activities.
entry criteria
acceptance testing
SW development model
functional incremental integration
35. An event or item that can be tested using one or more test cases
interoperability testing
test condition
test management tool features
testing process phases
36. Insertion of additional code in the existing program in order to count coverage items.
waterfall model phases
instrumentation
test planning Tasks
exit criteria
37. Actual inputs required to execute a test case
testing process phases
code coverage
contract acceptance testing
input specifications
38. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
informal review
interoperability
exhaustive testing
39. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
test tool deployment Success Factors
incident life cycle phases
Impact subheadings
big-bang testing
40. The smallest software item that can be tested in isolation.
efficiency
component
LCSAJ testing
incident report identifier
41. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
coverage measurement tools
LCSAJ testing
decision testing
waterfall model phases
42. 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
incident life cycle phases
incident description subheadings
risk-based testing
43. Waterfall iterative-incremental "V"
exploratory testing
functional incremental integration
Three main SW development models
test management tool features
44. Record details of test cases executed Record order of execution record results
component
test log uses
conformance testing tools
condition coverage
45. Sequence in which data items are accessed or modified by code.
contract acceptance testing
equivalence partitioning
cyclomatic complexity
data flow structure
46. A component of the incident report that determines the actual effect of the incident on the software and its users.
decision table testing
component testing
action
impact
47. Develop & proiroitize test cases Create groups of test cases Set up test environment
business process-based testing
actual result
iterative-incremental development models
test implementation tasks
48. Allows storage of test input and expected results in one or more central data sources or databases.
coverage measurement tools
stub
exhaustive testing
data-driven testing
49. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
maintainability testing
COTS
debugging tools
coverage measurement tools
50. Find defects in code while the software application being tested is running.
test levels
defect density
nonfunctional requirements
dynamic analysis tools