Work

Health software · web, iPhone and Android

Nobody finds bugs in health software funny. Fair enough.

• I test the website and both phone apps, by hand and with automation.
• I write automated tests with Reflect. They check maps, dashboards, alerts and messages.
• I write mobile tests for iPhone and Android with Maestro.
• I test APIs with Bruno, keep my test cases in Jira with Zephyr, and run everything in GitHub Actions.

Same job, second product · web and phones again

• I own all the testing here. If something ships broken, that one is on me.
• I check new features, I check the old ones still work, and I test the APIs with Postman.
• When a Cypress test fails, I find the real reason. I do not just run it again and hope.
• I check that the data stays correct when it moves between systems.
• I wrote down how we test, so new QA people can start faster.
• I work with developers and product managers to write better bug reports and ship faster.

A big world health organisation

It moved staff, money and salary data between very large systems. I was the only QA engineer on it. No pressure.

• I took over a test suite with 918 tests that only ran in one place. I grew it to more than 2,100.
• The tests now run in all four places (dev, sit, uat, prod) and cover three API versions.
• I added schema checks with Swagger and AJV, so the API gets checked on its own.
• I looked after the GitHub Actions pipelines: file checks, pull request rules and code checks.
• I looked after the release pipeline for a live system used around the world.

A big SaaS product · remote

• I moved about 2,000 tests from Cypress to Playwright. It took a while.
• Tests that failed for no real reason went down by 15%, and people started trusting the build again.
• I made the CI/CD steps reusable, so the pipelines were easier to look after.
• I made the tests faster. I cleaned up the code, fixed selectors and removed waits we did not need.
• I ran SQL queries to check the data was right.
• I wrote the Playwright guide the other teams used.

A health platform for clinics · remote

I came in to write React and left running the test team. Not the plan, but a good one.

• I managed three people and owned all the end to end tests.
• I tested the parts clinics use every day: bookings, client records and payments.
• I moved our tests off the database and onto mocks. That removed a lot of random failures.
• I used Jira to track and manage issues.

My first job · Pristina

• I turned Figma designs into working pages, and learned React the hard way.