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. A technique used to improve testing coverage by deliberately introducing faults in code.
LCSAJ testing
beta testing
fault attack
test levels
2. Software products or applications designed to automate manual testing tasks.
equivalence partitions
functional testing
automation tools
risk-based testing
3. Component - Integration - System - Acceptance
big-bang testing
test levels
decision table testing
IEEE incident report template
4. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
condition coverage
inspection
test planning Tasks
alpha testing
5. Operational testing performed at an _external_ site without involvement of the developing organization.
beta testing
condition coverage
big-bang testing
resolution types
6. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
code coverage
testing process phases
defect
maintenance testing
7. Develop & proiroitize test cases Create groups of test cases Set up test environment
component integration testing
test tool deployment Success Factors
test implementation tasks
test log uses
8. 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 analysis & design tasks
failure rate
acceptance criteria
test tool deployment Success Factors
9. Process used to create a SW product from initial conception to public release
SW development model
driver
documentation tools
interoperability testing
10. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
entry criteria
COTS
driver
contract acceptance testing
11. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
exit criteria
accuracy
contract acceptance testing
iterative-incremental development models
12. Response of the application to an input
action
anomalous events
error guessing
test log uses
13. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
defect
integration testing
multiple condition coverage
functional incremental integration
14. Based on analysis of functional specifications of a system.
failure
functional testing
code coverage
IEEE incident report template
15. 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
action
independence of testing
data flow structure
test planning Tasks
16. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
Impact subheadings
keyword-driven testing
boundary value analysis
IEEE incident report template
17. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
integration testing
maintainability testing
functional testing
18. Testing software in its operational environment
instrumentation
operational testing
maintainability testing
load testing
19. Measures amount of testing performed by a collection of test cases
coverage
exploratory testing
input specifications
cyclomatic complexity
20. Black-box test design technique - test cases are designed from a decision table.
integration testing
data flow structure
instrumentation
decision table testing
21. Calculates the number of executed branch outcomes in code.
incident description subheadings
decision coverage
exhaustive testing
alpha testing
22. 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
conditions
decision table testing
condition coverage
23. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
interoperability
black-box testing
LCSAJ
test control Tasks
24. Occurrences that happen before and after an unexpected event
control flow structure
anomalous events
driver
system testing
25. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).
incident life cycle phases
conformance testing tools
multiple condition coverage
configuration management tools
26. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
test tool deployment Success Factors
multiple condition coverage
configuration management tools
27. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
conformance testing tools
impact analysis
accuracy
risk-based testing
28. Events that occurred during the testing process our investigation.
configuration management
action
dynamic analysis tools
Incidents
29. Specific groups that represent a set of valid or invalid partitions for input conditions.
defect
equivalence partitions
incident life cycle phases
impact
30. Separation of testing responsibilities which encourages the accomplishment of objective testing
defect density
independence of testing
incident description subheadings
test execution tasks
31. Conditions required to begin testing activities.
decision table testing
entry criteria
iterative-incremental development models
component
32. 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
test tool deployment Success Factors
waterfall model benefits
LCSAJ testing
nonfunctional requirements
33. Tools used by developers to identify defects in programs.
debugging tools
multiple condition coverage
informal review
coverage measurement tools
34. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
accuracy
black-box testing
contract acceptance testing
conformance testing tools
35. Incident Report - Identifier - Summary - Incident - Description - Impact
IEEE incident report template
impact
integration
testing process phases
36. Used to replace a component that calls another component.
decision testing
driver
component integration testing
failure
37. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
code coverage
incident description subheadings
cyclomatic complexity
stub
38. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
incident description subheadings
acceptance testing
interoperability testing
incremental testing
39. A unique identifier for each incident report generated during test execution.
test levels
test tool deployment Success Factors
Impact subheadings
incident report identifier
40. Black-box testing technique used to create groups of input conditions that create the same kind of output.
actual result
component testing
equivalence partitioning
input specifications
41. Ability of software to provide appropriate performance relative to amount of resources used.
IEEE test case specification template
efficiency
Incidents
configuration management tools
42. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
defect masking
component
test analysis & design tasks
test control Tasks
43. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
maintainability testing
test tool deployment Success Factors
nonfunctional requirements
coverage
44. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
decision testing
interoperability testing
coverage measurement tools
integration testing
45. Special-purpose software used to simulate a component called by the component under test
exploratory testing
coverage
stub
multiple condition coverage
46. Human action that generates an incorrect result.
functionality
business process-based testing
error
impact
47. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
incident life cycle phases
system testing
defect
resolution types
48. One defect prevents the detection of another.
defect masking
resolution types
decision coverage
component integration testing
49. Used to test the functionality of software as mentioned in software requirement specifications.
data-driven testing
LCSAJ testing
functional testing tool
dynamic analysis tools
50. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
functional requirements
entry criteria
resolution types
cause-effect graphic testing