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. The ratio between the number of defects found and the size of the component/system tested.
functionality
inspection
defect density
load testing
2. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
test management tool features
test data preparation tools
Incidents
3. Actual inputs required to execute a test case
input specifications
error guessing
horizontal traceability
maintainability testing
4. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
integration management tools
LCSAJ testing
configuration management tools
5. Input or combination of inputs required to test software.
test levels
impact analysis
maintainability testing
conditions
6. A set of conditions that a system needs to meet in order to be accepted by end users
failure
IEEE incident report template
acceptance criteria
system testing
7. Incident Report - Identifier - Summary - Incident - Description - Impact
SW development model
test condition
defect
IEEE incident report template
8. Testing software in its operational environment
exploratory testing
operational testing
test condition
configuration management
9. Specific groups that represent a set of valid or invalid partitions for input conditions.
stub
monitor
exhaustive testing
equivalence partitions
10. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
ad hoc integration
incident report identifier
data-driven testing
11. Special-purpose software used to simulate a component that calls the component under test
driver
exploratory testing
failure rate
condition determination coverage
12. 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
waterfall model benefits
load testing
COTS
test tool deployment Success Factors
13. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
informal review
equivalence partitioning
efficiency
boundary value analysis
14. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
beta testing
driver
accuracy
decision testing
15. Tools used to identify and calculate coverage items in program code.
coverage measurement tools
incident management tools
decision testing
failure rate
16. Sequence in which data items are accessed or modified by code.
LCSAJ testing
test levels
resolution types
data flow structure
17. A task of maintaining and controlling changes to all entities of a system.
configuration management
functional requirements
waterfall model benefits
experience-based techniques
18. A technique used to improve testing coverage by deliberately introducing faults in code.
ad hoc integration
fault attack
test control Tasks
maintainability testing
19. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
cyclomatic complexity
stub
inspection
condition determination coverage
20. Develop & proiroitize test cases Create groups of test cases Set up test environment
decision table
business process-based testing
contract acceptance testing
test implementation tasks
21. Examine changes made to an operational system cause defects.
test analysis & design tasks
maintenance testing
exhaustive testing
business process-based testing
22. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
experience-based techniques
bottom-up integration
black-box testing
condition coverage
23. Requirements that determine the functionality of a software system.
monitor
test analysis & design tasks
functional requirements
agile software development model
24. Special-purpose software used to simulate a component called by the component under test
interoperability
component integration testing
stub
component testing
25. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
documentation tools
big-bang testing
Three main SW development models
26. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
decision table
integration management tools
contract acceptance testing
waterfall model phases
27. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident report
driver
cyclomatic complexity
exit criteria
28. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
impact analysis
Incidents
conformance testing tools
cyclomatic complexity
29. Occurrences that happen before and after an unexpected event
test analysis & design tasks
test management tool features
data-driven testing
anomalous events
30. Special additions or changes to the environment required to run a test case.
error guessing
code coverage
configuration management
environmental needs
31. Increased load (transations) used to test behavior of system under high volume.
incident report
load testing
system testing
defect
32. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
configuration management tools
nonfunctional requirements
decision table
cause-effect graphic testing
33. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
impact
failure rate
configuration management tools
maintainability
34. The smallest software item that can be tested in isolation.
component
incident report
independence of testing
stub
35. Find defects in code while the software application being tested is running.
code coverage
dynamic analysis tools
incident management tools
defect masking
36. A functional testing approach in which test cases are designed based on business processes.
risk-based testing
control flow structure
business process-based testing
integration management tools
37. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
equivalence partitioning
risk-based testing
impact analysis
Three main SW development models
38. Components are combined and tested in the order in which basic functionalities start working
agile software development model
functional incremental integration
failure rate
Three main SW development models
39. Testing an integrated system to validate it meets requirements
system testing
exhaustive testing
IEEE test case specification template
test execution tasks
40. Combining components or sytems into larger structural units or subsystems.
system testing
integration
test data preparation tools
nonfunctional requirements
41. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
anomalous events
incident report identifier
ad hoc integration
42. 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.
SW development model
monitor
inspection
independence of testing
43. Linear Code Sequence and Jump.
test planning Tasks
LCSAJ
test data preparation tools
decision table testing
44. Testing performed to determine whether the system meets acceptance criteria
boundary value analysis
bottom-up integration
acceptance testing
maintainability testing
45. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
data-driven testing
Incidents
resolution types
functional incremental integration
46. A unique identifier for each incident report generated during test execution.
incident report identifier
IEEE incident report template
cyclomatic complexity
system testing
47. Components are integrated in the order in which they are developed
ad hoc integration
incident report
cyclomatic complexity
anomalous events
48. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
stub
component
incident description subheadings
documentation tools
49. The process of finding analyzing and removing causes of failure in a software product.
action
decision coverage
debugging
risk-based testing
50. Process used to create a SW product from initial conception to public release
SW development model
debugging
equivalence partitions
incident report identifier