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. Black-box testing technique used to create groups of input conditions that create the same kind of output.
informal review
equivalence partitioning
functional incremental integration
Incidents
2. Conditions ensuring testing process is complete and the object being tested is ready for next stage.
operational testing
failure
horizontal traceability
exit criteria
3. Tests interfaces between components and between integrated components and systems.
anomalous events
incident description subheadings
test management tool features
integration testing
4. Integrate different kinds of tools to make test management more efficient and simple.
integration management tools
horizontal traceability
debugging
driver
5. Deviation of a software system from its expected delivery services or results
test data preparation tools
failure
independence of testing
Three main SW development models
6. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.
test implementation tasks
nonfunctional requirements
load testing
multiple condition coverage
7. A task of maintaining and controlling changes to all entities of a system.
Impact subheadings
exhaustive testing
nonfunctional requirements
configuration management
8. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.
defect density
fault attack
resolution types
SW development model
9. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
defect density
incident life cycle phases
entry criteria
10. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first
risk-based testing
error guessing
defect density
agile software development model
11. A functional testing approach in which test cases are designed based on business processes.
business process-based testing
condition coverage
configuration management tools
alpha testing
12. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
maintenance testing
conformance testing tools
coverage measurement tools
test data preparation tools
13. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
interoperability testing
iterative-incremental development models
condition coverage
IEEE incident report template
14. Human action that generates an incorrect result.
error
configuration management tools
exit criteria
test implementation tasks
15. Linear Code Sequence and Jump.
incident report identifier
contract acceptance testing
monitor
LCSAJ
16. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
boundary value analysis
testing process phases
Impact subheadings
test log uses
17. Behavior or response of a software application that you observe when you execute the action steps in the test case.
interoperability testing
LCSAJ
actual result
error
18. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports
test management tool features
incident management tools
impact
maintenance testing
19. Testing performed to determine whether the system meets acceptance criteria
functional testing
acceptance testing
LCSAJ testing
maintenance testing
20. Testing an integrated system to validate it meets requirements
defect
keyword-driven testing
system testing
functional testing
21. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
driver
interoperability testing
horizontal traceability
test execution tasks
22. Based on analysis of functional specifications of a system.
informal review
automation tools
functional testing
ad hoc integration
23. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
interoperability testing
control flow structure
LCSAJ
interoperability
24. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect
black-box testing
inspection
incident life cycle phases
25. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing
efficiency
test data preparation tools
test control Tasks
experience-based techniques
26. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
documentation tools
incident description subheadings
alpha testing
27. A component of the incident report that determines the actual effect of the incident on the software and its users.
decision table testing
impact
testing process phases
boundary value analysis
28. Measures amount of testing performed by a collection of test cases
testing process phases
alpha testing
coverage
monitor
29. Combining components or sytems into larger structural units or subsystems.
LCSAJ testing
integration
functional requirements
integration testing
30. White-box design technique used to design test cases for a software component using LCSAJ.
dynamic analysis tools
LCSAJ testing
boundary value analysis
incident life cycle phases
31. A document that provides the structure for writing test cases.
contract acceptance testing
IEEE test case specification template
boundary value analysis
IEEE incident report template
32. The capability of a software product to provide agreed and correct output with the required degree of precision
failure
accuracy
test tool deployment Success Factors
boundary value analysis
33. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.
monitor
interoperability
coverage measurement tools
incident report
34. Ability of software to provide appropriate performance relative to amount of resources used.
cause-effect graphic testing
debugging
functional incremental integration
efficiency
35. Input or combination of inputs required to test software.
failure rate
conditions
decision testing
risk-based testing
36. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables
input specifications
exit criteria
independence of testing
waterfall model benefits
37. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
maintainability
debugging
acceptance testing
operational testing
38. 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
experience-based techniques
coverage
risk-based testing
39. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.
contract acceptance testing
incident description subheadings
Impact subheadings
integration
40. Sequence in which instructions are executed through a component or system
independence of testing
acceptance testing
control flow structure
inspection
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
testing process phases
input specifications
failure
42. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
maintenance testing
test log uses
backbone integration
incremental testing
43. Conditions required to begin testing activities.
risk-based testing
entry criteria
coverage
component testing
44. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
resolution types
functionality
maintainability testing
impact analysis
45. Abilitiy of software to collaborate with one or more specified systems subsystem or components.
stub
beta testing
interoperability
incident life cycle phases
46. Used to test the functionality of software as mentioned in software requirement specifications.
functional testing tool
functionality
incident report
COTS
47. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.
condition determination coverage
big-bang testing
test implementation tasks
conditions
48. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.
nonfunctional requirements
incident report
SW development model
waterfall model benefits
49. A unique identifier for each incident report generated during test execution.
monitor
component integration testing
load testing
incident report identifier
50. 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).
configuration management tools
action
maintainability
waterfall model benefits