|
Observation: Often QA managers bothered with their automation when they did not get expected result. It’s often happen when client bought any automation toll and surprised to see that it does not support the application they are testing. Solutions/Suggestions: Expected problems and their solutions are suggested below: Unrealistic Exceptions: By viewing any automation tool demo most manager have pleased to see that it meets our requirement. But infect many problem has arises when they try it with their application. The vendor will only tell you set of hopes that how it will save time, how simple to setup, how easy to use, etc. These all things which you want to hear. Lack of Planning: From selection to implementation of the tool is a sensible process and it is required sufficient planning. This is ideal way to select any automation tool and the participation of end user in this process is very necessary. Lack of Process: Along the planning, process is also necessary to successfully implementation of any automation toll. In most cases developers write code against a set of requirements. If the requirement does not call for a change in GUI (graphical user interface) then, there should not be any change in GUI. Continuously changing in GUI with out any specific requirement or reason is problem in process. You will require any other best tool because of failure process of this tool. Conclusion: Awareness is required between QA managers on the advantages and limitation of automation. Start from initial step not previous step to fix any problem occurred in implementation of automation. Automation process help QA process in magic way, knowledge and understanding is required to save from troubleshooting. |
| Sponsored Links: |
| << back |