I have been recently hired on as an intern at a small company (i.e. about 50 people) and have been put in charge of setting up automated testing on equipment control software (they make analytical lab equipment). Anyways, after doing some research I am quickly coming to the conclusion that I am over my head a bit, at least if I want to do things right. I would really appreciate any advice that any more experienced programmers and testers would like to give, especially in the area of what testing software package would be the best to use.
The software itself is written in C++ and operates in a Windows environment. I also have access to the source code and am a competent programmer myself, so I can add any testing hooks that need to be put in.
I already plan on picking up a copy of “Effective Software Test Automation: Developing an Automated Software Testing Tool” and “Effective GUI Testing Automation : Developing an Automated GUI Testing Tool” by Kanglin Li in the near future. Is there any other reference books I should pick up and are the two I've picked worth buying?
I'd need to think a little more before giving you a full answer, but unless you are going to write your own testing tool from scratch and only use .NET, I don't find those books to be any use to your situation.
I found them to be a waste of money and would have prefered the trees to remain alove than them be wasted on those books. My opinion though.
There are a couple of other good Automation books like 'Just enough software test automation" from Mosley and Posey and "Automated Software Testing from (mainly) Dustin. I find those a little better and worth to keep in the library.
Hopfully once others have chimed in you will be floating after the cmpany tossed you into the deep end of the pool [img]images/icons/smile.gif[/img]
Another couple of sources for information will be white papers by Keith Zambelich, Brett Pettichord, and James Bach. Keith and Brett know the technical aspects (pro's / con's) and James knows the political aspects (setting expectations for yourself and management). These would be good places to start.
I would recommend you get to know and understand the manual process of testing first before you dive into the deep end of automation. As you may know you need to understand a process first before you can automate it properly, and effectively.