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. Waterfall iterative-incremental "V"
decision testing
incident report
Three main SW development models
equivalence partitioning
2. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
test analysis & design tasks
environmental needs
maintainability
efficiency
3. Tests interfaces between components and between integrated components and systems.
Impact subheadings
code coverage
integration testing
component testing
4. Behavior or response of a software application that you observe when you execute the action steps in the test case.
ad hoc integration
actual result
data flow structure
waterfall model benefits
5. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
resolution types
incident management tools
data-driven testing
test data preparation tools
6. Components are combined and tested in the order in which basic functionalities start working
functional incremental integration
condition coverage
driver
test control Tasks
7. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
Impact subheadings
keyword-driven testing
conformance testing tools
incremental testing
8. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
component integration testing
test tool deployment Success Factors
keyword-driven testing
maintainability
9. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
dynamic analysis tools
incident management tools
functionality
coverage measurement tools
10. A review not based on a formal documented procedure
cyclomatic complexity
experience-based techniques
informal review
bottom-up integration
11. 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 coverage
contract acceptance testing
test tool deployment Success Factors
risk-based testing
12. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
COTS
agile software development model
waterfall model benefits
dynamic analysis tools
13. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
fault attack
condition coverage
acceptance testing
interoperability testing
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.
incremental testing
decision table
driver
decision testing
15. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
test control Tasks
impact analysis
risk-based testing
data-driven testing
16. Occurrences that happen before and after an unexpected event
input specifications
business process-based testing
incremental testing
anomalous events
17. A unique identifier for each incident report generated during test execution.
incident report identifier
load testing
incident report
conditions
18. Sequence in which instructions are executed through a component or system
control flow structure
automation tools
anomalous events
defect masking
19. Severity - Priority
contract acceptance testing
Impact subheadings
bottom-up integration
nonfunctional requirements
20. Input or combination of inputs required to test software.
test planning Tasks
beta testing
equivalence partitions
conditions
21. A component of the incident report that determines the actual effect of the incident on the software and its users.
impact
anomalous events
control flow structure
nonfunctional requirements
22. Measures amount of testing performed by a collection of test cases
black-box testing
coverage
equivalence partitioning
condition coverage
23. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
testing process phases
test control Tasks
cause-effect graphic testing
incident description subheadings
24. Sequence in which data items are accessed or modified by code.
equivalence partitioning
alpha testing
test control Tasks
data flow structure
25. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
conformance testing tools
condition coverage
agile software development model
component integration testing
26. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
resolution types
IEEE incident report template
incident life cycle phases
27. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
backbone integration
failure rate
cause-effect graphic testing
LCSAJ testing
28. Human action that generates an incorrect result.
big-bang testing
coverage
condition coverage
error
29. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
bottom-up integration
functional testing
cause-effect graphic testing
test analysis & design tasks
30. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
error
monitor
alpha testing
functional incremental integration
31. White-box design technique used to design test cases for a software component using LCSAJ.
component integration testing
incident report identifier
LCSAJ testing
monitor
32. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
resolution types
black-box testing
decision testing
incremental testing
33. Examine changes made to an operational system cause defects.
anomalous events
Incidents
horizontal traceability
maintenance testing
34. Informal testing technique in which test planning and execution run in parallel
exploratory testing
Impact subheadings
integration
beta testing
35. One defect prevents the detection of another.
IEEE incident report template
inspection
load testing
defect masking
36. Used to test the functionality of software as mentioned in software requirement specifications.
independence of testing
functional testing tool
impact analysis
boundary value analysis
37. Deviation of a software system from its expected delivery services or results
entry criteria
load testing
cause-effect graphic testing
failure
38. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
incident life cycle phases
acceptance testing
maintainability testing
system testing
39. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
keyword-driven testing
error
test analysis & design tasks
40. Integration approach components or subsystems are combined all at once rather than in stages.
incident report identifier
acceptance criteria
operational testing
big-bang testing
41. An analysis that determines the portion of code on software executed by a set of test cases
LCSAJ
coverage
code coverage
defect density
42. Tools used to store and manage incidents return phone defects failures or anomalies.
equivalence partitions
agile software development model
integration
incident management tools
43. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
exhaustive testing
defect
black-box testing
decision coverage
44. 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
input specifications
big-bang testing
monitor
45. Component - Integration - System - Acceptance
automation tools
test log uses
test levels
anomalous events
46. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
backbone integration
cyclomatic complexity
inspection
test management tool features
47. Special additions or changes to the environment required to run a test case.
automation tools
maintenance testing
acceptance criteria
environmental needs
48. A set of conditions that a system needs to meet in order to be accepted by end users
failure rate
acceptance criteria
coverage
component integration testing
49. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component testing
component integration testing
inspection
test control Tasks
50. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.
boundary value analysis
incident report identifier
impact analysis
configuration management tools