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. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
resolution types
integration management tools
data flow structure
maintainability
2. The ratio between the number of defects found and the size of the component/system tested.
functional incremental integration
defect density
functional requirements
debugging tools
3. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
backbone integration
conditions
cause-effect graphic testing
nonfunctional requirements
4. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
operational testing
test implementation tasks
cyclomatic complexity
waterfall model benefits
5. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.
test condition
inspection
fault attack
conditions
6. Testing performed to determine whether the system meets acceptance criteria
informal review
coverage
interoperability
acceptance testing
7. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
actual result
iterative-incremental development models
functional incremental integration
8. A component of the incident report that determines the actual effect of the incident on the software and its users.
environmental needs
impact
functional incremental integration
incident description subheadings
9. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
contract acceptance testing
error guessing
integration
iterative-incremental development models
10. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
dynamic analysis tools
condition coverage
operational testing
integration
11. 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.
incremental testing
bottom-up integration
integration
maintainability testing
12. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
defect
test management tool features
multiple condition coverage
nonfunctional requirements
13. Linear Code Sequence and Jump.
Incidents
horizontal traceability
LCSAJ
experience-based techniques
14. Examine changes made to an operational system cause defects.
driver
anomalous events
equivalence partitions
maintenance testing
15. A task of maintaining and controlling changes to all entities of a system.
configuration management
input specifications
business process-based testing
maintainability testing
16. Special-purpose software used to simulate a component that calls the component under test
boundary value analysis
driver
informal review
coverage measurement tools
17. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
integration
integration management tools
IEEE test case specification template
decision testing
18. Occurrences that happen before and after an unexpected event
fault attack
code coverage
instrumentation
anomalous events
19. White-box design technique used to design test cases for a software component using LCSAJ.
risk-based testing
incident description subheadings
impact
LCSAJ testing
20. Behavior or response of a software application that you observe when you execute the action steps in the test case.
conditions
configuration management tools
condition determination coverage
actual result
21. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
functional incremental integration
Impact subheadings
incident description subheadings
22. Special additions or changes to the environment required to run a test case.
environmental needs
maintenance testing
Incidents
cause-effect graphic testing
23. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
test data preparation tools
waterfall model phases
bottom-up integration
incident management tools
24. 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
test data preparation tools
agile software development model
defect density
testing process phases
25. Testing software components that are separately testable. Also module program and unit testing.
impact
testing process phases
component testing
iterative-incremental development models
26. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
test tool deployment Success Factors
incident report identifier
configuration management
testing process phases
27. Integrate different kinds of tools to make test management more efficient and simple.
test execution tasks
integration management tools
fault attack
bottom-up integration
28. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
control flow structure
debugging tools
stub
29. Operational testing performed at an _external_ site without involvement of the developing organization.
testing process phases
IEEE test case specification template
beta testing
maintainability testing
30. Based on analysis of functional specifications of a system.
integration management tools
maintainability
functional testing
ad hoc integration
31. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
acceptance testing
bottom-up integration
error guessing
32. 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 execution tasks
system testing
component
33. Used to test the functionality of software as mentioned in software requirement specifications.
efficiency
test analysis & design tasks
waterfall model benefits
functional testing tool
34. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
decision testing
iterative-incremental development models
functional testing tool
defect
35. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
alpha testing
incident description subheadings
decision testing
36. The capability of a software product to provide agreed and correct output with the required degree of precision
agile software development model
COTS
accuracy
data-driven testing
37. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
system testing
integration testing
stub
38. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
alpha testing
interoperability testing
load testing
multiple condition coverage
39. Requirements that determine the functionality of a software system.
incident management tools
data-driven testing
functional requirements
decision coverage
40. Calculates the number of executed branch outcomes in code.
accuracy
decision coverage
defect density
exploratory testing
41. Human action that generates an incorrect result.
LCSAJ testing
risk-based testing
error
functional incremental integration
42. Black-box test design technique - test cases are designed from a decision table.
test data preparation tools
decision table testing
cyclomatic complexity
code coverage
43. Component - Integration - System - Acceptance
defect
component testing
test levels
coverage measurement tools
44. Tools used to store and manage incidents return phone defects failures or anomalies.
error guessing
control flow structure
IEEE incident report template
incident management tools
45. Increased load (transations) used to test behavior of system under high volume.
component integration testing
impact
load testing
inspection
46. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template
backbone integration
debugging
test data preparation tools
data flow structure
47. Response of the application to an input
acceptance testing
functional requirements
cause-effect graphic testing
action
48. Process used to create a SW product from initial conception to public release
SW development model
environmental needs
defect
configuration management
49. Black-box testing technique used to create groups of input conditions that create the same kind of output.
IEEE test case specification template
equivalence partitioning
actual result
cause-effect graphic testing
50. Events that occurred during the testing process our investigation.
Incidents
failure rate
accuracy
keyword-driven testing