Westpac NZ - Senior Automation Quality Engineer: Difference between revisions

Jump to navigation Jump to search
Line 18: Line 18:
* other linkedin recommendations - TBD
* other linkedin recommendations - TBD


=== MF8TL Team ===
=== MF8TL Team: Legacy API Server Replacement ===
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 used for the old MF8 system, and to apply them to the new MF8TL implementation.  
This team was implementing a replacement of a legacy API Server used by the bank's mobile and web apps. The old system had a mature API automation suite implemented using Java, TestNG, and REST Assured.


Primarily I worked to adapt an existing '''REST Assured''', '''testng''', '''Java''' automation suite. I created new scenarios following the patterns already used in the suite, using service classes, '''POJO'''s, extending base test classes etc. I also significantly refactored parts to standardise and improve the information logged to '''Splunk''' when failures were detected, using method overloading to remove duplicated code, centralising the code that despatches requests & receives the responses, creating a single place to verify the kind of response received, prior to transforming to the success response POJO's.
My work
* Refactored and extended the existing mature API automation suite to test the replacement system.
* Implemented method overloading to centralize reporting results to Splunk within the automation codebase.
* Identified and applied suitable testing tools and processes from the old system to the new implementation.
* Focused primarily on enhancing the API automation suite by creating new test scenarios using established patterns such as service classes, POJOs (Plain Old Java Objects), and extending base test classes.
* Streamlined code, reduced duplication, and centralized request dispatching and response handling processes through Splunk integration efforts.


===Test Environments Team===
===Test Environments Team===