Automate where it make sense

Automation Consulting

We Support all Major Platforms

We work across all major platforms and make recommendations without bias for technology, delivering integrated process automation solutions designed to meet your specific objectives. Our automation services support every phase of your project including requirements gathering right through to going live as well as ongoing maintenance and support.

TestPro Consultants are Automation Specialists

Our Team and Resources

We dispatch teams of skilled professionals to perform a range of testing services from inception and technical process design services to construction management. Our team helps you capture your most important processes an enables you to reduce the risk of any issues with BAU processes. Services range from quality management and cost reduction by investing in automation, training and support.

TestPro Supports a number of different Platforms

We work with and extend your Platform

We offer a diverse understanding in a variety of industries and technology platforms. Our proven development and execution methodology guides our process to ensure efficient, maintainable, cost-effective and timely project completion.


We know how to test ERP

ERP Systems

You can make the testing of ERP deployments more efficient from a time and cost perspective with assistance from TestPro.

We can apply our experience to make your testing more effective, achieve better quality and reduce cycle times. Our ERP testing skills cover both functional and performance testing.

With ERP applications such as SAP, PeopleSoft and Oracle, there are a variety of testing strategies which address a range of different business contexts and requirements.

TestPro ERP Project Experience

We have experience across a number of ERP implementations including clients such as BOC, Fairfax. AMP, University of Newcastle, University of NSW, Davids Limited, Metcash and George Weston Foods.

ERP Testing Strategies

The best strategy is selected after a review with the client and depends on factors such as project timelines, business objectives, testing budget …

Common test strategies are risk based: Testing should focus on highest areas of risk. This is based on the premise that there are areas of high(er) risk in any application system and when these are identified, to focus testing on those areas as this will reduce risk the most. With ERP deployments, higher risk will typically exist in areas where customisations have been done and/or where new business processes have been implemented.

A second testing strategy is priority based: Test should find the most important defects first. Most important means often “in the most important business functions”. These functions can be found by analysing how every function supports the mission, and checking which functions are critical and which are not.

You can also test more where you expect more defects, for example where customisations have been done. Focusing early on the worst areas in a release and testing them more helps reduce risk.

Another testing strategy is to test to a defined quality level! Most releases are not expected to be completely free of defects and not every function needs to work. Sometimes, you have options to release with a lower quality and/or reduced functionality, which means you can cut down testing in less important areas.

A major efficiency gain can be achieved with the automation of test execution. TestPro has experienced practitioners in test automation and automation frameworks, who are able to implement automation for ERP projects with minimal overhead compared to manual testing.

Implemented properly automation frameworks can make the pre-release testing of ERP updates and patches a relatively simple process. This is because the essential tests are captured into the framework and can be quickly and simply re-run to validate functionality.

Without the relevant automation experience, automation can be time consuming and expensive to implement. Not using the right approach potentially exacerbates the costs of creating and maintaining the automation scripts can outweigh the benefits derived from them. In this situation the scripts become redundant as they are no longer usable.