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. Record details of test cases executed Record order of execution record results
integration testing
stub
test log uses
documentation tools
2. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
conditions
debugging
keyword-driven testing
maintenance testing
3. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
risk-based testing
Three main SW development models
defect
4. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
defect density
big-bang testing
decision coverage
5. A component of the incident report that determines the actual effect of the incident on the software and its users.
debugging
impact analysis
impact
Three main SW development models
6. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
multiple condition coverage
defect masking
component
test execution tasks
7. 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).
configuration management tools
accuracy
component
LCSAJ
8. Measures amount of testing performed by a collection of test cases
component testing
failure rate
iterative-incremental development models
coverage
9. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
functional incremental integration
SW development model
incident description subheadings
failure rate
10. A set of conditions that a system needs to meet in order to be accepted by end users
instrumentation
cause-effect graphic testing
acceptance criteria
Three main SW development models
11. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
test condition
error guessing
IEEE test case specification template
SW development model
12. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
configuration management
cyclomatic complexity
interoperability
black-box testing
13. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
defect masking
conformance testing tools
failure
14. Find defects in code while the software application being tested is running.
driver
operational testing
business process-based testing
dynamic analysis tools
15. Events that occurred during the testing process our investigation.
test tool deployment Success Factors
nonfunctional requirements
decision table
Incidents
16. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
impact analysis
decision table
cause-effect graphic testing
test management tool features
17. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
component testing
configuration management tools
debugging
contract acceptance testing
18. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
functional testing tool
incident report
driver
19. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
functional incremental integration
agile software development model
nonfunctional requirements
driver
20. The ratio between the number of defects found and the size of the component/system tested.
coverage
defect density
decision coverage
functional requirements
21. Examine changes made to an operational system cause defects.
test planning Tasks
maintenance testing
debugging tools
beta testing
22. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
incident report identifier
exhaustive testing
iterative-incremental development models
integration management tools
23. 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
big-bang testing
agile software development model
SW development model
test tool deployment Success Factors
24. Software products or applications designed to automate manual testing tasks.
decision coverage
configuration management
automation tools
accuracy
25. Increased load (transations) used to test behavior of system under high volume.
load testing
IEEE incident report template
functional testing tool
data flow structure
26. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
waterfall model phases
condition coverage
functional testing tool
error
27. Special additions or changes to the environment required to run a test case.
decision testing
coverage measurement tools
environmental needs
automation tools
28. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
input specifications
IEEE incident report template
black-box testing
decision testing
29. Process used to create a SW product from initial conception to public release
horizontal traceability
interoperability testing
SW development model
contract acceptance testing
30. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
multiple condition coverage
Incidents
COTS
test execution tasks
31. Actual inputs required to execute a test case
alpha testing
input specifications
contract acceptance testing
equivalence partitions
32. 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
conformance testing tools
stub
exit criteria
33. Components are combined and tested in the order in which basic functionalities start working
impact analysis
test execution tasks
functional incremental integration
alpha testing
34. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
load testing
integration management tools
anomalous events
component integration testing
35. An analysis that determines the portion of code on software executed by a set of test cases
code coverage
COTS
test management tool features
test control Tasks
36. Sequence in which data items are accessed or modified by code.
actual result
environmental needs
boundary value analysis
data flow structure
37. Allows storage of test input and expected results in one or more central data sources or databases.
load testing
functional testing tool
test condition
data-driven testing
38. Component - Integration - System - Acceptance
test log uses
test levels
Three main SW development models
environmental needs
39. Components are integrated in the order in which they are developed
error
ad hoc integration
efficiency
maintenance testing
40. 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
LCSAJ
functional incremental integration
SW development model
41. Sequence in which instructions are executed through a component or system
instrumentation
beta testing
control flow structure
test tool deployment Success Factors
42. An event or item that can be tested using one or more test cases
beta testing
test condition
maintainability
backbone integration
43. 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
system testing
decision testing
IEEE incident report template
44. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
risk-based testing
component testing
integration
incident life cycle phases
45. Based on analysis of functional specifications of a system.
defect masking
acceptance testing
system testing
functional testing
46. Conditions required to begin testing activities.
SW development model
testing process phases
control flow structure
entry criteria
47. One defect prevents the detection of another.
beta testing
incident management tools
defect masking
test management tool features
48. Integrate different kinds of tools to make test management more efficient and simple.
test analysis & design tasks
integration management tools
actual result
SW development model
49. Waterfall iterative-incremental "V"
boundary value analysis
Three main SW development models
control flow structure
risk-based testing
50. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
IEEE test case specification template
integration testing
IEEE incident report template