Sunday, October 19, 2008

Web UI Testing put to good use :o)

Well my wife's high school needed some votes on a local news channel site to win some recognition. The rules say you can only vote once per hour. To keep things ethical I have limited our voting to 2 votes per hour (1 for me and 1 for my wife). To do this though I needed an automated way of putting in the votes. I used an open source web UI testing tool (Watin) to create a console app that opens the web page, selects the correct radio button, and then hit the vote button. Once complete the application closes IE. It then waits 60 minutes and starts all over again. I have this running on my virtual machine servers so it can run for the next few days.

This was a neat test and now has my interest in this tool for other items. While I am not at the computer during my votes - I am still abiding by the rules :o).

Happy Voting!!!!

Update - Still busy - just not blogging

Well it has been a while since my last post. I have been quite busy though. I have written a few test apps for various product support issues. My latest test app (in progress) is similar to a Microsoft UDL file. This app will let you run queries against and of my products databases using any of the data providers we utilize. This will give more details on why the connections / apps are failing.

My latest project is to write the automation that allows databases to be created (SQL and Oracle) once the software builds are complete. This is not a difficult task but is time consuming. There are some proprietary methods that must be used and learning these is not difficult - but can by tricky. Oracle and SQL behave so different they must be made to mimic each other.

Here are the steps I have to perform (all automated):

1) Create Database Connections
2) Create the Database and users on the database servers (Oracle and SQL)
3) Use our system to generate the schemas for the database
4) Populate the databases with sample data
5) Connect our software application to the databases

I am currently on step 3 due to time constraints.