Difference between revisions of "Lack of specific knowledge"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
# <span style="font-size: 16px">The only one that knew the automation has left the company. Look up the issue ''[[KNOW-HOW LEAKAGE]]'' in this case</span> | # <span style="font-size: 16px">The only one that knew the automation has left the company. Look up the issue ''[[KNOW-HOW LEAKAGE]]'' in this case</span> | ||
# <span style="font-size: 16px">You need an automation tool but don't know what criteria to apply to select the best one for your application. The issue ''[[INADEQUATE TOOLS]]'' will point to you the patterns needed to select the best tool for your application</span> | # <span style="font-size: 16px">You need an automation tool but don't know what criteria to apply to select the best one for your application. The issue ''[[INADEQUATE TOOLS]]'' will point to you the patterns needed to select the best tool for your application</span> | ||
− | # <span style="font-size: 16px">The Software Under Test (SUT) works with databases (or networks or whatever) and the automators are no experts in that field. Since it's usually not necessary for the automation team to be experts in every field, the issue that will help you here is ''[[INADEQUATE SUPPORT]]''</span> | + | # <span style="font-size: 16px">You are trying to understand how the automation works, but there is little or no helpful information about it, with within the scripts or elsewhere. The issue that will help you here is ''[[INADEQUATE DOCUMENTATION]]''</span> |
− | <br /> <br /> <span style="background-color: #ffffff; color: #000000; font-size: 16px">Return to [[Improve or revive test automation]]</span></div> | + | # <span style="font-size: 16px">The Software Under Test (SUT) works with databases (or networks or whatever) and the automators are no experts in that field. Since it's usually not necessary for the automation team to be experts in every field, the issue that will help you here is ''[[INADEQUATE SUPPORT]]''</span><br /> <br /> <span style="background-color: #ffffff; color: #000000; font-size: 16px">Return to [[Improve or revive test automation]]</span></div> |
Latest revision as of 15:42, 11 March 2019
Please select where you think the lack of knowledge is most severe
For the following items the issue of choice is LIMITED EXPERIENCE:
For the following items the issue of choice is LIMITED EXPERIENCE:
- The people that are to use the automation tool don't know how to use it
- The automators don't know the application they are supposed to automate
- Testers are supposed to write automation scripts, but don't know how
Other possible reasons for lack of knowledge:
- Management doesn't know what test automation means and therefore Managers don't see the value
- The only one that knew the automation has left the company. Look up the issue KNOW-HOW LEAKAGE in this case
- You need an automation tool but don't know what criteria to apply to select the best one for your application. The issue INADEQUATE TOOLS will point to you the patterns needed to select the best tool for your application
- You are trying to understand how the automation works, but there is little or no helpful information about it, with within the scripts or elsewhere. The issue that will help you here is INADEQUATE DOCUMENTATION
- The Software Under Test (SUT) works with databases (or networks or whatever) and the automators are no experts in that field. Since it's usually not necessary for the automation team to be experts in every field, the issue that will help you here is INADEQUATE SUPPORT
Return to Improve or revive test automation