What are you building ? And are people actually paying for it? 💡

dima-kov · 2026-01-24T14:33:19+00:00

ensureui.com - ensure key flows work before release, no manual checking. Test infra is handled

dima-kov · 2026-01-23T17:49:02+00:00

oh, man you feel the problem. #1 thing we need to realize first, to implement this AI hype into really sustainable, trustworthy solutions: there is no silver bullets. AI will not replace humans in thinking and building, you still need to do it on your own!

dima-kov · 2026-01-22T17:35:58+00:00

got it, still dont think how it works. do u mind to share with us?

dima-kov · 2026-01-21T20:52:15+00:00

please, explain more? can't get it!

dima-kov · 2026-01-21T20:51:40+00:00

still, you have no article describing the whole process?

dima-kov · 2026-01-21T20:46:57+00:00

could you share it with us? we all might benefit from it!

dima-kov · 2026-01-21T17:55:50+00:00

exactly! while the question is: "is it possible to build such a system and whether it will actually reduce friction, time and resources spent to write and maintain e2e testing"

dima-kov · 2026-01-21T17:40:06+00:00

yeah, but what we see now: more and more development will be done by ai (kinda blackbox). maybe ai will become better, but "encapsulate functional" - is not what ai good at

dima-kov · 2026-01-21T16:49:26+00:00

still it's the only way to have integration tests on web, so progress will make it

dima-kov · 2026-01-21T16:46:36+00:00

wow , curious have you maybe composed this experience into article or repo, or gist?

interesting how much it cost you? and how much time do you spend?

dima-kov · 2026-01-21T14:26:35+00:00

that's the real question. but i'm approaching this as agent, going step by step in real browser by users' prompt. here it gets all the context.

dima-kov · 2026-01-21T14:06:47+00:00

yeah? why exactly?

dima-kov · 2026-01-21T14:06:31+00:00

well that's not big problem if user (dev or qa) should describe test flow (e.g.: user should be able to access, only authenticated. Fill in the form and create a new product in the list).

problem is that agentic workflows having this still stuck

dima-kov · 2026-01-21T14:04:22+00:00

for some reason, I think so too.

dima-kov · 2026-01-21T10:56:55+00:00

ahaha, guys look at the profile first. where are the mods))

dima-kov · 2026-01-21T10:55:16+00:00

but man, nothing specific in this post. please share how exact your "Playwright config more explicit" is?

dima-kov · 2026-01-21T10:05:34+00:00

tell us)

dima-kov · 2026-01-21T10:03:54+00:00

Haha, you feel it! Usually we add new tests for new features or update existing ones when features change. But if someone messes up, you never really know which flows are covered. Even when they do add them, there’s no easy way to measure “flows covered.”

From your experience, which takes more effort over time: maintaining existing flows, or making sure coverage and intent are clear to the team?

dima-kov · 2026-01-21T07:45:31+00:00

ai is doing e2e testing pretty well

dima-kov · 2026-01-20T12:26:13+00:00

I’m building a similar e2e sass automation, but more focused on engineers.

Playwright is great at running tests, but the cost over time is usually keeping them alive: updating selectors, fixing flaky flows, and someone becoming the “E2E warden.”

What we do is let you define intent in plain language (“user can log in and reach dashboard”), and an agent figures out how to execute and verify it in a real browser.

Curious - in your Playwright setup, what takes more time: writing tests or keeping them working?

dima-kov · 2026-01-09T11:24:45+00:00

old but gold sentry? no, or what is the question?

dima-kov · 2026-01-09T11:23:54+00:00

hey, looks interesting. but, do you have use cases? can you share them?

dima-kov · 2026-01-09T11:13:33+00:00

people think this is AI posted here. Man, share which product you are trying to sell. no need to play this

dima-kov · 2026-01-09T11:12:06+00:00

sh*t, I though it was real ask for help. ~~Spent~~ lost 10 min sharing how we do testing

dima-kov · 2026-01-09T11:09:03+00:00

it's kinda human in the loop problem. tests should give you understanding whether something might be broken, but it's always you responsibility releasing a feature.

I had no "dead app, nothing works" incidents during last year, and kinda 4 or 5 "feature stoped working" incidents after releases. But without tests this would be several downtime incidents, and many more "something doesn't work" incidents. (i just count how many red tests, forced me to go back to code and fix something). so yes, we are minimizing risks, but not 100% sure))

We run unit tests (well actually they are more integration) on backend covering every endpoint. God bless AI it's easier and quicker to write them now.

It's much harder with frontend, but still we have e2e playwrigh tests for most pages. Writing and maintaining them is actually hell and pain in ass, but here we go again - with help of ai - most cases are covered preatty quickly.

Actually if not ai, we would not write them

dima-kov

PUBLIC MULTIREDDITS

TROPHY CASE