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 unique identifier for each incident report generated during test execution.
test levels
incident report identifier
incident management tools
nonfunctional requirements
2. Testing software in its operational environment
operational testing
incident report identifier
failure rate
conditions
3. Conditions required to begin testing activities.
entry criteria
fault attack
interoperability testing
accuracy
4. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
coverage
configuration management
black-box testing
interoperability testing
5. An event or item that can be tested using one or more test cases
test condition
maintenance testing
failure
anomalous events
6. Tools used by developers to identify defects in programs.
alpha testing
functional testing tool
functionality
debugging tools
7. An analysis that determines the portion of code on software executed by a set of test cases
test implementation tasks
code coverage
component
backbone integration
8. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
exit criteria
failure rate
entry criteria
accuracy
9. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
experience-based techniques
integration management tools
component
actual result
10. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
interoperability
coverage measurement tools
instrumentation
error guessing
11. Events that occurred during the testing process our investigation.
Incidents
IEEE test case specification template
test condition
backbone integration
12. Informal testing technique in which test planning and execution run in parallel
interoperability testing
functional requirements
exploratory testing
test planning Tasks
13. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
test log uses
boundary value analysis
black-box testing
test data preparation tools
14. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
impact analysis
test tool deployment Success Factors
equivalence partitions
multiple condition coverage
15. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
incident description subheadings
condition determination coverage
component integration testing
decision table
16. Testing software components that are separately testable. Also module program and unit testing.
component testing
Three main SW development models
condition coverage
coverage
17. Calculates the number of executed branch outcomes in code.
decision table testing
driver
maintainability testing
decision coverage
18. A table showing combinations of inputs and their associated actions.
data flow structure
decision table
dynamic analysis tools
error guessing
19. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
informal review
test planning Tasks
interoperability
integration testing
20. Tools used to store and manage incidents return phone defects failures or anomalies.
test condition
code coverage
incident management tools
fault attack
21. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
incident report identifier
maintainability testing
driver
22. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
actual result
waterfall model phases
conditions
test implementation tasks
23. Waterfall iterative-incremental "V"
Three main SW development models
decision table
maintainability testing
COTS
24. Linear Code Sequence and Jump.
decision testing
anomalous events
LCSAJ
IEEE test case specification template
25. Increased load (transations) used to test behavior of system under high volume.
defect
load testing
test log uses
horizontal traceability
26. 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.
Three main SW development models
impact analysis
inspection
ad hoc integration
27. 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.
system testing
bottom-up integration
exit criteria
defect masking
28. Human action that generates an incorrect result.
test execution tasks
integration management tools
cause-effect graphic testing
error
29. Testing an integrated system to validate it meets requirements
black-box testing
exit criteria
system testing
integration testing
30. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
acceptance testing
COTS
integration testing
31. Special-purpose software used to simulate a component called by the component under test
fault attack
incident life cycle phases
component
stub
32. Components are integrated in the order in which they are developed
dynamic analysis tools
input specifications
ad hoc integration
error
33. Used to replace a component that calls another component.
driver
Incidents
input specifications
exhaustive testing
34. 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
code coverage
efficiency
defect
35. Input or combination of inputs required to test software.
iterative-incremental development models
conditions
integration testing
defect masking
36. One defect prevents the detection of another.
defect masking
test planning Tasks
exit criteria
interoperability
37. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
impact analysis
functionality
horizontal traceability
functional incremental integration
38. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
nonfunctional requirements
component
backbone integration
bottom-up integration
39. A task of maintaining and controlling changes to all entities of a system.
test levels
configuration management
acceptance testing
test implementation tasks
40. Components are combined and tested in the order in which basic functionalities start working
actual result
maintainability
operational testing
functional incremental integration
41. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
cyclomatic complexity
instrumentation
monitor
dynamic analysis tools
42. Black-box testing technique used to create groups of input conditions that create the same kind of output.
equivalence partitioning
functional incremental integration
agile software development model
test planning Tasks
43. Sequence in which data items are accessed or modified by code.
horizontal traceability
incident report
defect masking
data flow structure
44. The ratio between the number of defects found and the size of the component/system tested.
independence of testing
code coverage
operational testing
defect density
45. 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 condition
test tool deployment Success Factors
test log uses
decision testing
46. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
coverage
nonfunctional requirements
component testing
component integration testing
47. Black-box test design technique - test cases are designed from a decision table.
load testing
Incidents
business process-based testing
decision table testing
48. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
control flow structure
defect
interoperability testing
agile software development model
49. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
error guessing
input specifications
impact analysis
incident life cycle phases
50. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
interoperability
stub
failure rate
decision coverage