Tech service

QA and test automation services

Rushi spent five years in the US working in Java, Spring Boot and QA, including work on TruCare, an enterprise healthcare management platform, at Casenet LLC, and for Freddie Mac through Hexaware Technologies. FamingU now builds AI-augmented test automation for teams that need reliable releases without a large QA department.

The problem

Releases break things, the test suite is flaky or missing, and nobody has time to fix it.

What we build

Automated tests in your repo and CI (Selenium, Playwright, Cypress), run on every build, with AI triage of failures.

What you get

Fewer surprises in production and a suite your team can trust, with overlap in your US morning hours.

Test automation framework development

Many teams do not need more tests; they need a framework that makes tests cheap to write and easy to trust. Framework development means the structure under the tests: page objects or screen models, test data handling, configuration for each environment, reporting that a developer can read, and a CI setup that runs the right tests at the right time.

Our open-source AI test automation framework (Java 17, Selenium and TestNG) shows how we build one: it writes test cases from plain user stories, heals broken locators with AI and logs every heal, and runs in GitHub Actions on every push. For a client we build the framework in your stack, Selenium or Playwright, Java, TypeScript or Python, and hand it over with the first tests already running.

API test automation

API tests check the endpoints your web and mobile apps depend on, without a browser. They run in seconds, break less often than UI tests, and catch most backend bugs before anyone opens a screen. We write them for REST services in Java with JUnit and Spring's test tools, or with Playwright's request API for JavaScript and TypeScript teams, and wire them into the same pipeline as the UI tests.

Our Inventory API project is tested this way at every layer, from unit tests to end-to-end tests that fire real HTTP requests at a running service. For an existing service with thin coverage, API tests are often the best first project: a safety net under the code before anyone changes it.

What is included

  • Test automation frameworks in Java, Selenium and TestNG
  • Test cases generated from user stories with AI, reviewed by an engineer
  • Self-healing locators that reduce flaky failures
  • CI pipelines on GitHub Actions with readable failure summaries
  • Regression suites for web apps
  • Remote work with overlap for US time zones

Good for

  • Startups shipping fast without a dedicated QA team
  • Teams with flaky or slow test suites
  • Agencies that need testing capacity on demand
Pricing

Pricing depends on what you need. After a short call you get a fixed quote before any work starts.

Get a quote

How it works

  1. Step 120-minute callYou tell us how the business runs today and where time is lost. We tell you honestly what is worth building.
  2. Step 2Audit the current setupWe review your tests, CI and release process and list the gaps that cost you the most.
  3. Step 3Build the frameworkWe automate the critical paths first and wire them into your CI.
  4. Step 4Hand over or run itYour team can own it, or we keep maintaining and extending it.

Questions

Can we see your work?

Yes. Two of our testing projects are open source on GitHub: an AI-augmented Selenium framework and the AI Test Triage GitHub Action.

Do you work with US clients?

Yes. Rushi studied and worked in the US for five years and works in US hours when needed.

What hours do you work with US teams?

Standard hours are IST, which overlap with US Eastern and Central mornings. We shift the schedule further for teams on the West Coast when a project needs it.

How much of our QA can be done from India?

Most of it: writing and maintaining automated tests, running regression on every build, exploratory testing and bug reports. What stays with you is product decisions and access to systems. We overlap with US hours for standups and work in your tools.

Selenium or Playwright: which should our team choose?

Both work. Selenium has the larger ecosystem and more engineers who know it; Playwright is faster to set up and handles modern web apps with less flakiness. If you already have a Selenium suite we extend it; for a new project we usually suggest Playwright.

Next step

Tell us what slows your business down.

A 20-minute call is enough to know if we can help. No pitch deck, no pressure.