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. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
system testing
test management tool features
iterative-incremental development models
functional testing
2. A component of the incident report that determines the actual effect of the incident on the software and its users.
SW development model
integration
LCSAJ testing
impact
3. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
multiple condition coverage
test management tool features
impact
LCSAJ testing
4. A set of conditions that a system needs to meet in order to be accepted by end users
decision table testing
coverage measurement tools
defect density
acceptance criteria
5. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
incident description subheadings
alpha testing
driver
maintainability testing
6. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
defect
maintainability testing
interoperability
load testing
7. Behavior or response of a software application that you observe when you execute the action steps in the test case.
incremental testing
acceptance criteria
actual result
action
8. 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
test tool deployment Success Factors
failure
driver
component
9. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
integration testing
waterfall model phases
test data preparation tools
10. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
failure
experience-based techniques
incident report
coverage measurement tools
11. Response of the application to an input
action
test levels
experience-based techniques
alpha testing
12. An event or item that can be tested using one or more test cases
bottom-up integration
test condition
defect masking
acceptance criteria
13. The capability of a software product to provide agreed and correct output with the required degree of precision
accuracy
code coverage
Impact subheadings
acceptance criteria
14. Based on analysis of functional specifications of a system.
beta testing
actual result
control flow structure
functional testing
15. Sequence in which instructions are executed through a component or system
control flow structure
interoperability
data-driven testing
data flow structure
16. Components are integrated in the order in which they are developed
debugging tools
ad hoc integration
horizontal traceability
decision coverage
17. Linear Code Sequence and Jump.
defect
independence of testing
LCSAJ
horizontal traceability
18. Conditions required to begin testing activities.
entry criteria
decision table testing
Impact subheadings
test analysis & design tasks
19. Input or combination of inputs required to test software.
load testing
conditions
boundary value analysis
exploratory testing
20. Allows storage of test input and expected results in one or more central data sources or databases.
configuration management tools
data-driven testing
incident report identifier
failure
21. 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
maintainability testing
cyclomatic complexity
test levels
22. 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).
integration
equivalence partitioning
integration testing
configuration management tools
23. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
IEEE incident report template
dynamic analysis tools
action
24. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
IEEE test case specification template
boundary value analysis
condition determination coverage
backbone integration
25. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
cyclomatic complexity
backbone integration
debugging
acceptance criteria
26. Tests interfaces between components and between integrated components and systems.
condition determination coverage
integration testing
decision testing
condition coverage
27. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
incident report
inspection
accuracy
monitor
28. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
decision coverage
interoperability
acceptance criteria
impact
29. Events that occurred during the testing process our investigation.
load testing
driver
Incidents
bottom-up integration
30. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
failure
monitor
black-box testing
error guessing
31. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
interoperability
configuration management tools
anomalous events
functionality
32. One defect prevents the detection of another.
independence of testing
LCSAJ testing
decision coverage
defect masking
33. 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.
operational testing
bottom-up integration
test tool deployment Success Factors
LCSAJ testing
34. Combining components or sytems into larger structural units or subsystems.
integration
functionality
actual result
inspection
35. A unique identifier for each incident report generated during test execution.
Incidents
multiple condition coverage
coverage
incident report identifier
36. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
environmental needs
fault attack
cyclomatic complexity
37. A task of maintaining and controlling changes to all entities of a system.
debugging
configuration management
test condition
risk-based testing
38. Actual inputs required to execute a test case
input specifications
multiple condition coverage
integration management tools
test control Tasks
39. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
inspection
experience-based techniques
resolution types
40. Tools used to store and manage incidents return phone defects failures or anomalies.
LCSAJ
incident management tools
failure rate
beta testing
41. 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
error guessing
integration
entry criteria
agile software development model
42. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
cyclomatic complexity
data flow structure
risk-based testing
waterfall model phases
43. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
entry criteria
integration
COTS
testing process phases
44. Process used to create a SW product from initial conception to public release
conformance testing tools
accuracy
SW development model
decision table testing
45. Develop & proiroitize test cases Create groups of test cases Set up test environment
testing process phases
test implementation tasks
acceptance testing
informal review
46. Measures amount of testing performed by a collection of test cases
coverage
IEEE test case specification template
alpha testing
debugging
47. Tools used by developers to identify defects in programs.
incident management tools
system testing
debugging tools
contract acceptance testing
48. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
configuration management tools
conformance testing tools
test control Tasks
fault attack
49. Testing software in its operational environment
defect
debugging
operational testing
impact analysis
50. A table showing combinations of inputs and their associated actions.
automation tools
component integration testing
resolution types
decision table