Proof of Work

Projects

116 automated tests (unique test definitions) across four independent projects with public source code. Every line of code, test, and CI/CD configuration is open on GitHub. These projects demonstrate Playwright automation architecture (page objects in the UI projects, an API client layer in the API project), testing methodology, negative testing strategy, and CI/CD integration.

4
Public Projects
116
Test Definitions in 4 Public Projects
UI + API
Testing Types
3 of 4
Last Recorded CI Runs Passed (ERPNext’s 22 Oct run failed: its test instance is gone)

Counting method

116 counts unique test definitions, counted from each repository’s test files at the commit shown here and cited on its project page (the same list playwright test --list prints): Automation Exercise 26 (789d413), ERPNext 6 (8990014), RESTful Booker 47 (a385240), Razorpay 37 (da9e7a2). It is not a coverage measure, not a count of executions and says nothing about whether those tests pass. ERPNext’s 6 includes 1 authentication setup test, and 3 of Razorpay’s 37 are live-mode tests run separately (34 run in CI). CI results are historical. The last runs were 29 August (Automation Exercise), 14 September (Razorpay) and 22 October 2026 (RESTful Booker, whose latest commit only added a manual workflow trigger), and all three passed. ERPNext’s last green run was 4 September; its latest run, on 22 October 2026, failed because the hosted test instance it needs is gone (by my reading of the job log). I checked all four run lists on 22 October 2026. CI is configured with retries.

01 Public projects

Public QA Projects

Four independent GitHub projects showcasing 116 unique automated test definitions. These public projects demonstrate my testing approach, automation architecture, and technical decision-making across UI automation, API testing, payment gateway QA, and test infrastructure.

Razorpay Payment Gateway QA & Automation: project coverCover for Razorpay Payment Gateway QA & Automation: 37 test definitions (34 run in CI, 3 live-gateway). Flow covered by the suite: create an order, verify the payment signature, receive a webhook, check its HMAC over the raw request body, update the order state. Built with Playwright, Node.js, Express, SQLite.PAYMENT WORKFLOW TESTINGRazorpayPayment GatewayQA & AutomationPlaywright · Node.js · Express · SQLite37test definitions34 run in CI, 3 live-gateway1Ordercreate order2Verifypay signature3Webhookevent ID4HMACraw body5StateSQLite stateTwo high-severity defects found, fixed and regression-testedsayedasif.comRazorpay Payment Gateway QA & Automation: project coverCover for Razorpay Payment Gateway QA & Automation: 37 test definitions (34 run in CI, 3 live-gateway). Flow covered by the suite: create an order, verify the payment signature, receive a webhook, check its HMAC over the raw request body, update the order state. Built with Playwright, Node.js, Express, SQLite.RazorpayPayment GatewayQA & Automation37test definitions34 run in CI, 3 live-gatewayPlaywright · Node.js · Express · SQLiteOrderVerifyWebhookHMACState

Payment Gateway QA & Automation

Razorpay Payment Gateway — QA & Automation

Independent QA project testing a Razorpay Test Mode payment flow for verification, security, webhook behavior, state transitions and failure handling. Two high-severity defects found in the demo app I built as the test target, fixed with regression tests.

37 Tests Last CI Run: 34 CI-safe tests passed (14 Sep 2026)

Playwright Test Node.js / Express Razorpay Test Mode SQLite GitHub Actions
RESTful Booker TypeScript API Automation: project coverCover for RESTful Booker TypeScript API Automation: 47 test definitions (9 spec files). Booking lifecycle covered by the suite: authenticate, create, read, update with PUT and PATCH, delete. Built with Playwright, TypeScript, REST API.API AUTOMATIONRESTful BookerTypeScript APIAutomationPlaywright · TypeScript · REST API47test definitions9 spec files1AuthPOST /auth2CreatePOST3ReadGET4UpdatePUT · PATCH5DeleteDELETEBooking lifecycle, negative cases and read-back checkssayedasif.comRESTful Booker TypeScript API Automation: project coverCover for RESTful Booker TypeScript API Automation: 47 test definitions (9 spec files). Booking lifecycle covered by the suite: authenticate, create, read, update with PUT and PATCH, delete. Built with Playwright, TypeScript, REST API.RESTful BookerTypeScript APIAutomation47test definitions9 spec filesPlaywright · TypeScript · REST APIAuthCreateReadUpdateDelete

