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. Calculates the number of executed branch outcomes in code.
test planning Tasks
condition determination coverage
decision coverage
maintenance testing
2. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
actual result
component
iterative-incremental development models
LCSAJ
3. Find defects in code while the software application being tested is running.
entry criteria
beta testing
dynamic analysis tools
incident life cycle phases
4. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
IEEE incident report template
test management tool features
waterfall model benefits
5. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
COTS
efficiency
maintainability
resolution types
6. Severity - Priority
exit criteria
configuration management tools
data flow structure
Impact subheadings
7. Events that occurred during the testing process our investigation.
incident report identifier
anomalous events
keyword-driven testing
Incidents
8. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
driver
test analysis & design tasks
configuration management tools
actual result
9. Examine changes made to an operational system cause defects.
condition determination coverage
maintenance testing
alpha testing
integration management tools
10. Response of the application to an input
LCSAJ
exhaustive testing
control flow structure
action
11. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
test levels
alpha testing
experience-based techniques
testing process phases
12. A review not based on a formal documented procedure
exit criteria
anomalous events
informal review
failure rate
13. Used to replace a component that calls another component.
driver
test analysis & design tasks
control flow structure
IEEE incident report template
14. Testing an integrated system to validate it meets requirements
decision testing
iterative-incremental development models
system testing
actual result
15. Testing software components that are separately testable. Also module program and unit testing.
test levels
component testing
independence of testing
decision testing
16. White-box design technique used to design test cases for a software component using LCSAJ.
LCSAJ testing
IEEE test case specification template
informal review
anomalous events
17. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
test control Tasks
failure rate
waterfall model phases
iterative-incremental development models
18. A functional testing approach in which test cases are designed based on business processes.
testing process phases
anomalous events
test control Tasks
business process-based testing
19. Actual inputs required to execute a test case
functional incremental integration
test management tool features
accuracy
input specifications
20. Sequence in which data items are accessed or modified by code.
data flow structure
equivalence partitions
impact analysis
test levels
21. A component of the incident report that determines the actual effect of the incident on the software and its users.
contract acceptance testing
incident report identifier
impact
debugging tools
22. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
coverage
black-box testing
test execution tasks
business process-based testing
23. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
defect density
maintainability testing
load testing
documentation tools
24. An analysis that determines the portion of code on software executed by a set of test cases
debugging
test control Tasks
code coverage
incident management tools
25. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
test management tool features
horizontal traceability
coverage
waterfall model benefits
26. Conditions required to begin testing activities.
entry criteria
exploratory testing
SW development model
keyword-driven testing
27. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
conditions
nonfunctional requirements
interoperability testing
experience-based techniques
28. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
action
contract acceptance testing
experience-based techniques
accuracy
29. A task of maintaining and controlling changes to all entities of a system.
SW development model
configuration management
backbone integration
error
30. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
environmental needs
testing process phases
beta testing
impact analysis
31. Insertion of additional code in the existing program in order to count coverage items.
decision table
experience-based techniques
instrumentation
data-driven testing
32. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
cyclomatic complexity
agile software development model
test implementation tasks
backbone integration
33. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
component integration testing
integration testing
IEEE test case specification template
exit criteria
34. Special-purpose software used to simulate a component that calls the component under test
integration
component testing
driver
load testing
35. Sequence in which instructions are executed through a component or system
exploratory testing
waterfall model benefits
control flow structure
cause-effect graphic testing
36. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
test execution tasks
defect
contract acceptance testing
exploratory testing
37. Components are integrated in the order in which they are developed
configuration management tools
system testing
ad hoc integration
driver
38. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
test implementation tasks
contract acceptance testing
monitor
interoperability
39. Tools used to store and manage incidents return phone defects failures or anomalies.
test analysis & design tasks
coverage
integration management tools
incident management tools
40. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
waterfall model benefits
boundary value analysis
bottom-up integration
COTS
41. Tests interfaces between components and between integrated components and systems.
actual result
impact
integration testing
maintenance testing
42. Black-box testing technique used to create groups of input conditions that create the same kind of output.
configuration management
big-bang testing
test execution tasks
equivalence partitioning
43. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
incremental testing
monitor
defect masking
LCSAJ testing
44. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
risk-based testing
multiple condition coverage
actual result
stub
45. Testing software in its operational environment
test analysis & design tasks
load testing
operational testing
failure
46. Informal testing technique in which test planning and execution run in parallel
exploratory testing
defect density
defect
maintainability
47. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
driver
interoperability
boundary value analysis
cyclomatic complexity
48. Based on analysis of functional specifications of a system.
exploratory testing
coverage
operational testing
functional testing
49. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
test data preparation tools
test levels
conformance testing tools
integration management tools
50. Special additions or changes to the environment required to run a test case.
multiple condition coverage
equivalence partitions
acceptance testing
environmental needs