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. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintenance testing
iterative-incremental development models
maintainability testing
maintainability
2. Sequence in which data items are accessed or modified by code.
risk-based testing
big-bang testing
data flow structure
component testing
3. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
integration management tools
impact
exit criteria
conditions
4. 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.
inspection
action
incident description subheadings
incident report identifier
5. Testing software in its operational environment
functional testing
equivalence partitions
operational testing
IEEE incident report template
6. A review not based on a formal documented procedure
maintainability testing
incident report identifier
conditions
informal review
7. An analysis that determines the portion of code on software executed by a set of test cases
environmental needs
code coverage
error guessing
operational testing
8. A table showing combinations of inputs and their associated actions.
dynamic analysis tools
decision table
experience-based techniques
configuration management tools
9. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations
SW development model
agile software development model
debugging
failure rate
10. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
test tool deployment Success Factors
driver
accuracy
waterfall model phases
11. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
waterfall model phases
integration management tools
entry criteria
test analysis & design tasks
12. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
multiple condition coverage
incident description subheadings
driver
data-driven testing
13. Process used to create a SW product from initial conception to public release
test levels
SW development model
acceptance testing
big-bang testing
14. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
boundary value analysis
incremental testing
failure rate
component integration testing
15. Used to replace a component that calls another component.
driver
impact
condition coverage
test execution tasks
16. A component of the incident report that determines the actual effect of the incident on the software and its users.
maintenance testing
testing process phases
impact
test planning Tasks
17. 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.
functional requirements
IEEE test case specification template
bottom-up integration
coverage measurement tools
18. The capability of a software product to provide agreed and correct output with the required degree of precision
incident management tools
alpha testing
iterative-incremental development models
accuracy
19. Ability of software to provide appropriate performance relative to amount of resources used.
defect
efficiency
inspection
decision table testing
20. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
conditions
decision testing
Incidents
functional testing
21. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
decision coverage
action
test data preparation tools
22. 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
error guessing
waterfall model benefits
coverage measurement tools
functional testing tool
23. Component - Integration - System - Acceptance
waterfall model phases
test tool deployment Success Factors
component testing
test levels
24. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
SW development model
conformance testing tools
coverage measurement tools
test execution tasks
25. Components are combined and tested in the order in which basic functionalities start working
input specifications
coverage
functional incremental integration
ad hoc integration
26. 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
anomalous events
configuration management tools
incremental testing
test planning Tasks
27. Tools used by developers to identify defects in programs.
debugging
independence of testing
debugging tools
data flow structure
28. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
component integration testing
risk-based testing
incident management tools
condition coverage
29. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
defect
horizontal traceability
cyclomatic complexity
multiple condition coverage
30. Examine changes made to an operational system cause defects.
actual result
maintenance testing
debugging tools
configuration management
31. Operational testing performed at an _external_ site without involvement of the developing organization.
iterative-incremental development models
incident life cycle phases
error
beta testing
32. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
data-driven testing
fault attack
functional testing tool
33. A unique identifier for each incident report generated during test execution.
functional incremental integration
integration management tools
test planning Tasks
incident report identifier
34. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
actual result
test implementation tasks
backbone integration
maintainability
35. Increased load (transations) used to test behavior of system under high volume.
driver
debugging tools
load testing
resolution types
36. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
impact analysis
integration
iterative-incremental development models
documentation tools
37. A document that records the description of each event that occurs during the testing process and that requires further investigation
Impact subheadings
incident report
defect
functional incremental integration
38. Requirements that determine the functionality of a software system.
functional requirements
coverage
impact
bottom-up integration
39. Linear Code Sequence and Jump.
component testing
maintenance testing
LCSAJ
anomalous events
40. 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
waterfall model benefits
iterative-incremental development models
test data preparation tools
decision testing
41. Tools used to store and manage incidents return phone defects failures or anomalies.
component integration testing
actual result
incident management tools
incident report
42. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
coverage
condition coverage
acceptance testing
test control Tasks
43. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test control Tasks
functional testing tool
equivalence partitioning
incident life cycle phases
44. Software products or applications designed to automate manual testing tasks.
actual result
anomalous events
automation tools
defect density
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
environmental needs
integration management tools
exploratory testing
46. Testing performed to determine whether the system meets acceptance criteria
resolution types
interoperability testing
efficiency
acceptance testing
47. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incremental testing
informal review
horizontal traceability
control flow structure
48. An event or item that can be tested using one or more test cases
test condition
incremental testing
interoperability testing
accuracy
49. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
configuration management
SW development model
backbone integration
50. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
functional testing
monitor
agile software development model
failure rate