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. Testing software in its operational environment
ad hoc integration
operational testing
incident management tools
conformance testing tools
2. 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
risk-based testing
LCSAJ testing
agile software development model
code coverage
3. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
impact analysis
independence of testing
documentation tools
COTS
4. Testing software components that are separately testable. Also module program and unit testing.
ad hoc integration
test execution tasks
component testing
defect density
5. Special-purpose software used to simulate a component called by the component under test
test data preparation tools
functional incremental integration
stub
driver
6. White-box design technique used to design test cases for a software component using LCSAJ.
exploratory testing
defect masking
LCSAJ testing
debugging tools
7. Response of the application to an input
incremental testing
action
test condition
alpha testing
8. 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.
action
test implementation tasks
bottom-up integration
incident description subheadings
9. Informal testing technique in which test planning and execution run in parallel
cause-effect graphic testing
integration
efficiency
exploratory testing
10. Based on analysis of functional specifications of a system.
control flow structure
coverage measurement tools
acceptance criteria
functional testing
11. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
bottom-up integration
black-box testing
decision coverage
12. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
coverage measurement tools
action
maintainability testing
iterative-incremental development models
13. The process of finding analyzing and removing causes of failure in a software product.
debugging
contract acceptance testing
iterative-incremental development models
decision table testing
14. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
cyclomatic complexity
waterfall model benefits
configuration management tools
15. Special additions or changes to the environment required to run a test case.
decision table
maintainability testing
driver
environmental needs
16. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
condition coverage
decision table testing
functionality
entry criteria
17. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
exhaustive testing
decision testing
error guessing
multiple condition coverage
18. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
ad hoc integration
contract acceptance testing
agile software development model
19. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
interoperability testing
maintainability testing
contract acceptance testing
incident report
20. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
impact analysis
IEEE incident report template
functional requirements
testing process phases
21. An event or item that can be tested using one or more test cases
test condition
debugging tools
IEEE test case specification template
incident report identifier
22. Examine changes made to an operational system cause defects.
Three main SW development models
maintenance testing
iterative-incremental development models
maintainability
23. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
decision table
coverage measurement tools
nonfunctional requirements
defect
24. Behavior or response of a software application that you observe when you execute the action steps in the test case.
incident life cycle phases
test management tool features
actual result
interoperability
25. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
inspection
interoperability
interoperability testing
26. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
exhaustive testing
incident life cycle phases
black-box testing
27. Used to replace a component that calls another component.
conditions
impact
driver
configuration management tools
28. Increased load (transations) used to test behavior of system under high volume.
alpha testing
load testing
fault attack
data-driven testing
29. A review not based on a formal documented procedure
informal review
horizontal traceability
waterfall model benefits
condition determination coverage
30. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
alpha testing
test condition
incident life cycle phases
interoperability testing
31. Separation of testing responsibilities which encourages the accomplishment of objective testing
incident description subheadings
independence of testing
experience-based techniques
LCSAJ
32. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
test data preparation tools
waterfall model phases
equivalence partitioning
33. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
component
test analysis & design tasks
test execution tasks
accuracy
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
maintainability
equivalence partitions
waterfall model benefits
informal review
35. Measures amount of testing performed by a collection of test cases
coverage
conditions
component testing
stub
36. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
test execution tasks
Incidents
alpha testing
driver
37. Severity - Priority
experience-based techniques
Impact subheadings
defect masking
keyword-driven testing
38. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test execution tasks
maintenance testing
data flow structure
test management tool features
39. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
test levels
impact
interoperability testing
decision testing
40. Occurrences that happen before and after an unexpected event
anomalous events
multiple condition coverage
SW development model
equivalence partitioning
41. 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
incident description subheadings
Three main SW development models
coverage
42. Linear Code Sequence and Jump.
maintenance testing
error
LCSAJ
resolution types
43. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
test control Tasks
automation tools
driver
conformance testing tools
44. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
integration testing
incremental testing
maintenance testing
business process-based testing
45. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
integration management tools
waterfall model benefits
integration testing
46. Tools used by developers to identify defects in programs.
accuracy
input specifications
test planning Tasks
debugging tools
47. Sequence in which data items are accessed or modified by code.
decision testing
data flow structure
fault attack
exhaustive testing
48. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
accuracy
interoperability
defect density
error guessing
49. Waterfall iterative-incremental "V"
error
experience-based techniques
Three main SW development models
keyword-driven testing
50. 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
experience-based techniques
test planning Tasks
error
incident report identifier