Aryaans have extensive experience in working with a variety of tools, such as Rational Robot, Segue's SilkTest, Compuware, Mercury Interactive's WinRunner and QuickTest Pro, Rational Visual Test, Worksoft's Certify, Seapine's QA Wizard, etc.
Functional testing can be automated to create a repository of reusable test scripts that help save considerable time and effort in functional and regression testing. Test scripts are prepared in order to ensure high degree of reusability and portability across environments.
Over the years we have gained expertise:
We can develop automation from the ground up, or expand an existing suite of automation scripts. Our familiarity with developing API-level tests launched by test harnesses, as well as with developing UI-driven scripts. Our library of automation functions can be readily adapted to most projects, greatly reducing the expense that our customers would incur in developing such libraries themselves. Our purpose is to ensure efficient automation.
Functional software test automation development is the automation of the test cases created to test the application/system. In layman’s terms this is the process of creating scripts to automatically execute certain tests created during the test development life cycle (ATLC).
For the development of the automation scripts the following process is followed:
Creating an automated test is generally more time-consuming (expensive) than running it once manually. It is for this reason that a careful decision should be made with regards to which tests would be beneficial to automate.In this phase we need to establish which tests would be automated by understanding what tests have already been created for testing the system.
Design the implementation with a focus on reducing the maintenance effort on the functional test automation scripts. To achieve this we need to encourage reuse of the script components as far as possible. We have to plan what utilities will have to be created. These utilities or functions will be reused in our test automation script creation. An example of such a utility script or function might be the error reporting or logging mechanism.Proper planning will ensure that we create the most cost efficient automated tests in the shortest possible time. At the end of this phase we will know if we will implement a data driven or keyword approach or if we will use the standard capture-playback method.
After careful planning during the design phase we will have a set of reusable utility scripts, which can be used as building blocks to create the scripts that will comprise the automated regression tests. Scripting can now start…After completing the utility scripts they need to be unit tested and then incorporated into the automated regression suite.
In this phase we integrate the test scripts and utility scripts into the regression suite and execute the test cases automatically. The integration phase also contains test automation development system testing. After successful testing we are now prepared and ready for the reuse of our set of automated tests.The automated tests can now be run and re-run as required by our testing process.
During the life cycle of our system the system itself will change, requiring us to change our test cases. If the test cases change the functional test automation regression suite will have to be adapted to deal with the changing system. Maintenance will have to be done on our initial automated regression tests and/or utility scripts.