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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
exit criteria
condition coverage
equivalence partitioning
interoperability testing
2. A task of maintaining and controlling changes to all entities of a system.
ad hoc integration
integration management tools
configuration management
component testing
3. Special additions or changes to the environment required to run a test case.
IEEE incident report template
environmental needs
operational testing
independence of testing
4. Behavior or response of a software application that you observe when you execute the action steps in the test case.
incident report identifier
operational testing
waterfall model benefits
actual result
5. White-box design technique used to design test cases for a software component using LCSAJ.
entry criteria
nonfunctional requirements
SW development model
LCSAJ testing
6. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
IEEE incident report template
waterfall model benefits
LCSAJ
maintainability
7. Black-box test design technique - test cases are designed from a decision table.
ad hoc integration
code coverage
iterative-incremental development models
decision table testing
8. Actual inputs required to execute a test case
decision testing
input specifications
exit criteria
cause-effect graphic testing
9. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons
functional requirements
component integration testing
defect
test tool deployment Success Factors
10. All possible combinations of input values and preconditions are tested.
driver
test tool deployment Success Factors
coverage
exhaustive testing
11. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
configuration management tools
conformance testing tools
monitor
control flow structure
12. Develop & proiroitize test cases Create groups of test cases Set up test environment
risk-based testing
condition coverage
test implementation tasks
equivalence partitioning
13. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).
condition coverage
Impact subheadings
configuration management
configuration management tools
14. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
test management tool features
operational testing
condition determination coverage
15. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
test control Tasks
risk-based testing
operational testing
functional requirements
16. 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
Incidents
COTS
agile software development model
test log uses
17. Events that occurred during the testing process our investigation.
Incidents
backbone integration
driver
condition coverage
18. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
incident management tools
environmental needs
LCSAJ
19. Find defects in code while the software application being tested is running.
configuration management
configuration management tools
Incidents
dynamic analysis tools
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.
decision testing
condition coverage
cause-effect graphic testing
SW development model
21. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
dynamic analysis tools
debugging
exploratory testing
22. Integrate different kinds of tools to make test management more efficient and simple.
incident description subheadings
integration management tools
test log uses
maintainability
23. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
decision table testing
exit criteria
cyclomatic complexity
24. The capability of a software product to provide agreed and correct output with the required degree of precision
test management tool features
accuracy
coverage measurement tools
debugging
25. Component - Integration - System - Acceptance
monitor
test planning Tasks
test levels
Incidents
26. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
data-driven testing
control flow structure
maintenance testing
27. One defect prevents the detection of another.
cyclomatic complexity
defect masking
equivalence partitions
conditions
28. Record details of test cases executed Record order of execution record results
fault attack
test implementation tasks
test log uses
equivalence partitions
29. Used to test the functionality of software as mentioned in software requirement specifications.
error
functional testing tool
test analysis & design tasks
incremental testing
30. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
informal review
integration
interoperability
integration management tools
31. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
maintenance testing
ad hoc integration
documentation tools
input specifications
32. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
entry criteria
decision table
component testing
33. Human action that generates an incorrect result.
error
LCSAJ
monitor
alpha testing
34. Requirements that determine the functionality of a software system.
horizontal traceability
incident report
interoperability
functional requirements
35. 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 data preparation tools
integration
entry criteria
test management tool features
36. Special-purpose software used to simulate a component called by the component under test
maintainability
stub
integration management tools
waterfall model benefits
37. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
decision testing
waterfall model phases
cause-effect graphic testing
actual result
38. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
horizontal traceability
maintenance testing
condition coverage
ad hoc integration
39. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
LCSAJ testing
code coverage
component integration testing
big-bang testing
40. 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
test analysis & design tasks
test planning Tasks
instrumentation
boundary value analysis
41. 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
configuration management
incremental testing
test implementation tasks
42. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
control flow structure
IEEE test case specification template
test implementation tasks
43. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
impact
boundary value analysis
experience-based techniques
decision coverage
44. Process used to create a SW product from initial conception to public release
interoperability
integration
test management tool features
SW development model
45. Insertion of additional code in the existing program in order to count coverage items.
black-box testing
instrumentation
boundary value analysis
defect density
46. Severity - Priority
stub
Impact subheadings
configuration management
exhaustive testing
47. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
component integration testing
test tool deployment Success Factors
actual result
alpha testing
48. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
test analysis & design tasks
ad hoc integration
dynamic analysis tools
failure rate
49. A component of the incident report that determines the actual effect of the incident on the software and its users.
decision table
impact
driver
data flow structure
50. Ability of software to provide appropriate performance relative to amount of resources used.
driver
condition coverage
efficiency
independence of testing