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. A document that records the description of each event that occurs during the testing process and that requires further investigation
functional incremental integration
incident report
integration testing
impact
2. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
waterfall model benefits
backbone integration
automation tools
agile software development model
3. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
impact analysis
risk-based testing
condition coverage
test control Tasks
4. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
defect
data flow structure
decision testing
defect density
5. Testing performed to determine whether the system meets acceptance criteria
incident management tools
maintainability
acceptance testing
impact analysis
6. Increased load (transations) used to test behavior of system under high volume.
bottom-up integration
load testing
informal review
waterfall model phases
7. A functional testing approach in which test cases are designed based on business processes.
decision coverage
waterfall model phases
business process-based testing
functional incremental integration
8. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
functional requirements
incident management tools
LCSAJ
exit criteria
9. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
data flow structure
stub
functional testing
10. Conditions required to begin testing activities.
functional incremental integration
entry criteria
dynamic analysis tools
incident life cycle phases
11. Find defects in code while the software application being tested is running.
integration testing
configuration management
dynamic analysis tools
test tool deployment Success Factors
12. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
testing process phases
COTS
configuration management tools
component integration testing
13. Linear Code Sequence and Jump.
agile software development model
LCSAJ
Incidents
IEEE test case specification template
14. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
failure rate
control flow structure
functional incremental integration
automation tools
15. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
functional testing tool
integration
defect
ad hoc integration
16. Tools used to identify and calculate coverage items in program code.
incident report
system testing
coverage measurement tools
functional requirements
17. Waterfall iterative-incremental "V"
Three main SW development models
incident management tools
condition determination coverage
independence of testing
18. An event or item that can be tested using one or more test cases
acceptance criteria
interoperability testing
decision table testing
test condition
19. Sequence in which instructions are executed through a component or system
functional incremental integration
multiple condition coverage
decision table
control flow structure
20. Measures amount of testing performed by a collection of test cases
condition coverage
informal review
coverage
defect density
21. Behavior or response of a software application that you observe when you execute the action steps in the test case.
actual result
conformance testing tools
test management tool features
test log uses
22. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
integration
agile software development model
experience-based techniques
equivalence partitioning
23. Separation of testing responsibilities which encourages the accomplishment of objective testing
risk-based testing
independence of testing
test condition
debugging
24. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
load testing
informal review
error guessing
decision coverage
25. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
integration
component testing
keyword-driven testing
contract acceptance testing
26. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
load testing
bottom-up integration
coverage measurement tools
27. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
driver
error guessing
cause-effect graphic testing
28. Process used to create a SW product from initial conception to public release
incident life cycle phases
Three main SW development models
SW development model
interoperability
29. 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).
test log uses
accuracy
functional testing
configuration management tools
30. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
incremental testing
dynamic analysis tools
decision table
impact analysis
31. 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.
dynamic analysis tools
condition determination coverage
inspection
debugging tools
32. Tools used by developers to identify defects in programs.
contract acceptance testing
debugging tools
test execution tasks
test control Tasks
33. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
control flow structure
test analysis & design tasks
conditions
exit criteria
34. A task of maintaining and controlling changes to all entities of a system.
waterfall model benefits
monitor
configuration management
component
35. Black-box test design technique - test cases are designed from a decision table.
decision table testing
test management tool features
cause-effect graphic testing
incremental testing
36. Software products or applications designed to automate manual testing tasks.
inspection
data-driven testing
anomalous events
automation tools
37. White-box design technique used to design test cases for a software component using LCSAJ.
acceptance testing
component
action
LCSAJ testing
38. Severity - Priority
Impact subheadings
maintainability testing
input specifications
actual result
39. Sequence in which data items are accessed or modified by code.
test tool deployment Success Factors
integration management tools
Impact subheadings
data flow structure
40. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
conformance testing tools
multiple condition coverage
automation tools
condition coverage
41. Component - Integration - System - Acceptance
test levels
bottom-up integration
decision table
informal review
42. Specific groups that represent a set of valid or invalid partitions for input conditions.
equivalence partitions
incremental testing
load testing
decision table testing
43. Components are combined and tested in the order in which basic functionalities start working
efficiency
functional incremental integration
action
instrumentation
44. One defect prevents the detection of another.
stub
interoperability
defect masking
exhaustive testing
45. Examine changes made to an operational system cause defects.
maintenance testing
component
data flow structure
Three main SW development models
46. Develop & proiroitize test cases Create groups of test cases Set up test environment
contract acceptance testing
test implementation tasks
test data preparation tools
coverage measurement tools
47. Incident Report - Identifier - Summary - Incident - Description - Impact
ad hoc integration
test levels
inspection
IEEE incident report template
48. Special additions or changes to the environment required to run a test case.
exhaustive testing
testing process phases
environmental needs
decision coverage
49. 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
incident description subheadings
data-driven testing
code coverage
50. Events that occurred during the testing process our investigation.
impact analysis
Incidents
entry criteria
stub