Skip to Content

Hi, my name is

Ramesh Lakmal.

QA engineer focused on reliable releases.

Quality work centered on reducing surprises at release time: focused manual testing, practical automation and lightweight performance checks, with findings that are clear, actionable and easy to reproduce.

Open Resume

About Me

QA engineer focused on reducing product risk and supporting reliable, high-quality releases. Validates features through structured testing, identifies high-impact issues early and communicates findings clearly so teams can make quick, confident decisions.

Experience includes testing web and mobile applications across LMS, ERP, POS and cloud-based platforms.

Currently focused on building maintainable automation and improving test efficiency with modern tools and practices.

Core expertise:

  • Test Design & Execution
  • End-to-End Automation (Playwright, Selenium)
  • API Testing & Validation
  • Performance Testing & Monitoring (JMeter, Grafana)
  • Test Management & Reporting (Azure DevOps)
  • CI/CD Test Integration
Ramesh Lakmal

Experience & Education

Quality Assurance Engineer @ WaveZync

October 2024 - Present

  • Sole QA engineer across multiple concurrent projects, responsible for test planning, execution, defect tracking and release validation.
  • Test web, mobile and cloud-based products, including Analyst Builder and Paradise Cloud, in close collaboration with developers, designers and stakeholders.
  • Lead bug triage with the development and UI/UX teams to prioritize defects and track them through to resolution.
  • Test REST APIs with Postman and Swagger, validating endpoints, payloads, responses and backend integrations.
  • Verify consistent functionality and user experience across iOS, Android, browsers and screen sizes.

Work

Latest work

  1. 2026

    E2E Testing with Claude Agents

    A five-stage pipeline in which Claude agents turn a web feature into a Playwright test suite. A setup agent analyzes the application source, a planning agent writes test scenarios from that analysis, and a generator agent produces tests that follow a strict page-object convention, with a human review gate after setup and after planning. A healer agent repairs tests that break when the UI changes. Demonstrated on the Sauce Demo store.

    Playwright, Claude, Agentic Testing

    Article Source
  2. 2026

    TestPilot AI

    TestPilot AI converts software requirements into structured, prioritized test cases. It analyzes the input to identify key test conditions, applies the relevant test design techniques and generates a deduplicated test suite. Results are shown in a searchable format and can be exported or synced directly to Jira (AIO Tests) for end-to-end traceability.

    Anthropic, Jira

    Live app Source
  3. 2025

    QA Workflow with Playwright, GitHub Actions and AIO Tests

    A Playwright Test project, with page objects, fixtures and a reusable authentication setup, that reports each run to AIO Tests in Jira. Test titles carry AIO case keys, so every automated result is recorded against its test case in a test cycle. A GitHub Actions workflow runs the suite on demand, with credentials stored as repository secrets. The accompanying article explains the setup step by step.

    Playwright, GitHub Actions, AIO Tests

    Article Source
  4. 2025

    Understanding the Basics of Performance Testing

    A short introduction to performance testing and why it matters before real traffic exposes problems. It explains load, stress, spike and soak testing, what each one reveals about an application, and the metrics worth watching, such as response time, throughput and error rate.

    Performance Testing, JMeter

    Article
  5. 2025

    Performance Monitoring Using JMeter + InfluxDB + Grafana

    A performance test setup for the OrangeHRM demo application. JMeter test plans cover login and employee creation, using test data from a CSV file and values extracted from earlier responses. A backend listener streams live results to InfluxDB, and Grafana dashboards chart response times, throughput and errors while the test runs. A GitHub Actions workflow runs the plan on every push and keeps the HTML report as a build artifact.

    JMeter, InfluxDB, Grafana

    Article Source
  6. 2024

    Playwright Automation with ZeroStep

    An experiment with ZeroStep, which adds an ai() step to Playwright tests. Instead of CSS or XPath selectors, each step is a plain-language instruction that is resolved to an action at run time, so tests are less affected by changes to the UI. The project automates a checkout flow and documents practical guidelines for writing reliable instructions.

    Playwright, ZeroStep

    Source
View all 11 projects

Contact

Get in Touch

Open to QA engineering and automation opportunities, with a focus on improving product quality and release confidence.

Based in Colombo, Sri Lanka.