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. Conditions required to begin testing activities.
environmental needs
entry criteria
integration management tools
defect density
2. 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.
backbone integration
operational testing
bottom-up integration
input specifications
3. Testing software in its operational environment
testing process phases
operational testing
nonfunctional requirements
dynamic analysis tools
4. Tools used to store and manage incidents return phone defects failures or anomalies.
Impact subheadings
test execution tasks
testing process phases
incident management tools
5. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
test execution tasks
equivalence partitioning
incident life cycle phases
6. Events that occurred during the testing process our investigation.
Incidents
functional requirements
testing process phases
entry criteria
7. Used to test the functionality of software as mentioned in software requirement specifications.
bottom-up integration
functional testing tool
debugging tools
failure rate
8. 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.
test condition
test execution tasks
inspection
beta testing
9. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
debugging tools
debugging
equivalence partitions
10. Testing an integrated system to validate it meets requirements
debugging
system testing
IEEE incident report template
incident life cycle phases
11. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
decision coverage
configuration management tools
resolution types
incident description subheadings
12. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
defect
testing process phases
stub
operational testing
13. Based on analysis of functional specifications of a system.
input specifications
decision table testing
environmental needs
functional testing
14. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
iterative-incremental development models
test tool deployment Success Factors
test levels
15. 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
interoperability
input specifications
agile software development model
impact
16. 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
test implementation tasks
test data preparation tools
dynamic analysis tools
control flow structure
17. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
accuracy
control flow structure
error guessing
agile software development model
18. Sequence in which data items are accessed or modified by code.
informal review
data flow structure
failure rate
component testing
19. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
anomalous events
functional incremental integration
COTS
impact analysis
20. Develop & proiroitize test cases Create groups of test cases Set up test environment
configuration management tools
test control Tasks
test implementation tasks
waterfall model phases
21. A document that provides the structure for writing test cases.
IEEE test case specification template
boundary value analysis
test implementation tasks
waterfall model benefits
22. A document that records the description of each event that occurs during the testing process and that requires further investigation
conditions
risk-based testing
defect density
incident report
23. Testing performed to determine whether the system meets acceptance criteria
nonfunctional requirements
incident management tools
acceptance testing
system testing
24. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
monitor
functional requirements
incident report
conformance testing tools
25. Deviation of a software system from its expected delivery services or results
failure
actual result
IEEE test case specification template
iterative-incremental development models
26. Examine changes made to an operational system cause defects.
maintenance testing
decision table
waterfall model benefits
component integration testing
27. Linear Code Sequence and Jump.
control flow structure
LCSAJ
contract acceptance testing
coverage measurement tools
28. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
black-box testing
cause-effect graphic testing
exploratory testing
IEEE test case specification template
29. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
Three main SW development models
horizontal traceability
big-bang testing
black-box testing
30. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
alpha testing
defect density
exit criteria
incremental testing
31. All possible combinations of input values and preconditions are tested.
exhaustive testing
exploratory testing
iterative-incremental development models
instrumentation
32. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
LCSAJ testing
documentation tools
waterfall model phases
defect density
33. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
failure rate
defect density
contract acceptance testing
data-driven testing
34. Increased load (transations) used to test behavior of system under high volume.
multiple condition coverage
control flow structure
conformance testing tools
load testing
35. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
configuration management tools
experience-based techniques
incident life cycle phases
acceptance testing
36. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
acceptance criteria
accuracy
resolution types
37. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
decision coverage
testing process phases
nonfunctional requirements
driver
38. A unique identifier for each incident report generated during test execution.
conformance testing tools
functional requirements
IEEE test case specification template
incident report identifier
39. One defect prevents the detection of another.
functionality
maintainability testing
defect masking
incident management tools
40. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
condition coverage
risk-based testing
component integration testing
interoperability
41. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test analysis & design tasks
entry criteria
functional testing tool
COTS
42. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
cause-effect graphic testing
automation tools
error guessing
43. The capability of a software product to provide agreed and correct output with the required degree of precision
boundary value analysis
Three main SW development models
accuracy
component testing
44. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
cyclomatic complexity
test control Tasks
functionality
interoperability testing
45. Tools used to identify and calculate coverage items in program code.
data-driven testing
decision table testing
coverage measurement tools
functional requirements
46. A component of the incident report that determines the actual effect of the incident on the software and its users.
test control Tasks
multiple condition coverage
decision table
impact
47. Components are combined and tested in the order in which basic functionalities start working
action
Incidents
interoperability testing
functional incremental integration
48. An event or item that can be tested using one or more test cases
impact analysis
test condition
maintenance testing
LCSAJ testing
49. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
equivalence partitions
incident report identifier
waterfall model phases
LCSAJ
50. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
driver
test management tool features
maintainability
Impact subheadings