Selected work

Banking automation that reconciles to the cent

At Wells Fargo I automated testing for banking applications, where a defect isn’t an inconvenience, it’s someone’s money. It’s where I learned to check the data, not just the screen.

Company
Wells Fargo
Role
QA Automation Tester
When
Jun 2019 to Jul 2022
Focus
UI, API and data automation

What I built

  • A Java, Maven, Selenium and Cucumber BDD framework using the Page Object Model and Singleton patterns, with smoke and regression suites running through Jenkins CI/CD.
  • REST API automation with REST Assured and Postman, validating integrations and data exchange across banking applications.
  • SQL and JDBC validation utilities that reconcile API results with Oracle database records, which also powered data-driven test coverage.

Why reconciliation mattered

A banking UI can show the right number while the record behind it is wrong. Checking what the API returned against what the database actually stored closes that gap: if the two disagree, the test fails, no matter how good the screen looks.

How I worked

I ran functional, system-integration, regression and defect-validation testing in an Agile team, and worked closely with developers to isolate and resolve issues. The habits from here, Gherkin that reads like the business rule and assertions that go all the way to the data, are the ones I still build on.

Tools

Java, Maven, Selenium WebDriver, Cucumber, REST Assured, Postman, SQL, JDBC, Oracle, Jenkins.