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. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
functional testing
entry criteria
integration testing
test analysis & design tasks
2. Special additions or changes to the environment required to run a test case.
test levels
system testing
environmental needs
accuracy
3. Sequence in which data items are accessed or modified by code.
defect density
incident life cycle phases
condition coverage
data flow structure
4. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
functional incremental integration
informal review
nonfunctional requirements
component integration testing
5. Tools used to identify and calculate coverage items in program code.
conformance testing tools
exit criteria
coverage measurement tools
decision coverage
6. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
interoperability testing
resolution types
integration
7. Response of the application to an input
agile software development model
condition determination coverage
action
independence of testing
8. Insertion of additional code in the existing program in order to count coverage items.
IEEE test case specification template
integration management tools
failure rate
instrumentation
9. All possible combinations of input values and preconditions are tested.
experience-based techniques
agile software development model
integration management tools
exhaustive testing
10. Components are combined and tested in the order in which basic functionalities start working
data flow structure
test log uses
horizontal traceability
functional incremental integration
11. 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
waterfall model phases
LCSAJ testing
independence of testing
12. Waterfall iterative-incremental "V"
functional testing tool
Three main SW development models
failure
incident description subheadings
13. Based on analysis of functional specifications of a system.
exit criteria
interoperability
functional testing
test execution tasks
14. Testing an integrated system to validate it meets requirements
system testing
acceptance testing
risk-based testing
big-bang testing
15. Informal testing technique in which test planning and execution run in parallel
exploratory testing
configuration management
component
big-bang testing
16. Special-purpose software used to simulate a component that calls the component under test
coverage
error guessing
driver
fault attack
17. 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
horizontal traceability
conditions
maintenance testing
18. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
error
test control Tasks
condition coverage
19. A table showing combinations of inputs and their associated actions.
incident report identifier
automation tools
nonfunctional requirements
decision table
20. Occurrences that happen before and after an unexpected event
test planning Tasks
load testing
agile software development model
anomalous events
21. Actual inputs required to execute a test case
backbone integration
code coverage
coverage measurement tools
input specifications
22. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
incident description subheadings
fault attack
efficiency
error guessing
23. 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
Impact subheadings
test tool deployment Success Factors
incident life cycle phases
testing process phases
24. Specific groups that represent a set of valid or invalid partitions for input conditions.
black-box testing
operational testing
equivalence partitions
incident report identifier
25. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
system testing
data-driven testing
accuracy
26. Software products or applications designed to automate manual testing tasks.
decision testing
automation tools
waterfall model benefits
decision table
27. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
decision table testing
incremental testing
instrumentation
28. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
component integration testing
horizontal traceability
test control Tasks
impact
29. Severity - Priority
test condition
boundary value analysis
Impact subheadings
test implementation tasks
30. Examine changes made to an operational system cause defects.
acceptance testing
configuration management
maintenance testing
action
31. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
data flow structure
incident description subheadings
automation tools
resolution types
32. Black-box testing technique used to create groups of input conditions that create the same kind of output.
boundary value analysis
data flow structure
equivalence partitioning
instrumentation
33. Increased load (transations) used to test behavior of system under high volume.
data-driven testing
load testing
waterfall model phases
keyword-driven testing
34. 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
conformance testing tools
waterfall model benefits
risk-based testing
agile software development model
35. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
interoperability
error
efficiency
decision testing
36. Deviation of a software system from its expected delivery services or results
defect density
failure
bottom-up integration
anomalous events
37. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
stub
horizontal traceability
functional testing tool
38. The process of finding analyzing and removing causes of failure in a software product.
resolution types
test execution tasks
test analysis & design tasks
debugging
39. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
condition coverage
configuration management tools
Three main SW development models
40. An event or item that can be tested using one or more test cases
test condition
waterfall model phases
test data preparation tools
COTS
41. Incident Report - Identifier - Summary - Incident - Description - Impact
maintainability testing
IEEE incident report template
test log uses
decision table testing
42. Human action that generates an incorrect result.
equivalence partitioning
interoperability testing
error
inspection
43. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
business process-based testing
contract acceptance testing
iterative-incremental development models
44. Calculates the number of executed branch outcomes in code.
multiple condition coverage
test tool deployment Success Factors
Three main SW development models
decision coverage
45. A document that records the description of each event that occurs during the testing process and that requires further investigation
exploratory testing
documentation tools
automation tools
incident report
46. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
incremental testing
exit criteria
IEEE incident report template
driver
47. A set of conditions that a system needs to meet in order to be accepted by end users
incremental testing
acceptance criteria
incident life cycle phases
multiple condition coverage
48. Behavior or response of a software application that you observe when you execute the action steps in the test case.
LCSAJ
integration management tools
actual result
action
49. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
functional incremental integration
waterfall model benefits
incident report identifier
cause-effect graphic testing
50. 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
LCSAJ
test data preparation tools
failure rate
decision testing