API Automation

RESTful Booker API Automation

Independent project: Playwright and TypeScript tests for the public RESTful Booker practice API: authentication, create, retrieve, full and partial update, delete, negative cases and multi-step workflows, built on reusable API client classes.

47 Tests Last CI Run: Passed (22 Oct 2026)

Playwright Test TypeScript REST API GitHub Actions
ERPNext QA Automation: project coverCover for ERPNext QA Automation: 6 test definitions (5 UI + 1 auth setup). Workflow covered by the suite: reuse the saved login, open a new document, select an item through the autocomplete, set quantity and rate, save and verify. Built with Playwright, Page Object Model, GitHub Actions.UI TEST AUTOMATION · ERPERPNextQA AutomationPlaywright · Page Object Model · GitHub Actions6test definitions5 UI + 1 auth setup1Authsaved login2Formnew document3Itemautocomplete4Qtyand rate5Savethen verifyMaterial Request · Quotation · Sales Ordersayedasif.comERPNext QA Automation: project coverCover for ERPNext QA Automation: 6 test definitions (5 UI + 1 auth setup). Workflow covered by the suite: reuse the saved login, open a new document, select an item through the autocomplete, set quantity and rate, save and verify. Built with Playwright, Page Object Model, GitHub Actions.ERPNextQA Automation6test definitions5 UI + 1 auth setupPlaywright · Page Object Model · GitHub ActionsAuthFormItemQtySave

UI Automation

ERPNext QA Automation

Automated testing of ERPNext business workflows including Material Request, Quotation and Sales Order. Features Page Object Model architecture, Playwright UI automation, GitHub Actions CI/CD integration, and reliability investigation.

6 Tests Last CI Run: Failed (22 Oct 2026, test instance gone); last green 4 Sep 2026

Playwright Page Object Model JavaScript GitHub Actions
Automation Exercise: project coverCover for Automation Exercise: 26 test definitions (16 API + 10 UI). Shopping flow covered by the suite: log in or sign up, browse products, add to and remove from the cart, review the order items, check out. Built with Playwright, Page Object Model, GitHub Actions.PRACTICE-SITE PROJECTAutomationExercisePlaywright · Page Object Model · GitHub Actions26test definitions16 API + 10 UI1Loginor sign up2Browseproducts3Cartadd, remove4Revieworder items5Checkoutplace orderUI flows plus API tests for account, authentication and productssayedasif.comAutomation Exercise: project coverCover for Automation Exercise: 26 test definitions (16 API + 10 UI). Shopping flow covered by the suite: log in or sign up, browse products, add to and remove from the cart, review the order items, check out. Built with Playwright, Page Object Model, GitHub Actions.AutomationExercise26test definitions16 API + 10 UIPlaywright · Page Object Model · GitHub ActionsLoginBrowseCartReviewCheckout

Practice-Site Project · UI & API

Automation Exercise

End-to-end test automation across authentication, product catalog, shopping cart, checkout and REST API endpoints, run against automationexercise.com, a public demo store built for test practice. Demonstrates UI and API validation with Page Object Model architecture and GitHub Actions CI.

26 Tests Last CI Run: Passed (29 Aug 2026)

Playwright API Testing Page Object Model JavaScript GitHub Actions

02 Scope

What This Work Demonstrates

  • UI Automation
  • API Testing
  • Test Architecture
  • Page Objects & API Clients
  • TypeScript
  • Negative Testing
  • CI/CD Automation
  • Test Reporting

03 Inspect

What You Can Inspect

All projects are open source on GitHub. Inspect the code, test suites and CI workflows. CI run logs require a GitHub sign-in.

Source Code

Complete test frameworks, API clients, and automation architecture

CI Run History

GitHub Actions run history for the public projects (job logs require a GitHub sign-in)

Documentation

README files with project structure, test descriptions, and architecture