SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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. Sequence in which instructions are executed through a component or system
control flow structure
interoperability testing
driver
equivalence partitions
2. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure
decision table testing
LCSAJ testing
testing process phases
stub
3. Develop & proiroitize test cases Create groups of test cases Set up test environment
test implementation tasks
load testing
incident management tools
black-box testing
4. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
bottom-up integration
independence of testing
monitor
cause-effect graphic testing
5. Examine changes made to an operational system cause defects.
maintenance testing
test planning Tasks
cause-effect graphic testing
test execution tasks
6. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).
LCSAJ testing
data-driven testing
error guessing
test log uses
7. Ability of software to provide appropriate performance relative to amount of resources used.
efficiency
acceptance testing
experience-based techniques
backbone integration
8. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers
incident description subheadings
decision table
fault attack
waterfall model phases
9. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)
inspection
functional requirements
failure rate
contract acceptance testing
10. Insertion of additional code in the existing program in order to count coverage items.
contract acceptance testing
instrumentation
incident management tools
defect
11. Based on analysis of functional specifications of a system.
integration
test control Tasks
test implementation tasks
functional testing
12. Calculates the number of executed branch outcomes in code.
inspection
decision coverage
test condition
decision table testing
13. A task of maintaining and controlling changes to all entities of a system.
test control Tasks
code coverage
configuration management
incident management tools
14. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
defect
functional testing tool
incident report
error guessing
15. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.
operational testing
maintainability
interoperability
waterfall model benefits
16. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.
conformance testing tools
incident life cycle phases
incident description subheadings
entry criteria
17. Components are combined and tested in the order in which basic functionalities start working
acceptance testing
data flow structure
functional incremental integration
decision testing
18. An event or item that can be tested using one or more test cases
actual result
data-driven testing
test condition
contract acceptance testing
19. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
boundary value analysis
conformance testing tools
functionality
test analysis & design tasks
20. Testing software in its operational environment
horizontal traceability
LCSAJ
actual result
operational testing
21. A document that records the description of each event that occurs during the testing process and that requires further investigation
exhaustive testing
cause-effect graphic testing
control flow structure
incident report
22. Informal testing technique in which test planning and execution run in parallel
accuracy
exploratory testing
cause-effect graphic testing
nonfunctional requirements
23. A document that provides the structure for writing test cases.
experience-based techniques
cyclomatic complexity
IEEE test case specification template
instrumentation
24. Tools used by developers to identify defects in programs.
incident life cycle phases
debugging tools
entry criteria
anomalous events
25. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
decision testing
component integration testing
decision table
dynamic analysis tools
26. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan
load testing
documentation tools
condition coverage
maintainability
27. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
incident description subheadings
maintainability testing
keyword-driven testing
fault attack
28. Special-purpose software used to simulate a component that calls the component under test
driver
exploratory testing
business process-based testing
IEEE test case specification template
29. Component - Integration - System - Acceptance
test levels
data flow structure
interoperability testing
control flow structure
30. 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
incremental testing
operational testing
defect density
31. Tools used to identify and calculate coverage items in program code.
driver
decision table
maintainability
coverage measurement tools
32. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
boundary value analysis
experience-based techniques
backbone integration
COTS
33. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
backbone integration
interoperability testing
configuration management tools
defect
34. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components
component integration testing
incremental testing
test planning Tasks
black-box testing
35. Measures amount of testing performed by a collection of test cases
backbone integration
coverage
error guessing
IEEE test case specification template
36. Process used to create a SW product from initial conception to public release
bottom-up integration
debugging
coverage measurement tools
SW development model
37. White-box design technique used to design test cases for a software component using LCSAJ.
incident report identifier
condition determination coverage
decision testing
LCSAJ testing
38. A review not based on a formal documented procedure
informal review
documentation tools
defect
LCSAJ
39. Combining components or sytems into larger structural units or subsystems.
failure
independence of testing
integration
black-box testing
40. A component of the incident report that determines the actual effect of the incident on the software and its users.
data-driven testing
cause-effect graphic testing
impact
maintenance testing
41. Used to test the functionality of software as mentioned in software requirement specifications.
error
functional testing tool
test log uses
IEEE test case specification template
42. 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
incident description subheadings
boundary value analysis
equivalence partitions
waterfall model benefits
43. Increased load (transations) used to test behavior of system under high volume.
keyword-driven testing
condition determination coverage
anomalous events
load testing
44. Waterfall iterative-incremental "V"
action
maintenance testing
resolution types
Three main SW development models
45. A set of conditions that a system needs to meet in order to be accepted by end users
acceptance criteria
iterative-incremental development models
conformance testing tools
test levels
46. The capability of a software product to provide agreed and correct output with the required degree of precision
SW development model
cyclomatic complexity
equivalence partitioning
accuracy
47. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.
waterfall model benefits
functionality
functional incremental integration
exhaustive testing
48. Response of the application to an input
anomalous events
action
test log uses
Three main SW development models
49. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
test execution tasks
IEEE test case specification template
incident life cycle phases
operational testing
50. Linear Code Sequence and Jump.
beta testing
incident description subheadings
LCSAJ
incident management tools