QA Testing for Web Apps

As the lead QA Test Engineer for the AWV report (German regulatory reporting), I had to work with the BA’s, Developers, Project Managers, Reg Ops and numerous representatives (based in the EU, USA and India) from the multiple upstream payment systems.

 My primary objective was to ensure that the payments were flowing into our AWV report as expected and to highlight any bugs / defects spotted in our tests with the relevant developers using JIRA for tracking. In addition to this, I had to write our Test Cases (test objective and necessary steps) and manage the test flow from start to end with documented evidence of my findings for approval by the project and test managers, lead BA and most importantly, the internal regulators.

Functional Tests carried out (to ensure QA): Front to Back / End to End, Regression, Unit Testing, System Integration Testing (SIT) and User Acceptance Testing (UAT)

Automation Testing: I had to use IntelliJ (Cucumber feature files, using the Gherkin language) to write automated test scripts, Control-M and OST (internally developed tool) to download and replay payments from the upstream systems and Oracle (using PL/SQL) to verify the data flowing into our FLARE hub.

Manual Testing: Using Control-M, I would manually run a payment transaction (using both synchronous and asynchronous processes) and monitor the results. I would verify the logs to ensure we made the right calls and received the correct responses and identified any errors that were thrown up. I would first identify if the issue is on our end, if not I would escalate it to the external team and work together to resolve the issue.

Support our developers in the development of our internal payment replay tool, OST by testing out each component that was due to be deployed at the end of the sprint.

Peer test with the lead QA to validate each other’s test scripts.

Participated in scrum meetings which involve daily standups, sprint planning and sprint retrospectives.