CLIENT PROFILE
Client is a community service organization that has been transforming the lives of Australians in need for more than 150 years. Client provides:
- Accommodation and support programs for the homeless
- Creative services for homeless youth
- Counseling and support programs for families
- Accommodation and support for people with disabilities
With over 3,500 employees, volunteers, Board members, and supporters, the organization advocates for disadvantaged Australians and helps them get back on their feet. Working alongside government, corporate Australia, churches, and the wider community, the client is determined to overcome disadvantage across the nation.

BUSINESS SOLUTION
The client had a web-based, secure client record management system that helps create and maintain electronic records. The application used advanced Ajax controls and Selenium RC for automation testing. Scripts were written in Java using Eclipse and executed via an existing Excel-driven framework.
Challenges faced:
- Incremental feature updates changed workflows, causing existing scripts to fail
- The framework produced memory errors when executing scripts in batch mode
- Pop-ups (single and multiple) were not handled by Selenium, requiring additional handling
- New features required framework updates and new script development
The client wanted:
- Existing failing scripts fixed
- Pop-up handling built into the framework
- New scripts developed for added functionality
SOLUTION
Adactin proposed and implemented a gradual update process, divided into 5 phases:
Phase 1 – Analysis of Memory Issues in Framework
- Identified root cause: 32-bit Eclipse had limited Java heap size
- Migrated to 64-bit Eclipse and OS, resolving memory issues
- Set up 64-bit automation framework system:
- Installed Eclipse
- Setup Selenium RC
- Added external libraries and JARs
- Installed Java and AutoIt
Phase 2 – Analysis of Existing Failing Scripts
- Reviewed application functionalities
- Set up test environment and automation framework
- Executed all existing scripts
- Logged and categorized issues by complexity and resolution time
- Identified Java code issues not correctly executing methods related to workflows
Phase 3 – Fixing of Failed Scripts
- Environment setup completed
- Addressed issues:
- Entered data in
TestData.xls
for new functionality - Added new keywords to framework and scripts
- Debugged and fixed Java code and variables
- Entered and corrected missing/incorrect XPaths
- Entered data in
- Implemented Pop-up Handling:
- Analyzed workflows triggering pop-ups
- Created pop-up-specific AutoIt EXE
- Integrated AutoIt EXE calls in the scripts
Phase 4 – Writing New Scripts
- Created new scripts for added functionality:
- Defined test steps in
Framework.xls
- Added required data in
TestData.xls
- Entered XPaths for new fields
- Developed specific Java files in Eclipse
- Executed all new scripts
- Defined test steps in
Phase 5 – Knowledge Transfer
- Created comprehensive update and fix reports
- Delivered knowledge transfer sessions covering framework enhancements
- Trained client’s internal automation analysts

BENEFITS
- 64-bit setup enabled faster execution; scripts now run overnight in batch mode
- Automation regression testing saved 40% of testing time
- Pop-ups successfully handled using AutoIt
- Reduced script execution time led to increased productivity
- Provided debug and enhancement documentation, aiding long-term maintenance of the framework
TECHNOLOGY STACK
- OS – Windows 2007
- Database – SQL Server 2000
- Programming Language – Java
- Automation Tool – Selenium RC
- Pop-up Handling – AutoIt
ASSISTANCE PROVIDED BY CLIENT RESOURCES
- IT team assisted in setting up the 64-bit machine
- Testing team helped with setting up the environment
- Testing team provided test data and scripts