I find the bugs that live between systems.

I’m Adem Kabayel, a QA automation engineer and SDET in Vancouver. For six years I’ve tested retail, supply-chain and banking platforms, following each change from the screen through the API, the Kafka topic and the database row.

  • Open to QA automation and SDET roles
  • ISTQB Certified Tester (CTFL)

Selected work

Three teams, three kinds of risk: inventory that has to match what’s on the shelf, supply-chain plans that have to load and calculate correctly, and money that has to reconcile to the cent.

Testing RFID inventory from the handheld to the cloud

  • lululemon, contract
  • QA Automation Engineer, RFID
  • Dec 2024 to present

Shipment and inventory-count workflows that cross handheld scanners, REST APIs, Spring Boot services, Kafka events and the Nedap iD Cloud platform. I build the Java BDD automation that checks every hop, and trace failures across producers, consumers and vendor integrations.

Read the case study

A test framework a whole team could build on

  • Kinaxis
  • Software Developer 1, Core Web QA
  • Aug 2022 to May 2024

I designed a reusable UI and interface automation framework in TestCafe and TypeScript for complex supply-chain applications, wired regression into CI/CD, and was QA prime for epics from acceptance criteria to the release call.

Read the case study

Banking automation that reconciles to the cent

  • Wells Fargo
  • QA Automation Tester
  • Jun 2019 to Jul 2022

A Java, Selenium and Cucumber BDD framework with smoke and regression suites in Jenkins, REST API automation, and SQL and JDBC utilities that reconcile what the API returned with what Oracle recorded.

Read the case study

How I work

  • Start from the architecture

    Requirements say what a system should do. The architecture shows where it will break: which services depend on each other, where the data moves, which events fire in between. I map that first, then write the tests.

  • Every check has to be able to fail

    If a check can’t fail for a real reason, it doesn’t earn a place in the suite. Tests that only ever pass are noise, and noise is how real failures get ignored.

  • Follow the failure all the way down

    A red test is where the work starts. I trace it through logs, topics, queries and cloud outputs until I can show the developer which component broke, with the evidence attached.

  • Talk about risk, not test counts

    Release decisions need a plain read on what’s covered, what isn’t, and what could go wrong. I write that down for developers, vendors and stakeholders before the release, not after.

Things I build to learn

Side projects in public, where I try tools before I need them at work.

  • workbook-mcp-serverJava, in progress

    A Model Context Protocol server that lets AI assistants like Claude and GitHub Copilot generate Excel workbooks on request. Built on the official MCP Java SDK over stdio, with Apache POI doing the spreadsheet work and JUnit 5 tests around the generator.

    • Java 21
    • MCP Java SDK
    • Apache POI
    • JUnit 5
    • Maven
    GitHub
  • playwright-labTypeScript

    UI and API tests in Playwright, including a GraphQL check that looks past the HTTP 200 and an axe-core accessibility scan that attaches its full results to the report. I wrote up both in notes.

    • Playwright
    • TypeScript
    • GraphQL
    • axe-core
    GitHub
  • springboot-kafka-real-world-projectJava

    Two Spring Boot services: a producer that streams Wikimedia’s live recent-changes feed into a Kafka topic, and a consumer that writes those events to a database. Built while learning Kafka producers and consumers from the inside.

    • Spring Boot
    • Apache Kafka
    • Java
    • Maven
    GitHub

Tools I use

Languages
Java, TypeScript, JavaScript, Python, SQL, Node.js
UI and API automation
Playwright, Selenium WebDriver, TestCafe, Cypress, REST Assured, Postman, cURL
Frameworks and build
Cucumber and Gherkin, JUnit 5, TestNG, Jest, Pytest, Maven, Page Object Model, Allure
Distributed systems
Apache Kafka, REST APIs, Spring Boot services, microservices, Apigee, Kong
Cloud, data and observability
AWS S3, RDS and Glue, Snowflake, MySQL, Oracle SQL, MongoDB, Splunk, Lenses
CI/CD and delivery
GitLab CI/CD, Jenkins, Kubernetes, Git, Jira, Xray, TestRail, Zephyr
ISTQB Certified Tester, Foundation Level (CTFL) ASTQB / ISTQB, July 2026. Credential ID 26-CTFL-01438-USA