When I was automating testing our first project, it was a web based administration app. For that, I did some research and we chose to go with Sahi. I was able to achieve about 60-70% automation with Sahi and very happy with its result. During that time, one day I also gave a presentation at my office about what and how is web testing automation with Sahi. The presentation I created for this is the following:
This presentation gives a very brief idea about web testing automation in general and with Sahi. In the coming posts, I will try to share the issues I faced both with automating testing for desktop and web apps.
Sahi helped us automate our web application testing by 60%-70%. Till now I am quite happy with it.
On a continuation to my previous post regarding Testing Automation Tools, I will try to write the process through which I went while writing the testing scripts.
The application for which I wanted to do the automated testing is a web based application written in PHP on top of Zend Framework. As Zend Framework follows the MVC pattern, we followed the same pattern. For database, we wrote our own layer and didn’t use the layer which Zend Framework provided.
For testing automation I followed the same design rules, which I followed while designing and writing this application. I wrote testing scripts for each entity in their own files. Then I called them in one main file, which I run when I want to run the regression test. Following is an example configuration file:
//include all files, which are required to run the test cases
// create company info
I treat this main script as my main configuration file. Where I declare some global variables, call those scripts which I need to run during my test run. I can include the scripts, which I need to run and can exclude those scripts which I don’t need.
I will continue with this series with further updates on how I wrote automated tests for every individual entity.