Template:WestpacShort

Senior Automation Test Engineer - Westpac (Apr-2021 - Nov-2023)

References

TBD xxx

At Westpac I worked as a roving Quality Engineer across a number of teams. I regularly needed to learn new product domains, and new technology stacks for both the product as well as the automation. It was fun and exciting, keeping me on my toes to quickly adapt and pickup new knowledge and skills. The common thread was always testing through learning and discovering the product and project. Identifying the biggest issues directly in front of us, as well as looking to the future for pitfalls to avoid.

• MF8TL Team

MF8, aka Mobile First V8, was a legacy API product, and was part of a mobile and web app development eco system sold by IBM. MF8 needed to be replaced with a new temporary solution, MF8TL, prior to migrating all functionality to micro-services. MF8 & MF8TL were effectively API (middleware) services facilitating access to the wider banking network. MF8TL needed to be stood up quickly, and behave identically to the legacy MF8 system.

My involvement with the team was to identify existing testing tools and processes available for the old MF8 system, and to apply them to the new MF8TL implementation.

Primarily I worked on adapting an existing REST Assured, testng, Java automation suite. I refactored significant parts of it to use method overloading to centralise the code that despatched requests and received the responses, for the purpose of improving and standardising the logging being sent to Splunk.

• Test Environments Team

The main task this team worked on was to build a fun little webapp UI and API server using Node.js, Express.js, React, and the mermaid.js diagramming tool to create node maps of how various systems connected. In this project I was more a JavaScript developer than a tester.

• Observability Squad

With this team I switched to a more Platform Engineering role, and became the Westpac Splunk Champion. We were supporting and growing the Splunk platform for Westpac internal technology teams. I have had exposure to Splunk in previous companies and have truly loved it for analysing data. I really like to try and find the customers' experiences come through the data. I would always ask the teams we were supporting on their Splunk onboarding journey three things:

1. Are you logging how well your product/service/feature is working? eg transactions per hour
2. Are you catching all the errors and warnings to know when the product/service/feature is doing something bad
3. When you observe an error/warning are you recording good quality information that truly helps devOps understand the issue, and expedites the remediation of the issue?

The latter I find particularly important because in the end the objective is to minimise the risk of major issues by knowing about them quickly, and also being able to solve them quickly. Timely & good quality information is paramount.

• D365 KiwiSaver Squad

Built a Selenium WebDriver POM based cucumber Java automation suite from scratch to test a D365 webapp.

Mobile Squad

Manual and automated testing of Westpac's iOS & Android mobile apps.