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. Tools used to identify and calculate coverage items in program code.
bottom-up integration
independence of testing
incident report
coverage measurement tools
2. 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
test levels
failure
functional testing tool
3. Special additions or changes to the environment required to run a test case.
anomalous events
component integration testing
environmental needs
fault attack
4. The capability of a software product to provide agreed and correct output with the required degree of precision
backbone integration
accuracy
iterative-incremental development models
test control Tasks
5. Testing an integrated system to validate it meets requirements
fault attack
system testing
risk-based testing
business process-based testing
6. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
documentation tools
defect
test levels
component integration testing
7. 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
test planning Tasks
multiple condition coverage
backbone integration
coverage measurement tools
8. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
exit criteria
inspection
failure rate
9. Examine changes made to an operational system cause defects.
efficiency
maintenance testing
instrumentation
error
10. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
iterative-incremental development models
test analysis & design tasks
test condition
11. Develop & proiroitize test cases Create groups of test cases Set up test environment
efficiency
test implementation tasks
configuration management tools
functionality
12. Sequence in which instructions are executed through a component or system
acceptance criteria
control flow structure
test management tool features
experience-based techniques
13. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
inspection
functional incremental integration
bottom-up integration
14. Used to replace a component that calls another component.
test planning Tasks
Impact subheadings
business process-based testing
driver
15. One defect prevents the detection of another.
waterfall model benefits
defect masking
interoperability
incident report identifier
16. The process of finding analyzing and removing causes of failure in a software product.
incident description subheadings
component testing
debugging
bottom-up integration
17. Input or combination of inputs required to test software.
conditions
incident report
control flow structure
input specifications
18. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
functional testing
IEEE incident report template
functionality
condition coverage
19. Testing performed to determine whether the system meets acceptance criteria
driver
acceptance testing
horizontal traceability
test log uses
20. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
IEEE test case specification template
testing process phases
decision coverage
functional requirements
21. Tests interfaces between components and between integrated components and systems.
load testing
cause-effect graphic testing
automation tools
integration testing
22. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
waterfall model benefits
interoperability
SW development model
23. Sequence in which data items are accessed or modified by code.
condition coverage
impact analysis
data flow structure
integration management tools
24. Specific groups that represent a set of valid or invalid partitions for input conditions.
functionality
instrumentation
equivalence partitions
multiple condition coverage
25. Ability of software to provide appropriate performance relative to amount of resources used.
monitor
efficiency
actual result
backbone integration
26. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
IEEE test case specification template
interoperability
operational testing
actual result
27. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
contract acceptance testing
action
component
test control Tasks
28. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
entry criteria
driver
test execution tasks
alpha testing
29. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
test analysis & design tasks
impact
nonfunctional requirements
COTS
30. A table showing combinations of inputs and their associated actions.
maintenance testing
LCSAJ
decision table
data-driven testing
31. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
component testing
action
defect
error guessing
32. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
functionality
decision coverage
contract acceptance testing
SW development model
33. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
exhaustive testing
incremental testing
component integration testing
interoperability
34. A unique identifier for each incident report generated during test execution.
automation tools
LCSAJ
configuration management
incident report identifier
35. Record details of test cases executed Record order of execution record results
instrumentation
decision testing
test log uses
functionality
36. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
integration testing
defect masking
impact analysis
COTS
37. Severity - Priority
actual result
Impact subheadings
test condition
nonfunctional requirements
38. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
LCSAJ testing
big-bang testing
conformance testing tools
coverage measurement tools
39. Occurrences that happen before and after an unexpected event
configuration management
functionality
ad hoc integration
anomalous events
40. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
resolution types
test implementation tasks
waterfall model phases
decision testing
41. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
environmental needs
experience-based techniques
condition coverage
test data preparation tools
42. Find defects in code while the software application being tested is running.
test log uses
integration management tools
COTS
dynamic analysis tools
43. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
maintenance testing
multiple condition coverage
component integration testing
informal review
44. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
Incidents
dynamic analysis tools
horizontal traceability
stub
45. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
agile software development model
boundary value analysis
integration testing
46. An analysis that determines the portion of code on software executed by a set of test cases
business process-based testing
equivalence partitioning
code coverage
action
47. Operational testing performed at an _external_ site without involvement of the developing organization.
failure
beta testing
test analysis & design tasks
IEEE incident report template
48. Informal testing technique in which test planning and execution run in parallel
exploratory testing
exhaustive testing
code coverage
defect masking
49. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
beta testing
test control Tasks
interoperability testing
iterative-incremental development models
50. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
operational testing
integration testing
decision table
risk-based testing