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. Testing software in its operational environment
incident management tools
operational testing
integration
integration testing
2. Occurrences that happen before and after an unexpected event
alpha testing
incident report identifier
anomalous events
iterative-incremental development models
3. An event or item that can be tested using one or more test cases
code coverage
SW development model
test condition
contract acceptance testing
4. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
conditions
functional requirements
test levels
impact analysis
5. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
defect
IEEE incident report template
test planning Tasks
monitor
6. Input or combination of inputs required to test software.
conditions
test control Tasks
Three main SW development models
acceptance criteria
7. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
multiple condition coverage
test execution tasks
conformance testing tools
integration
8. A set of conditions that a system needs to meet in order to be accepted by end users
waterfall model benefits
dynamic analysis tools
acceptance criteria
condition coverage
9. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
input specifications
test execution tasks
incident report identifier
keyword-driven testing
10. 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
action
test data preparation tools
test planning Tasks
11. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
condition coverage
coverage measurement tools
test tool deployment Success Factors
12. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
conditions
defect masking
test implementation tasks
13. Tools used to store and manage incidents return phone defects failures or anomalies.
test log uses
failure
functional incremental integration
incident management tools
14. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
failure
maintenance testing
cyclomatic complexity
informal review
15. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
functional testing
waterfall model benefits
risk-based testing
agile software development model
16. Separation of testing responsibilities which encourages the accomplishment of objective testing
entry criteria
iterative-incremental development models
failure rate
independence of testing
17. A functional testing approach in which test cases are designed based on business processes.
code coverage
business process-based testing
debugging tools
environmental needs
18. Severity - Priority
defect density
equivalence partitioning
condition coverage
Impact subheadings
19. A review not based on a formal documented procedure
informal review
test analysis & design tasks
exit criteria
automation tools
20. Incident Report - Identifier - Summary - Incident - Description - Impact
conditions
data flow structure
driver
IEEE incident report template
21. Special-purpose software used to simulate a component called by the component under test
decision testing
stub
nonfunctional requirements
IEEE test case specification template
22. Combining components or sytems into larger structural units or subsystems.
integration
condition coverage
component
bottom-up integration
23. Deviation of a software system from its expected delivery services or results
failure
load testing
testing process phases
exhaustive testing
24. Tools used by developers to identify defects in programs.
risk-based testing
debugging tools
efficiency
functional requirements
25. 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.
bottom-up integration
incident description subheadings
decision testing
environmental needs
26. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
waterfall model benefits
maintainability
incident report
alpha testing
27. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
equivalence partitioning
conformance testing tools
integration management tools
waterfall model phases
28. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
monitor
black-box testing
functional testing
error
29. Used to test the functionality of software as mentioned in software requirement specifications.
IEEE test case specification template
incident report
maintainability
functional testing tool
30. Record details of test cases executed Record order of execution record results
test log uses
impact analysis
black-box testing
horizontal traceability
31. A component of the incident report that determines the actual effect of the incident on the software and its users.
Incidents
impact
component testing
condition determination coverage
32. Actual inputs required to execute a test case
control flow structure
COTS
test execution tasks
input specifications
33. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
test log uses
test management tool features
actual result
34. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
fault attack
horizontal traceability
defect masking
waterfall model phases
35. Component - Integration - System - Acceptance
acceptance testing
test levels
control flow structure
test tool deployment Success Factors
36. 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
component integration testing
waterfall model benefits
decision testing
incident life cycle phases
37. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
nonfunctional requirements
incident management tools
condition coverage
alpha testing
38. Increased load (transations) used to test behavior of system under high volume.
load testing
exit criteria
COTS
action
39. Integrate different kinds of tools to make test management more efficient and simple.
error guessing
LCSAJ
integration management tools
component testing
40. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
automation tools
bottom-up integration
acceptance criteria
41. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
conditions
functional incremental integration
equivalence partitioning
boundary value analysis
42. Calculates the number of executed branch outcomes in code.
accuracy
decision coverage
black-box testing
incident report identifier
43. The ratio between the number of defects found and the size of the component/system tested.
horizontal traceability
defect density
decision coverage
LCSAJ testing
44. 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
keyword-driven testing
informal review
LCSAJ
test tool deployment Success Factors
45. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
integration testing
agile software development model
documentation tools
bottom-up integration
46. Conditions required to begin testing activities.
entry criteria
action
backbone integration
incident life cycle phases
47. 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
functional incremental integration
component integration testing
agile software development model
test planning Tasks
48. Develop & proiroitize test cases Create groups of test cases Set up test environment
waterfall model phases
maintainability
test implementation tasks
contract acceptance testing
49. Black-box test design technique - test cases are designed from a decision table.
acceptance testing
component integration testing
big-bang testing
decision table testing
50. Requirements that determine the functionality of a software system.
entry criteria
functional requirements
agile software development model
LCSAJ testing