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. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
business process-based testing
conformance testing tools
Three main SW development models
input specifications
2. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect
functional testing
alpha testing
system testing
3. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
accuracy
bottom-up integration
conditions
cyclomatic complexity
4. A technique used to improve testing coverage by deliberately introducing faults in code.
alpha testing
functional requirements
decision table
fault attack
5. Ability of software to provide appropriate performance relative to amount of resources used.
system testing
coverage
multiple condition coverage
efficiency
6. Components are integrated in the order in which they are developed
LCSAJ
maintainability
ad hoc integration
boundary value analysis
7. The process of finding analyzing and removing causes of failure in a software product.
decision table
debugging
equivalence partitioning
test levels
8. 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.
LCSAJ testing
Three main SW development models
instrumentation
bottom-up integration
9. Response of the application to an input
defect
agile software development model
action
test control Tasks
10. Testing software components that are separately testable. Also module program and unit testing.
failure rate
efficiency
component testing
business process-based testing
11. Human action that generates an incorrect result.
action
fault attack
maintainability testing
error
12. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
functional testing tool
COTS
automation tools
test log uses
13. Increased load (transations) used to test behavior of system under high volume.
test execution tasks
load testing
informal review
incident description subheadings
14. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
testing process phases
efficiency
LCSAJ
impact
15. Record details of test cases executed Record order of execution record results
defect density
test log uses
coverage
equivalence partitions
16. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
experience-based techniques
maintainability testing
interoperability testing
monitor
17. Testing performed to determine whether the system meets acceptance criteria
incremental testing
big-bang testing
acceptance testing
integration management tools
18. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
dynamic analysis tools
incremental testing
exit criteria
integration
19. Sequence in which data items are accessed or modified by code.
IEEE test case specification template
system testing
data flow structure
keyword-driven testing
20. One defect prevents the detection of another.
error guessing
waterfall model benefits
defect masking
acceptance testing
21. A document that provides the structure for writing test cases.
exhaustive testing
impact analysis
IEEE test case specification template
coverage measurement tools
22. Special additions or changes to the environment required to run a test case.
incident report
environmental needs
dynamic analysis tools
risk-based testing
23. Insertion of additional code in the existing program in order to count coverage items.
impact
interoperability
entry criteria
instrumentation
24. Input or combination of inputs required to test software.
operational testing
conditions
stub
waterfall model benefits
25. A task of maintaining and controlling changes to all entities of a system.
code coverage
configuration management
acceptance testing
ad hoc integration
26. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
decision table testing
backbone integration
data flow structure
27. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
exhaustive testing
equivalence partitioning
waterfall model phases
ad hoc integration
28. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
Three main SW development models
alpha testing
decision testing
29. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
component testing
incident life cycle phases
decision testing
condition coverage
30. The ratio between the number of defects found and the size of the component/system tested.
defect density
nonfunctional requirements
acceptance testing
impact analysis
31. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
agile software development model
test planning Tasks
waterfall model phases
incident description subheadings
32. A set of conditions that a system needs to meet in order to be accepted by end users
efficiency
acceptance criteria
waterfall model benefits
incident management tools
33. Software products or applications designed to automate manual testing tasks.
operational testing
test tool deployment Success Factors
inspection
automation tools
34. Integration approach components or subsystems are combined all at once rather than in stages.
boundary value analysis
big-bang testing
resolution types
defect
35. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
decision testing
incident description subheadings
keyword-driven testing
cause-effect graphic testing
36. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
alpha testing
backbone integration
debugging
component
37. White-box design technique used to design test cases for a software component using LCSAJ.
maintainability
LCSAJ testing
stub
defect
38. 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
backbone integration
error
agile software development model
boundary value analysis
39. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
incident description subheadings
accuracy
functionality
incident life cycle phases
40. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
functional requirements
black-box testing
monitor
interoperability
41. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
boundary value analysis
test implementation tasks
alpha testing
equivalence partitions
42. Tests interfaces between components and between integrated components and systems.
test implementation tasks
integration testing
equivalence partitioning
debugging tools
43. Process used to create a SW product from initial conception to public release
SW development model
COTS
error
component
44. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
waterfall model benefits
functionality
alpha testing
efficiency
45. Component - Integration - System - Acceptance
debugging
automation tools
test levels
independence of testing
46. 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
functionality
test planning Tasks
agile software development model
47. The smallest software item that can be tested in isolation.
component
resolution types
debugging tools
condition determination coverage
48. Testing an integrated system to validate it meets requirements
data flow structure
system testing
debugging
experience-based techniques
49. Used to replace a component that calls another component.
big-bang testing
Incidents
exploratory testing
driver
50. Based on analysis of functional specifications of a system.
functional testing
test planning Tasks
load testing
operational testing