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.
interoperability testing
test planning Tasks
horizontal traceability
input specifications
2. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
data flow structure
risk-based testing
monitor
test log uses
3. Tools used by developers to identify defects in programs.
stub
debugging tools
LCSAJ testing
coverage measurement tools
4. Testing performed to determine whether the system meets acceptance criteria
documentation tools
acceptance testing
component integration testing
decision coverage
5. Special-purpose software used to simulate a component that calls the component under test
component testing
driver
decision coverage
environmental needs
6. 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
documentation tools
instrumentation
big-bang testing
test tool deployment Success Factors
7. Ability of software to provide appropriate performance relative to amount of resources used.
incident life cycle phases
efficiency
contract acceptance testing
beta testing
8. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
backbone integration
iterative-incremental development models
condition determination coverage
waterfall model phases
9. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
debugging tools
nonfunctional requirements
coverage
environmental needs
10. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
functional requirements
alpha testing
operational testing
11. Tools used to identify and calculate coverage items in program code.
exit criteria
system testing
condition coverage
coverage measurement tools
12. Examine changes made to an operational system cause defects.
maintenance testing
exploratory testing
impact
LCSAJ testing
13. A component of the incident report that determines the actual effect of the incident on the software and its users.
decision table
impact
LCSAJ testing
configuration management tools
14. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
data-driven testing
decision table testing
test management tool features
alpha testing
15. All possible combinations of input values and preconditions are tested.
error guessing
error
exhaustive testing
IEEE test case specification template
16. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
fault attack
configuration management
COTS
cause-effect graphic testing
17. A document that records the description of each event that occurs during the testing process and that requires further investigation
driver
incident report
configuration management
defect masking
18. Find defects in code while the software application being tested is running.
maintenance testing
horizontal traceability
automation tools
dynamic analysis tools
19. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
integration management tools
coverage measurement tools
decision testing
component integration testing
20. Behavior or response of a software application that you observe when you execute the action steps in the test case.
test implementation tasks
waterfall model phases
error
actual result
21. Special additions or changes to the environment required to run a test case.
automation tools
impact
environmental needs
test log uses
22. A task of maintaining and controlling changes to all entities of a system.
condition determination coverage
condition coverage
configuration management
interoperability testing
23. Record details of test cases executed Record order of execution record results
configuration management
test log uses
instrumentation
dynamic analysis tools
24. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
defect
coverage
incident description subheadings
25. Sequence in which data items are accessed or modified by code.
risk-based testing
data flow structure
system testing
contract acceptance testing
26. A review not based on a formal documented procedure
informal review
test log uses
interoperability testing
operational testing
27. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
test control Tasks
test analysis & design tasks
Incidents
decision table
28. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
inspection
interoperability
COTS
backbone integration
29. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
error
incident description subheadings
data flow structure
data-driven testing
30. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
beta testing
system testing
impact analysis
accuracy
31. Deviation of a software system from its expected delivery services or results
failure
exit criteria
defect masking
actual result
32. A unique identifier for each incident report generated during test execution.
Incidents
incident report identifier
IEEE incident report template
cause-effect graphic testing
33. Input or combination of inputs required to test software.
conditions
error guessing
condition determination coverage
functional requirements
34. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
ad hoc integration
backbone integration
maintainability testing
35. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
integration
configuration management tools
impact
36. Human action that generates an incorrect result.
test condition
exit criteria
error
informal review
37. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
functional testing tool
bottom-up integration
functional requirements
38. One defect prevents the detection of another.
iterative-incremental development models
error guessing
anomalous events
defect masking
39. The ratio between the number of defects found and the size of the component/system tested.
exhaustive testing
configuration management
defect density
nonfunctional requirements
40. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
backbone integration
stub
decision table
41. A document that provides the structure for writing test cases.
impact
IEEE test case specification template
functional incremental integration
control flow structure
42. Software products or applications designed to automate manual testing tasks.
automation tools
incident report identifier
conformance testing tools
conditions
43. Response of the application to an input
test control Tasks
action
control flow structure
efficiency
44. 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.
incident report identifier
impact analysis
iterative-incremental development models
inspection
45. Component - Integration - System - Acceptance
decision table testing
condition determination coverage
failure rate
test levels
46. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
documentation tools
accuracy
failure
debugging tools
47. Actual inputs required to execute a test case
code coverage
integration management tools
input specifications
Three main SW development models
48. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
decision table testing
condition determination coverage
incident life cycle phases
testing process phases
49. Specific groups that represent a set of valid or invalid partitions for input conditions.
equivalence partitions
resolution types
decision table testing
interoperability testing
50. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
LCSAJ testing
Three main SW development models
control flow structure
COTS