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. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
maintainability testing
cyclomatic complexity
Impact subheadings
2. Conditions required to begin testing activities.
environmental needs
maintainability
Three main SW development models
entry criteria
3. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
environmental needs
functional requirements
defect
Incidents
4. Linear Code Sequence and Jump.
condition determination coverage
control flow structure
test tool deployment Success Factors
LCSAJ
5. 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
functional incremental integration
test levels
actual result
6. Severity - Priority
configuration management
agile software development model
horizontal traceability
Impact subheadings
7. Events that occurred during the testing process our investigation.
Incidents
load testing
integration
configuration management tools
8. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
error
conditions
test analysis & design tasks
resolution types
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
LCSAJ
agile software development model
acceptance testing
bottom-up integration
10. A document that records the description of each event that occurs during the testing process and that requires further investigation
ad hoc integration
driver
bottom-up integration
incident report
11. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
test planning Tasks
load testing
maintainability testing
LCSAJ testing
12. A unique identifier for each incident report generated during test execution.
configuration management tools
integration
incident report identifier
test log uses
13. 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
impact
decision testing
iterative-incremental development models
14. Ability of software to provide appropriate performance relative to amount of resources used.
horizontal traceability
decision coverage
efficiency
exhaustive testing
15. Informal testing technique in which test planning and execution run in parallel
driver
functionality
condition determination coverage
exploratory testing
16. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
decision testing
maintenance testing
data flow structure
driver
17. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
alpha testing
test planning Tasks
decision testing
18. The ratio between the number of defects found and the size of the component/system tested.
incident life cycle phases
contract acceptance testing
defect density
instrumentation
19. 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
acceptance criteria
incident management tools
Incidents
20. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
functional incremental integration
LCSAJ testing
incident description subheadings
test data preparation tools
21. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
fault attack
black-box testing
independence of testing
22. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
operational testing
action
inspection
23. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
incident life cycle phases
cause-effect graphic testing
risk-based testing
24. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
inspection
horizontal traceability
environmental needs
debugging tools
25. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
condition determination coverage
component integration testing
exhaustive testing
action
26. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
decision table
impact analysis
keyword-driven testing
27. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
testing process phases
waterfall model phases
risk-based testing
condition determination coverage
28. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
black-box testing
waterfall model phases
error guessing
impact analysis
29. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
test tool deployment Success Factors
cyclomatic complexity
incident life cycle phases
30. Find defects in code while the software application being tested is running.
dynamic analysis tools
fault attack
test execution tasks
test analysis & design tasks
31. Examine changes made to an operational system cause defects.
test data preparation tools
COTS
SW development model
maintenance testing
32. Process used to create a SW product from initial conception to public release
acceptance testing
conformance testing tools
SW development model
IEEE incident report template
33. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
integration testing
multiple condition coverage
experience-based techniques
driver
34. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
nonfunctional requirements
risk-based testing
impact
35. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
maintainability testing
action
debugging tools
36. Based on analysis of functional specifications of a system.
boundary value analysis
monitor
functional testing
control flow structure
37. Black-box testing technique used to create groups of input conditions that create the same kind of output.
defect density
equivalence partitioning
waterfall model benefits
operational testing
38. Human action that generates an incorrect result.
defect density
exit criteria
error
code coverage
39. One defect prevents the detection of another.
failure rate
defect masking
coverage measurement tools
informal review
40. Occurrences that happen before and after an unexpected event
test log uses
impact
anomalous events
contract acceptance testing
41. Used to test the functionality of software as mentioned in software requirement specifications.
code coverage
integration
resolution types
functional testing tool
42. Insertion of additional code in the existing program in order to count coverage items.
decision testing
instrumentation
operational testing
waterfall model phases
43. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
driver
alpha testing
ad hoc integration
acceptance criteria
44. A technique used to improve testing coverage by deliberately introducing faults in code.
decision coverage
equivalence partitions
fault attack
multiple condition coverage
45. 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
bottom-up integration
functional requirements
waterfall model benefits
incident report identifier
46. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
functional incremental integration
automation tools
testing process phases
test log uses
47. The capability of a software product to provide agreed and correct output with the required degree of precision
interoperability
accuracy
efficiency
driver
48. Specific groups that represent a set of valid or invalid partitions for input conditions.
equivalence partitions
iterative-incremental development models
instrumentation
contract acceptance testing
49. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
test analysis & design tasks
defect density
testing process phases
50. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
black-box testing
IEEE test case specification template
accuracy
business process-based testing