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. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
accuracy
test planning Tasks
risk-based testing
2. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
conditions
incident life cycle phases
contract acceptance testing
Incidents
3. Special additions or changes to the environment required to run a test case.
black-box testing
environmental needs
driver
big-bang testing
4. Insertion of additional code in the existing program in order to count coverage items.
impact
nonfunctional requirements
instrumentation
actual result
5. 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
dynamic analysis tools
functional testing
test planning Tasks
operational testing
6. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
acceptance testing
exit criteria
big-bang testing
7. Incident Report - Identifier - Summary - Incident - Description - Impact
incident report
maintenance testing
failure rate
IEEE incident report template
8. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
horizontal traceability
documentation tools
component
9. Black-box testing technique used to create groups of input conditions that create the same kind of output.
beta testing
equivalence partitioning
testing process phases
SW development model
10. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
black-box testing
condition coverage
incident management tools
incident life cycle phases
11. Human action that generates an incorrect result.
error
test control Tasks
waterfall model benefits
integration
12. Components are combined and tested in the order in which basic functionalities start working
environmental needs
IEEE incident report template
incident report identifier
functional incremental integration
13. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
load testing
resolution types
acceptance criteria
environmental needs
14. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables
waterfall model benefits
configuration management tools
contract acceptance testing
impact
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 condition
test tool deployment Success Factors
documentation tools
independence of testing
16. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
configuration management
test log uses
cyclomatic complexity
test analysis & design tasks
17. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
conditions
waterfall model phases
boundary value analysis
testing process phases
18. Measures amount of testing performed by a collection of test cases
functional requirements
coverage
integration management tools
coverage measurement tools
19. Find defects in code while the software application being tested is running.
driver
horizontal traceability
dynamic analysis tools
impact
20. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
integration management tools
actual result
black-box testing
incident management tools
21. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
cause-effect graphic testing
decision testing
test control Tasks
integration
22. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
informal review
environmental needs
conformance testing tools
automation tools
23. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
incident management tools
interoperability testing
resolution types
24. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
fault attack
defect
COTS
exit criteria
25. Specific groups that represent a set of valid or invalid partitions for input conditions.
decision testing
action
equivalence partitions
instrumentation
26. Informal testing technique in which test planning and execution run in parallel
exploratory testing
test management tool features
decision testing
testing process phases
27. Separation of testing responsibilities which encourages the accomplishment of objective testing
COTS
environmental needs
independence of testing
inspection
28. Testing software components that are separately testable. Also module program and unit testing.
coverage measurement tools
agile software development model
component testing
conditions
29. A table showing combinations of inputs and their associated actions.
test planning Tasks
test levels
decision table
IEEE test case specification template
30. Component - Integration - System - Acceptance
test execution tasks
test levels
cause-effect graphic testing
test condition
31. Special-purpose software used to simulate a component that calls the component under test
condition determination coverage
component integration testing
coverage measurement tools
driver
32. Events that occurred during the testing process our investigation.
boundary value analysis
Incidents
acceptance testing
maintainability testing
33. Increased load (transations) used to test behavior of system under high volume.
load testing
functionality
maintainability
action
34. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
test execution tasks
test control Tasks
stub
environmental needs
35. Black-box test design technique - test cases are designed from a decision table.
waterfall model phases
decision table testing
boundary value analysis
bottom-up integration
36. White-box design technique used to design test cases for a software component using LCSAJ.
waterfall model benefits
debugging tools
interoperability
LCSAJ testing
37. Severity - Priority
monitor
risk-based testing
Impact subheadings
debugging tools
38. Tools used to identify and calculate coverage items in program code.
impact analysis
ad hoc integration
coverage measurement tools
load testing
39. A document that provides the structure for writing test cases.
LCSAJ testing
test planning Tasks
IEEE test case specification template
incident description subheadings
40. Conditions required to begin testing activities.
test control Tasks
entry criteria
risk-based testing
coverage
41. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
agile software development model
incremental testing
code coverage
decision testing
42. 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
condition determination coverage
agile software development model
beta testing
independence of testing
43. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
debugging
nonfunctional requirements
IEEE test case specification template
test planning Tasks
44. Response of the application to an input
actual result
acceptance testing
action
functionality
45. Special-purpose software used to simulate a component called by the component under test
integration testing
ad hoc integration
stub
boundary value analysis
46. Used to replace a component that calls another component.
resolution types
driver
efficiency
business process-based testing
47. Calculates the number of executed branch outcomes in code.
documentation tools
incident report identifier
decision coverage
bottom-up integration
48. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incremental testing
condition determination coverage
test control Tasks
acceptance criteria
49. 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
failure
input specifications
incident description subheadings
50. Linear Code Sequence and Jump.
independence of testing
test analysis & design tasks
COTS
LCSAJ