niteshnagpal

Thanks - this helps sharpen the scope.

To clarify the intent: I’m not trying to automate tests or recreate flows the way Selenium/Cypress do. Those tools are for running flows; my problem happens while building flows.

When I’m iterating on a UI or fixing a bug deep inside a multi-step process, the slow part isn’t writing a test — it’s manually getting back to that state after each code change. That’s where the 30–90 minutes disappear.

You mentioned rigging a harness. That’s exactly the behavior I see in teams: everyone builds their own one-off harness, scripts, or shortcuts. The idea here is to replace that glue code with a generic, one-click “jump back to this state” snapshot.

So the goal isn’t automation or testing — it’s eliminating repetitive environment setup during local development.

I agree that building a minimal prototype for myself is the right next step. If it genuinely reduces the friction I hit daily, I’ll share it with others and see if the value transfers.

Appreciate the thoughtful feedback.

You’re right - it’s not a testing tool, and I should’ve framed it more precisely.

I’m not trying to replace unit tests or integration tests.

The problem I’m solving is much simpler and happens during development, not during automated testing.

When working on big web apps, I often spend 30-90 minutes just navigating or recreating state (auth → forms → data → steps) to reach the screen I’m actually working on.

The idea is a browser extension that lets you:

- capture the current app state (URL + local/session storage + cookies + form inputs) - and instantly restore it later - so you can jump straight back to that deep state during local development

It’s basically a workflow accelerator for manual dev, not a test framework.

Does that distinction make more sense?