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. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
coverage measurement tools
condition determination coverage
test data preparation tools
impact analysis
2. Testing software components that are separately testable. Also module program and unit testing.
component testing
integration testing
test management tool features
decision table
3. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
big-bang testing
test management tool features
coverage
condition determination coverage
4. Input or combination of inputs required to test software.
test data preparation tools
entry criteria
conditions
cause-effect graphic testing
5. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.
condition coverage
interoperability testing
Impact subheadings
instrumentation
6. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
testing process phases
dynamic analysis tools
configuration management tools
multiple condition coverage
7. The smallest software item that can be tested in isolation.
operational testing
maintenance testing
component
COTS
8. Combining components or sytems into larger structural units or subsystems.
impact analysis
exit criteria
debugging tools
integration
9. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).
big-bang testing
integration
configuration management tools
acceptance testing
10. A set of conditions that a system needs to meet in order to be accepted by end users
impact
coverage measurement tools
acceptance criteria
alpha testing
11. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
incremental testing
configuration management tools
entry criteria
12. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
risk-based testing
cause-effect graphic testing
incident description subheadings
documentation tools
13. A task of maintaining and controlling changes to all entities of a system.
agile software development model
data flow structure
component testing
configuration management
14. 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.
coverage
equivalence partitioning
bottom-up integration
driver
15. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance
waterfall model phases
iterative-incremental development models
maintainability
LCSAJ
16. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
maintainability testing
resolution types
functionality
environmental needs
17. 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 log uses
test control Tasks
entry criteria
18. Requirements that determine the functionality of a software system.
decision table testing
functional requirements
defect
integration
19. A document that records the description of each event that occurs during the testing process and that requires further investigation
incident life cycle phases
failure rate
incident report
equivalence partitions
20. Based on analysis of functional specifications of a system.
exhaustive testing
entry criteria
functional testing
decision coverage
21. Develop & proiroitize test cases Create groups of test cases Set up test environment
iterative-incremental development models
test implementation tasks
dynamic analysis tools
Impact subheadings
22. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
error
incident life cycle phases
contract acceptance testing
test planning Tasks
23. Deviation of a software system from its expected delivery services or results
failure
waterfall model benefits
Impact subheadings
anomalous events
24. Informal testing technique in which test planning and execution run in parallel
exit criteria
Three main SW development models
contract acceptance testing
exploratory testing
25. Occurrences that happen before and after an unexpected event
SW development model
interoperability
driver
anomalous events
26. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
incident report identifier
horizontal traceability
cause-effect graphic testing
cyclomatic complexity
27. Calculates the number of executed branch outcomes in code.
conditions
Three main SW development models
condition determination coverage
decision coverage
28. The ratio between the number of defects found and the size of the component/system tested.
test control Tasks
control flow structure
defect density
decision testing
29. Tools used by developers to identify defects in programs.
debugging tools
test levels
anomalous events
failure rate
30. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
integration testing
test control Tasks
keyword-driven testing
defect
31. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
multiple condition coverage
iterative-incremental development models
exhaustive testing
32. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
exploratory testing
resolution types
LCSAJ
input specifications
33. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
integration
coverage
defect
functional requirements
34. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
component integration testing
monitor
fault attack
iterative-incremental development models
35. Linear Code Sequence and Jump.
LCSAJ
Three main SW development models
incident description subheadings
test tool deployment Success Factors
36. The capability of a software product to provide agreed and correct output with the required degree of precision
test analysis & design tasks
accuracy
waterfall model benefits
decision testing
37. Sequence in which data items are accessed or modified by code.
data flow structure
decision coverage
defect density
functionality
38. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.
integration management tools
cyclomatic complexity
test execution tasks
control flow structure
39. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
alpha testing
acceptance criteria
incident description subheadings
40. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
interoperability testing
exhaustive testing
conformance testing tools
integration testing
41. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)
decision testing
alpha testing
load testing
testing process phases
42. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
interoperability
integration
incident description subheadings
decision coverage
43. Insertion of additional code in the existing program in order to count coverage items.
instrumentation
defect
multiple condition coverage
acceptance 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
test tool deployment Success Factors
efficiency
dynamic analysis tools
driver
45. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
accuracy
maintenance testing
contract acceptance testing
Impact subheadings
46. One defect prevents the detection of another.
acceptance testing
component integration testing
defect masking
operational testing
47. Specific groups that represent a set of valid or invalid partitions for input conditions.
risk-based testing
equivalence partitions
exhaustive testing
defect masking
48. Components are combined and tested in the order in which basic functionalities start working
stub
maintainability testing
cause-effect graphic testing
functional incremental integration
49. Component - Integration - System - Acceptance
boundary value analysis
IEEE test case specification template
efficiency
test levels
50. Record details of test cases executed Record order of execution record results
incident report
fault attack
impact analysis
test log uses