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. Special-purpose software used to simulate a component called by the component under test
operational testing
integration management tools
integration testing
stub
2. Increased load (transations) used to test behavior of system under high volume.
resolution types
load testing
inspection
system testing
3. Component - Integration - System - Acceptance
experience-based techniques
test levels
exploratory testing
component testing
4. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
big-bang testing
maintainability testing
code coverage
experience-based techniques
5. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
decision testing
inspection
defect masking
6. Operational testing performed at an _external_ site without involvement of the developing organization.
informal review
beta testing
automation tools
LCSAJ
7. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
IEEE incident report template
equivalence partitions
data flow structure
incident description subheadings
8. Separation of testing responsibilities which encourages the accomplishment of objective testing
component testing
interoperability testing
independence of testing
testing process phases
9. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
input specifications
action
boundary value analysis
inspection
10. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
decision coverage
exit criteria
resolution types
interoperability testing
11. A component of the incident report that determines the actual effect of the incident on the software and its users.
configuration management
impact
incident management tools
functional incremental integration
12. Testing performed to determine whether the system meets acceptance criteria
debugging tools
acceptance testing
cause-effect graphic testing
exit criteria
13. Components are integrated in the order in which they are developed
decision table
informal review
debugging
ad hoc integration
14. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
nonfunctional requirements
cause-effect graphic testing
iterative-incremental development models
multiple condition coverage
15. A task of maintaining and controlling changes to all entities of a system.
Three main SW development models
acceptance criteria
configuration management tools
configuration management
16. Integrate different kinds of tools to make test management more efficient and simple.
conditions
waterfall model phases
actual result
integration management tools
17. Tools used by developers to identify defects in programs.
debugging
configuration management tools
cyclomatic complexity
debugging tools
18. The capability of a software product to provide agreed and correct output with the required degree of precision
test tool deployment Success Factors
failure rate
accuracy
horizontal traceability
19. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
incident description subheadings
defect masking
functional testing
horizontal traceability
20. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
functional incremental integration
test management tool features
iterative-incremental development models
interoperability testing
21. Testing software in its operational environment
operational testing
coverage measurement tools
acceptance testing
LCSAJ testing
22. Process used to create a SW product from initial conception to public release
equivalence partitions
SW development model
cause-effect graphic testing
test implementation tasks
23. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
informal review
contract acceptance testing
keyword-driven testing
IEEE test case specification template
24. 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.
alpha testing
efficiency
bottom-up integration
accuracy
25. Black-box test design technique - test cases are designed from a decision table.
decision table testing
interoperability testing
black-box testing
Incidents
26. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
configuration management
LCSAJ
incremental testing
Impact subheadings
27. The smallest software item that can be tested in isolation.
independence of testing
component
data flow structure
control flow structure
28. Requirements that determine the functionality of a software system.
test control Tasks
dynamic analysis tools
iterative-incremental development models
functional requirements
29. Severity - Priority
Impact subheadings
incremental testing
configuration management tools
iterative-incremental development models
30. Black-box testing technique used to create groups of input conditions that create the same kind of output.
nonfunctional requirements
LCSAJ testing
waterfall model phases
equivalence partitioning
31. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
acceptance criteria
beta testing
entry criteria
alpha testing
32. Behavior or response of a software application that you observe when you execute the action steps in the test case.
acceptance criteria
equivalence partitions
fault attack
actual result
33. Examine changes made to an operational system cause defects.
data flow structure
maintenance testing
integration testing
incident description subheadings
34. Used to test the functionality of software as mentioned in software requirement specifications.
interoperability testing
integration testing
bottom-up integration
functional testing tool
35. Sequence in which data items are accessed or modified by code.
data flow structure
decision coverage
efficiency
cyclomatic complexity
36. Input or combination of inputs required to test software.
defect
conditions
debugging tools
incident life cycle phases
37. 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
interoperability testing
testing process phases
Three main SW development models
38. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
condition coverage
black-box testing
impact analysis
iterative-incremental development models
39. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
incident report identifier
functional incremental integration
maintainability
multiple condition coverage
40. 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.
inspection
driver
coverage measurement tools
condition determination coverage
41. Combining components or sytems into larger structural units or subsystems.
integration
Three main SW development models
cause-effect graphic testing
COTS
42. Occurrences that happen before and after an unexpected event
agile software development model
integration
multiple condition coverage
anomalous events
43. Specific groups that represent a set of valid or invalid partitions for input conditions.
coverage measurement tools
agile software development model
equivalence partitions
functional requirements
44. Response of the application to an input
configuration management tools
boundary value analysis
action
integration
45. Waterfall iterative-incremental "V"
acceptance testing
Three main SW development models
maintainability
actual result
46. Tools used to identify and calculate coverage items in program code.
defect
dynamic analysis tools
cyclomatic complexity
coverage measurement tools
47. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
keyword-driven testing
test levels
risk-based testing
input specifications
48. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
equivalence partitioning
impact analysis
IEEE incident report template
condition determination coverage
49. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
exploratory testing
ad hoc integration
monitor
LCSAJ testing
50. Tools used to store and manage incidents return phone defects failures or anomalies.
maintainability
configuration management
incident management tools
maintainability testing