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. An event or item that can be tested using one or more test cases
test condition
risk-based testing
equivalence partitions
alpha testing
2. Testing software in its operational environment
maintenance testing
decision table
system testing
operational testing
3. Special-purpose software used to simulate a component called by the component under test
error guessing
IEEE test case specification template
load testing
stub
4. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
incident report
dynamic analysis tools
cause-effect graphic testing
actual result
5. Used to test the functionality of software as mentioned in software requirement specifications.
driver
functional testing tool
dynamic analysis tools
alpha testing
6. Components are integrated in the order in which they are developed
failure rate
ad hoc integration
decision testing
test levels
7. Special additions or changes to the environment required to run a test case.
acceptance testing
incident report
coverage measurement tools
environmental needs
8. Software products or applications designed to automate manual testing tasks.
maintainability testing
agile software development model
test planning Tasks
automation tools
9. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
component testing
data flow structure
defect density
decision testing
10. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
iterative-incremental development models
functional incremental integration
incident life cycle phases
11. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
acceptance criteria
coverage measurement tools
IEEE test case specification template
12. Tools used by developers to identify defects in programs.
debugging tools
boundary value analysis
incident life cycle phases
data flow structure
13. Examine changes made to an operational system cause defects.
maintenance testing
test analysis & design tasks
business process-based testing
test condition
14. Sequence in which instructions are executed through a component or system
code coverage
configuration management
control flow structure
input specifications
15. The smallest software item that can be tested in isolation.
input specifications
integration testing
defect masking
component
16. Conditions required to begin testing activities.
entry criteria
IEEE incident report template
integration testing
agile software development model
17. Input or combination of inputs required to test software.
agile software development model
functional testing tool
conditions
monitor
18. The process of finding analyzing and removing causes of failure in a software product.
impact analysis
debugging
configuration management tools
acceptance criteria
19. Testing an integrated system to validate it meets requirements
independence of testing
LCSAJ
operational testing
system testing
20. A functional testing approach in which test cases are designed based on business processes.
COTS
environmental needs
operational testing
business process-based testing
21. The ratio between the number of defects found and the size of the component/system tested.
defect density
load testing
incremental testing
iterative-incremental development models
22. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test control Tasks
agile software development model
failure rate
driver
23. Used to replace a component that calls another component.
input specifications
decision table
cyclomatic complexity
driver
24. 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
equivalence partitioning
acceptance testing
test tool deployment Success Factors
nonfunctional requirements
25. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
test planning Tasks
backbone integration
coverage measurement tools
automation tools
26. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
alpha testing
maintenance testing
interoperability
27. Increased load (transations) used to test behavior of system under high volume.
condition coverage
load testing
alpha testing
incident management tools
28. Integration approach components or subsystems are combined all at once rather than in stages.
configuration management
waterfall model benefits
big-bang testing
informal review
29. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
alpha testing
exit criteria
equivalence partitions
component testing
30. 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
functional incremental integration
test planning Tasks
entry criteria
Impact subheadings
31. Black-box test design technique - test cases are designed from a decision table.
accuracy
decision table testing
boundary value analysis
acceptance criteria
32. Behavior or response of a software application that you observe when you execute the action steps in the test case.
actual result
data flow structure
failure rate
conformance testing tools
33. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incremental testing
waterfall model phases
debugging tools
black-box testing
34. Based on analysis of functional specifications of a system.
functional testing
test management tool features
coverage measurement tools
condition determination coverage
35. A technique used to improve testing coverage by deliberately introducing faults in code.
test data preparation tools
configuration management
fault attack
backbone integration
36. Waterfall iterative-incremental "V"
operational testing
control flow structure
instrumentation
Three main SW development models
37. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
acceptance testing
keyword-driven testing
anomalous events
black-box testing
38. Calculates the number of executed branch outcomes in code.
conditions
bottom-up integration
decision coverage
defect masking
39. Tools used to store and manage incidents return phone defects failures or anomalies.
test control Tasks
debugging tools
incident management tools
interoperability testing
40. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
bottom-up integration
test data preparation tools
conformance testing tools
LCSAJ
41. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
bottom-up integration
inspection
cyclomatic complexity
data flow structure
42. Specific groups that represent a set of valid or invalid partitions for input conditions.
functional testing
equivalence partitions
defect density
data-driven testing
43. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
cyclomatic complexity
error guessing
functionality
conditions
44. A table showing combinations of inputs and their associated actions.
functional requirements
entry criteria
decision table
backbone integration
45. 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
contract acceptance testing
backbone integration
decision table testing
agile software development model
46. Develop & proiroitize test cases Create groups of test cases Set up test environment
inspection
equivalence partitioning
decision table
test implementation tasks
47. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
acceptance testing
functional testing
impact analysis
defect
48. A document that provides the structure for writing test cases.
IEEE test case specification template
nonfunctional requirements
defect density
control flow structure
49. Allows storage of test input and expected results in one or more central data sources or databases.
test log uses
integration
data-driven testing
test data preparation tools
50. Combining components or sytems into larger structural units or subsystems.
integration
experience-based techniques
big-bang testing
data-driven testing