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 code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
equivalence partitions
configuration management
IEEE incident report template
cyclomatic complexity
2. Waterfall iterative-incremental "V"
boundary value analysis
maintainability
Three main SW development models
integration
3. The capability of a software product to provide agreed and correct output with the required degree of precision
impact analysis
test execution tasks
accuracy
LCSAJ
4. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
acceptance criteria
experience-based techniques
test log uses
ad hoc integration
5. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
Three main SW development models
condition coverage
resolution types
risk-based testing
6. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
iterative-incremental development models
test tool deployment Success Factors
functional requirements
backbone integration
7. 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
decision testing
incident report identifier
informal review
test tool deployment Success Factors
8. Used to replace a component that calls another component.
system testing
driver
functional requirements
entry criteria
9. Black-box testing technique used to create groups of input conditions that create the same kind of output.
exploratory testing
documentation tools
data flow structure
equivalence partitioning
10. Integrate different kinds of tools to make test management more efficient and simple.
documentation tools
integration management tools
iterative-incremental development models
agile software development model
11. Special-purpose software used to simulate a component called by the component under test
test condition
defect masking
stub
system testing
12. A table showing combinations of inputs and their associated actions.
test condition
acceptance criteria
decision table
exhaustive testing
13. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.
instrumentation
failure rate
debugging tools
decision testing
14. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
instrumentation
interoperability
functionality
15. Conditions required to begin testing activities.
entry criteria
equivalence partitions
failure rate
actual result
16. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
black-box testing
functional testing
testing process phases
17. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
SW development model
conformance testing tools
condition coverage
integration testing
18. Testing performed to determine whether the system meets acceptance criteria
acceptance testing
test execution tasks
exhaustive testing
dynamic analysis tools
19. Requirements that determine the functionality of a software system.
nonfunctional requirements
functional requirements
equivalence partitioning
interoperability testing
20. A unique identifier for each incident report generated during test execution.
decision testing
interoperability
test implementation tasks
incident report identifier
21. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
action
environmental needs
component integration testing
22. 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
agile software development model
LCSAJ testing
system testing
defect masking
23. One defect prevents the detection of another.
decision table testing
decision table
IEEE incident report template
defect masking
24. Allows storage of test input and expected results in one or more central data sources or databases.
input specifications
acceptance criteria
data-driven testing
maintenance testing
25. A document that records the description of each event that occurs during the testing process and that requires further investigation
waterfall model phases
IEEE incident report template
equivalence partitioning
incident report
26. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect masking
defect
debugging
instrumentation
27. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
data-driven testing
failure
documentation tools
28. Input or combination of inputs required to test software.
conditions
agile software development model
resolution types
load testing
29. 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
driver
test data preparation tools
failure rate
interoperability
30. 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
iterative-incremental development models
IEEE test case specification template
environmental needs
31. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
SW development model
decision testing
conformance testing tools
functionality
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
LCSAJ
action
test control Tasks
entry criteria
33. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
independence of testing
defect masking
entry criteria
incremental testing
34. Tools used to store and manage incidents return phone defects failures or anomalies.
incident management tools
nonfunctional requirements
integration testing
contract acceptance testing
35. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
functional testing
documentation tools
fault attack
36. Human action that generates an incorrect result.
error
acceptance criteria
test execution tasks
entry criteria
37. Component - Integration - System - Acceptance
component testing
functional incremental integration
fault attack
test levels
38. The ratio between the number of defects found and the size of the component/system tested.
keyword-driven testing
input specifications
defect density
contract acceptance testing
39. An event or item that can be tested using one or more test cases
test condition
agile software development model
test levels
error guessing
40. Integration approach components or subsystems are combined all at once rather than in stages.
big-bang testing
action
efficiency
acceptance testing
41. Behavior or response of a software application that you observe when you execute the action steps in the test case.
error guessing
defect masking
horizontal traceability
actual result
42. A document that provides the structure for writing test cases.
waterfall model phases
IEEE test case specification template
iterative-incremental development models
test implementation tasks
43. A functional testing approach in which test cases are designed based on business processes.
acceptance testing
driver
agile software development model
business process-based testing
44. 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
boundary value analysis
configuration management tools
decision table
test planning Tasks
45. A review not based on a formal documented procedure
informal review
component testing
data-driven testing
risk-based testing
46. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
debugging tools
boundary value analysis
anomalous events
multiple condition coverage
47. Testing an integrated system to validate it meets requirements
system testing
configuration management tools
decision table
action
48. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
big-bang testing
LCSAJ testing
test execution tasks
load testing
49. Specific groups that represent a set of valid or invalid partitions for input conditions.
data flow structure
incident life cycle phases
equivalence partitions
entry criteria
50. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
maintainability
interoperability testing
LCSAJ testing
integration