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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.
Impact subheadings
interoperability testing
boundary value analysis
defect density
2. Allows storage of test input and expected results in one or more central data sources or databases.
data-driven testing
defect
input specifications
test control Tasks
3. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations
agile software development model
decision testing
dynamic analysis tools
IEEE test case specification template
4. White-box design technique used to design test cases for a software component using LCSAJ.
coverage measurement tools
maintenance testing
LCSAJ testing
black-box testing
5. A functional testing approach in which test cases are designed based on business processes.
accuracy
coverage measurement tools
business process-based testing
acceptance testing
6. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.
component testing
iterative-incremental development models
configuration management tools
operational testing
7. Integration approach components or subsystems are combined all at once rather than in stages.
inspection
boundary value analysis
anomalous events
big-bang testing
8. Used to replace a component that calls another component.
driver
component testing
efficiency
accuracy
9. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.
integration testing
defect
automation tools
maintainability
10. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram
anomalous events
cause-effect graphic testing
condition determination coverage
functional testing
11. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes
configuration management tools
LCSAJ
actual result
test execution tasks
12. Process used to create a SW product from initial conception to public release
fault attack
SW development model
contract acceptance testing
coverage
13. Calculates the number of executed branch outcomes in code.
decision coverage
Three main SW development models
functional incremental integration
impact
14. Behavior or response of a software application that you observe when you execute the action steps in the test case.
multiple condition coverage
actual result
incremental testing
defect masking
15. Actual inputs required to execute a test case
experience-based techniques
input specifications
LCSAJ
dynamic analysis tools
16. Tracing requirements for a level of testing using test documentation from the test plan to the test script.
horizontal traceability
input specifications
test implementation tasks
incident description subheadings
17. 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.
agile software development model
interoperability testing
bottom-up integration
SW development model
18. Tests interfaces between components and between integrated components and systems.
integration management tools
integration testing
entry criteria
test implementation tasks
19. Combining components or sytems into larger structural units or subsystems.
integration
entry criteria
actual result
test analysis & design tasks
20. Integration Approach: A frame or backbone is created and components are progressively integrated into it.
code coverage
test execution tasks
exhaustive testing
backbone integration
21. Components are combined and tested in the order in which basic functionalities start working
fault attack
backbone integration
functional testing
functional incremental integration
22. Requirements that determine the functionality of a software system.
anomalous events
input specifications
exploratory testing
functional requirements
23. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.
instrumentation
COTS
action
testing process phases
24. Conditions required to begin testing activities.
documentation tools
impact analysis
independence of testing
entry criteria
25. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".
component integration testing
exit criteria
horizontal traceability
business process-based testing
26. Record details of test cases executed Record order of execution record results
keyword-driven testing
test log uses
alpha testing
coverage
27. Severity - Priority
environmental needs
Impact subheadings
test log uses
decision coverage
28. A technique used to improve testing coverage by deliberately introducing faults in code.
fault attack
business process-based testing
independence of testing
defect masking
29. Increased load (transations) used to test behavior of system under high volume.
incident description subheadings
load testing
keyword-driven testing
equivalence partitioning
30. An analysis that determines the portion of code on software executed by a set of test cases
decision testing
code coverage
exploratory testing
Three main SW development models
31. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance
component testing
maintainability testing
fault attack
waterfall model phases
32. Examine changes made to an operational system cause defects.
maintenance testing
configuration management
independence of testing
environmental needs
33. 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
integration testing
documentation tools
exit criteria
waterfall model benefits
34. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools
component testing
defect
test analysis & design tasks
integration management tools
35. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed
incident life cycle phases
equivalence partitions
test implementation tasks
configuration management
36. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.
action
test execution tasks
coverage measurement tools
impact analysis
37. Separation of testing responsibilities which encourages the accomplishment of objective testing
independence of testing
nonfunctional requirements
test log uses
input specifications
38. All possible combinations of input values and preconditions are tested.
actual result
IEEE incident report template
exhaustive testing
functional requirements
39. Tools used to identify and calculate coverage items in program code.
instrumentation
test execution tasks
coverage measurement tools
decision coverage
40. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.
data flow structure
anomalous events
keyword-driven testing
impact analysis
41. 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 description subheadings
decision testing
decision table testing
42. A unique identifier for each incident report generated during test execution.
incremental testing
conformance testing tools
incident report identifier
efficiency
43. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.
incremental testing
conditions
LCSAJ
test implementation tasks
44. Tools used by developers to identify defects in programs.
resolution types
functional testing tool
impact
debugging tools
45. Occurrences that happen before and after an unexpected event
component integration testing
anomalous events
defect
configuration management
46. Used to test the functionality of software as mentioned in software requirement specifications.
multiple condition coverage
SW development model
functional testing tool
test implementation tasks
47. Tools used to store and manage incidents return phone defects failures or anomalies.
component
coverage measurement tools
incident management tools
resolution types
48. Sequence in which instructions are executed through a component or system
failure rate
control flow structure
fault attack
failure
49. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.
anomalous events
incident description subheadings
experience-based techniques
functional requirements
50. Based on analysis of functional specifications of a system.
data-driven testing
functional testing
backbone integration
action