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. Integration approach components or subsystems are combined all at once rather than in stages.
boundary value analysis
big-bang testing
data flow structure
input specifications
2. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
inspection
condition determination coverage
conformance testing tools
interoperability
3. Testing performed to determine whether the system meets acceptance criteria
actual result
acceptance testing
maintainability testing
debugging tools
4. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
test planning Tasks
decision coverage
maintainability
incident description subheadings
5. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
functional testing
keyword-driven testing
iterative-incremental development models
6. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
component integration testing
alpha testing
contract acceptance testing
test log uses
7. Software products or applications designed to automate manual testing tasks.
automation tools
operational testing
equivalence partitioning
resolution types
8. Separation of testing responsibilities which encourages the accomplishment of objective testing
testing process phases
coverage
test control Tasks
independence of testing
9. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
cyclomatic complexity
error guessing
incident report identifier
failure rate
10. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
coverage measurement tools
functional incremental integration
cyclomatic complexity
entry criteria
11. Behavior or response of a software application that you observe when you execute the action steps in the test case.
equivalence partitions
driver
Impact subheadings
actual result
12. Based on analysis of functional specifications of a system.
test implementation tasks
functional testing
inspection
decision table
13. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect
dynamic analysis tools
test control Tasks
IEEE incident report template
14. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
alpha testing
test execution tasks
instrumentation
maintainability
15. 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
component testing
nonfunctional requirements
driver
16. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
maintainability
action
impact analysis
multiple condition coverage
17. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
input specifications
cause-effect graphic testing
keyword-driven testing
system testing
18. Testing an integrated system to validate it meets requirements
system testing
bottom-up integration
stub
incident description subheadings
19. One defect prevents the detection of another.
defect masking
condition coverage
condition determination coverage
stub
20. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
operational testing
acceptance criteria
experience-based techniques
equivalence partitioning
21. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
dynamic analysis tools
nonfunctional requirements
test levels
22. A set of conditions that a system needs to meet in order to be accepted by end users
functionality
inspection
code coverage
acceptance criteria
23. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
black-box testing
defect
big-bang testing
exploratory testing
24. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
Impact subheadings
impact
informal review
25. The ratio between the number of defects found and the size of the component/system tested.
instrumentation
condition coverage
defect density
integration management tools
26. All possible combinations of input values and preconditions are tested.
functional testing
defect masking
test log uses
exhaustive testing
27. Testing software in its operational environment
dynamic analysis tools
operational testing
contract acceptance testing
test control Tasks
28. Sequence in which instructions are executed through a component or system
failure rate
control flow structure
testing process phases
failure
29. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
nonfunctional requirements
functional incremental integration
debugging
30. Allows storage of test input and expected results in one or more central data sources or databases.
SW development model
equivalence partitions
data-driven testing
test planning Tasks
31. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
equivalence partitions
Three main SW development models
maintainability testing
test management tool features
32. The process of finding analyzing and removing causes of failure in a software product.
incident report
anomalous events
decision table
debugging
33. A document that records the description of each event that occurs during the testing process and that requires further investigation
integration testing
incident report
alpha testing
functional testing
34. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
control flow structure
interoperability
test data preparation tools
35. 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).
automation tools
configuration management tools
efficiency
waterfall model benefits
36. Increased load (transations) used to test behavior of system under high volume.
load testing
risk-based testing
debugging tools
LCSAJ testing
37. Tests interfaces between components and between integrated components and systems.
system testing
integration testing
decision coverage
efficiency
38. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
test management tool features
failure
interoperability testing
integration
39. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
integration testing
experience-based techniques
backbone integration
accuracy
40. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
decision testing
incremental testing
horizontal traceability
41. Develop & proiroitize test cases Create groups of test cases Set up test environment
test implementation tasks
incident management tools
Impact subheadings
test tool deployment Success Factors
42. A task of maintaining and controlling changes to all entities of a system.
independence of testing
iterative-incremental development models
configuration management
component integration testing
43. A document that provides the structure for writing test cases.
Impact subheadings
driver
incident report identifier
IEEE test case specification template
44. Input or combination of inputs required to test software.
conditions
accuracy
independence of testing
driver
45. Components are integrated in the order in which they are developed
functional incremental integration
fault attack
stub
ad hoc integration
46. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
informal review
LCSAJ
cyclomatic complexity
47. Waterfall iterative-incremental "V"
Three main SW development models
business process-based testing
test implementation tasks
test levels
48. Component - Integration - System - Acceptance
environmental needs
keyword-driven testing
test levels
SW development model
49. Ability of software to provide appropriate performance relative to amount of resources used.
incident description subheadings
IEEE incident report template
efficiency
stub
50. Requirements that determine the functionality of a software system.
functional requirements
conditions
condition determination coverage
automation tools