Companies often spend a lot on performing test automation to reduce the efforts spent by testing team. We read a lot about how to make the automation projects successful, but, have you ever thought on how you can achieve it otherwise. If you are one who want to make any of the automation initiatives unsuccessful, do proceed reading further.
Don’t involve team during planning
Planning is not important. Just tell people what areas they will work and they will deliver. This will ensure that people are spending time in delivering what they are asked to do without putting their brains behind.
Select tool based on team knowledge
Irrespective of the technology used by the application, use the tool that the team members assigned to the project knows. Don’t waste time on hiring or updating the skill sets of people.
Estimate based on your scripting speed
Don’t consider test case complexity/team skill sets/learning curve/hiring time etc while estimating the efforts. Just estimate based on how much you alone will be able to achieve.
Automate areas having high probability of changes, first
Consider that the critical areas from the point of testing are the ones that are getting changed in every build. Start automating them first. This will ensure that the team spends the time on maintenance rather than new development.
Freeze the build for the complete duration of project
Before starting the project, be strict on not changing any product build, irrespective of releases made to the testing team in between. Just make your scripts compatible with the initial version of the build provided to you. This will ensure that your scripts do not run on the latest build and hence will help in failing the UAT.
Avoid any communication with stakeholders
Stakeholders always ask for reports that often decreases the productivity. They also do not have any rights to get information on the challenges that the team is facing. If you want to fail miserably, it is seriously advised not to tell stakeholders anything about the project before the final delivery.
Keep Script integration at low priority
Do not estimate for script integration and do not even care for it. If time permits, then do it immediately before UAT so as to ensure there is enough evidence of script not working.
In case you have any other tip, request you to share it in comments and I will add it up in the upcoming post.