Technical skills needed to use WinRunner
My company will be evaluating WinRunner. Can anyone advise what technical skills are needed (programming, etc) to use WinRunner or any other Mercury product effectively?
Thanks in advance,
Re: Technical skills needed to use WinRunner
General programming knowledge will be useful: For creating robust and maintainable WR scripts AND for automating tests (if you have an understanding of how the AUT (application under test) does work internally, it will be easier to automate).
When the automation project grows, design techniques will become more important: You will have to plan & create a framework of libraries, external tools, tools to run sets of tests, which requires the tests itself to be more robust (recovery routines, establishing preconditions for running a test, ...).
For bigger automation projects it involves (almost) the same amount of planning and design as in software projects.
Non-technical skills like communication, gathering and sharing information, ... are also very helpful for setting up an automation project that will live longer than just for a single release.
PS: Have you also thought of the expectations your managers have? If they will expect miracles from automation, it's also not likely to be a success... Maybe they can screw down their expectations to a realistic amount.