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
integration testing
actual result
independence of testing
coverage measurement tools
2. Increased load (transations) used to test behavior of system under high volume.
exhaustive testing
cause-effect graphic testing
informal review
load testing
3. Ability of software to provide appropriate performance relative to amount of resources used.
entry criteria
integration
efficiency
incident life cycle phases
4. Occurrences that happen before and after an unexpected event
incremental testing
anomalous events
IEEE incident report template
failure
5. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
horizontal traceability
error guessing
black-box testing
6. Requirements that determine the functionality of a software system.
functional incremental integration
functional requirements
interoperability testing
component integration testing
7. The capability of a software product to provide agreed and correct output with the required degree of precision
SW development model
incremental testing
maintenance testing
accuracy
8. Special-purpose software used to simulate a component that calls the component under test
driver
integration management tools
coverage measurement tools
LCSAJ
9. Integration approach components or subsystems are combined all at once rather than in stages.
conformance testing tools
big-bang testing
integration testing
instrumentation
10. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
informal review
integration
defect
risk-based testing
11. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
driver
business process-based testing
configuration management tools
12. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
code coverage
incident report
alpha testing
waterfall model benefits
13. Waterfall iterative-incremental "V"
test log uses
risk-based testing
LCSAJ
Three main SW development models
14. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
incident description subheadings
condition determination coverage
error
15. Sequence in which instructions are executed through a component or system
impact analysis
informal review
dynamic analysis tools
control flow structure
16. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
testing process phases
test tool deployment Success Factors
impact analysis
control flow structure
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.
bottom-up integration
ad hoc integration
integration testing
test data preparation tools
18. 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
agile software development model
driver
input specifications
functional requirements
19. Black-box test design technique - test cases are designed from a decision table.
incident description subheadings
debugging tools
decision table testing
impact
20. Based on analysis of functional specifications of a system.
equivalence partitioning
ad hoc integration
functional testing
driver
21. Testing software components that are separately testable. Also module program and unit testing.
interoperability testing
component testing
incident report identifier
test planning Tasks
22. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
resolution types
cause-effect graphic testing
Impact subheadings
fault attack
23. Components are integrated in the order in which they are developed
ad hoc integration
incremental testing
maintainability
input specifications
24. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
agile software development model
stub
automation tools
condition determination coverage
25. Tests interfaces between components and between integrated components and systems.
component testing
IEEE test case specification template
test planning Tasks
integration testing
26. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
functional incremental integration
contract acceptance testing
horizontal traceability
integration management tools
27. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
IEEE incident report template
exploratory testing
test control Tasks
condition determination coverage
28. Testing performed to determine whether the system meets acceptance criteria
control flow structure
error guessing
acceptance testing
integration
29. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
acceptance criteria
automation tools
iterative-incremental development models
component
30. Linear Code Sequence and Jump.
maintainability testing
component
efficiency
LCSAJ
31. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
test levels
COTS
test tool deployment Success Factors
incremental testing
32. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
contract acceptance testing
incident life cycle phases
component integration testing
resolution types
33. Behavior or response of a software application that you observe when you execute the action steps in the test case.
incident management tools
test log uses
actual result
inspection
34. Components are combined and tested in the order in which basic functionalities start working
test control Tasks
anomalous events
waterfall model phases
functional incremental integration
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.
decision testing
condition coverage
incident report identifier
component testing
36. Insertion of additional code in the existing program in order to count coverage items.
automation tools
business process-based testing
Incidents
instrumentation
37. Actual inputs required to execute a test case
exit criteria
input specifications
driver
condition determination coverage
38. Measures amount of testing performed by a collection of test cases
impact analysis
incremental testing
coverage
equivalence partitions
39. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
risk-based testing
defect
decision table testing
test management tool features
40. Informal testing technique in which test planning and execution run in parallel
maintenance testing
exploratory testing
incident report
debugging
41. A document that provides the structure for writing test cases.
operational testing
maintainability testing
input specifications
IEEE test case specification template
42. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
maintainability testing
risk-based testing
incident description subheadings
exit criteria
43. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
multiple condition coverage
test analysis & design tasks
resolution types
code coverage
44. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
maintainability
test analysis & design tasks
acceptance criteria
45. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
Impact subheadings
contract acceptance testing
keyword-driven testing
condition determination coverage
46. Calculates the number of executed branch outcomes in code.
instrumentation
decision coverage
decision testing
Incidents
47. Black-box testing technique used to create groups of input conditions that create the same kind of output.
defect density
equivalence partitioning
component testing
beta testing
48. A unique identifier for each incident report generated during test execution.
exhaustive testing
load testing
incident report identifier
incident life cycle phases
49. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
component integration testing
environmental needs
functionality
conformance testing tools
50. Record details of test cases executed Record order of execution record results
efficiency
alpha testing
test log uses
nonfunctional requirements