“I didn’t plan to build a QA platform. I just wanted to solve the problems I kept facing.”

Where It All Began

Hi, I’m Faraz Ahmed.

I discovered Software QA during my university years. What started with a Software Quality Assurance class, experimenting with Cypress, and a curiosity for finding things that others missed eventually became my career.

There was something uniquely satisfying about looking at a codebase not just as a creator, but as someone examining where the seams might rip under real-world pressure. Most people write software assuming the happy path; QA is about protecting the user when the world isn't so forgiving.

From Manual Testing to Leading QA Teams

After graduating, I worked across different teams, startups, and product companies as an SQA Engineer. Over time, I moved through the entire spectrum of quality engineering: manual exploratory testing, test framework automation, API contract validation, database testing, and eventually deep into mobile testing.

Later, as I began leading QA teams and architecting release pipelines, the scope of the problems shifted. It was no longer just about writing test scripts—it was about engineering velocity. And that was where the cracks in existing tools became unbearable.

The Breaking Point: “Why are we still doing this this way?”

Every mobile QA engineer knows the routine: you write an Appium suite, run it in CI, and wake up to red builds not because the app broke, but because an element's selector shifted by two pixels or a cloud simulator took 45 seconds to boot.

We were paying thousands of dollars every month to stream video feeds of mobile phones from data centers across the continent, enduring 400ms of lag per tap. And when a test failed, nobody trusted the result. Was it an app bug? A cloud timeout? A dropped ADB socket? Or just flaky locator logic?

Eventually, I started asking myself one simple, persistent question: Why are we still doing this this way?

The Genesis of Gravity QA & Graviton

That question became Gravity QA.

I decided to build it strictly from the perspective of someone who actually uses these tools every single day. I didn't want another cloud wrapper or another layer of YAML config. I wanted a desktop-native platform that puts the execution runtime directly on the engineer's workstation, using the physical devices sitting right on our desks.

By taking advantage of native USB pipelines and low-level compositors, we achieved sub-16ms screen mirroring and instant touch dispatch. Zero cloud egress bills. Zero data privacy compromises.

Enter Graviton: Rethinking Mobile Automation from Scratch

While engineering Gravity QA, a deeper challenge emerged: selector fragility. Even if your runtime is fast, tests will still break if locators are fragile.

That journey led to Graviton — our dedicated attempt to rethink mobile automation from the ground up. Instead of brittle XPaths, Graviton constructs an intelligent heuristic graph of accessibility attributes, visual geometry, and parent-child hierarchies. When UI designs change, Graviton auto-heals the locator in real time.

Gravity QA is built from the problems I’ve experienced firsthand. And I’m building the tools I always wished I had.