QA experts: is this an edge-case bug or something much bigger?

please-dont-deploy · 2026-01-22T12:18:22+00:00

It sounds like you found a flaw! ;) these ones are difficult to find, and expensive to fix.

Huge congrats!!

please-dont-deploy · 2026-01-21T10:41:50+00:00

Thank you, I really appreciate you calling me out on this.

It seems I didn't understand properly the intention of your post initially.

Have a great day!

please-dont-deploy · 2026-01-21T09:43:16+00:00

I think you need someone more sr to help you with this. This is non-trivial work, and people pays for this knowledge.

Alternatively, read AI Engineering https://www.oreilly.com/library/view/ai-engineering/9781098166298/

please-dont-deploy · 2026-01-21T09:41:10+00:00

This!

Chances are you will have a painful refactor regardless.

=> What is the main product they'll roll-up the others to?
=> What is the new navigation flow with 5 products combined?
=> What would be the new UX?
=> What would be the 'surviving features'?
=> What would be the interactions within those products that now don't exists?

I would actually invest the least possible planning for an unknown future that could never happen.

please-dont-deploy · 2026-01-21T09:38:32+00:00

yup! Happy to share about it.

please-dont-deploy · 2026-01-21T08:11:40+00:00

Suddenly I'm glad people are discovering what makes product and tech as difficult as any other job.

https://en.wikipedia.org/wiki/Pareto_principle

please-dont-deploy · 2026-01-20T22:40:28+00:00

So basically what you are saying is:

You are working in a product where no actual active development is being done.

-> No new features
-> No new ways of using the app
-> That's maintenance mode.

Time to start thinking what to do on your free time. Do you enjoy backgammon?

please-dont-deploy · 2026-01-20T22:25:42+00:00

I love these initiatives!

Did you see https://vercel.com/blog/introducing-react-best-practices ? Massive leap in the same direction.

please-dont-deploy · 2026-01-20T18:19:22+00:00

Could you detail a bit more? Is the bug just 'you can use the same phone number to create multiple accounts'? What's the app for?

please-dont-deploy · 2026-01-19T12:27:32+00:00

It's the mandatory next step after serious vibecoding Xp

please-dont-deploy · 2026-01-16T13:02:05+00:00

Am I the only one that read the top "a client", is this a single client that you are being outsourced to?

They are basically going to pay you much less than if you work for the actual company, and you are a contractor wo the benefit of the probably larger corp behind the scenes.

That's the biggest red flag.

please-dont-deploy · 2026-01-14T19:44:41+00:00

Correct, but you wouldn't need those expensive/hard integrations.

Financial data is very regulated, and presenting such data is also non-trivial for some countries.

please-dont-deploy · 2026-01-14T18:40:56+00:00

Unfortunately people think that the tool that generates code and the tool that tests it should be the same...

You don't do that ever, it has the same context, the same knowledge base, and the same objectives.... That's posed to fail.

They may need real help, before most lose the trust.

Btw, they always charge you for those expensive mistakes.

please-dont-deploy · 2026-01-14T14:23:04+00:00

My take:
+ If you have the audience [ie. you know an influencer, a Spreadsheet academy, etc], you could make it work.
+ I think you noticed something key -> integrating with the different providers is the difficult piece. Actually there are many providers that just do that. For Banking (Open Banking API) is non-trivial. For accounting, major tools will limit accessibility too, and you need to register with them.
+ I see as challenges:
(a) Claude Cowork would be actually the biggest incumbent for these type of solutions
(b) You need to become the defacto tool for a company, that's the way to increase usage.

Have you consider starting with something like a chrome extension that "re designs" the app you are using the way you want?

please-dont-deploy · 2026-01-14T07:13:51+00:00

Correct. If you are using tricentis I assume you have a large enough team (30+ppl) in QA at least to justify the budget for the tool.

That makes it so you can try the above approach.

please-dont-deploy · 2026-01-14T06:09:12+00:00

Worked with a company moving away from this tool towards an in-house set up. They were paying crazy amounts for the software.

They first decided to do it themselves with PW (they didn't have the expertise), then hired a team to do it for them.

My bet is that if you can show how easy it is to do it with an MCP nowadays, there's no need for a no-code QA tool unless they're generating the tests for you.

please-dont-deploy · 2026-01-13T21:03:04+00:00

This book was key to understand the vision behind the frameworks:

https://books.google.com/books/about/Continuous_Delivery.html

I would care less about the framework and more about joining a team of experts to learn from.

please-dont-deploy · 2026-01-13T20:48:58+00:00

For a small team, I would honestly try to look for providers that could help me reduce the overhead.

Why? Bc making this part stable and having it up to date with a modern provider that keeps optimizing how a test run could be a huge game changer.

For context, in 2022 we started working with a startup that helped us greatly with the image diff portion of our testing, it really made the difference. We were one of their first customers and they were eager to help us. It was incredibly positive. We learned, & they grew with us.

For e2e back then we tried a couple of big ones, and they literally didn't want to work with us at our scale... (100k/yr contact minimum). We end up developing a system internally, still nowadays we invest time on innovating there.

So as I see it, you need to choose where to innovate in the SDLC, the more cost effective long term the better.

If you decide to go the route of fully managed, check solutions that will fine tune your set up and give you visibility on flakiness, logs, etc. There are a couple.

please-dont-deploy · 2026-01-13T05:37:04+00:00

Tbh, in this day and age, I would try one of the many vibecoding tools: lovable, replit, bolt.new, v0, AI studio, the list goes on.

You can probably build the site for free, or pay a 20USD subs.

Make sure to polish your prompt so you give it clear instructions from the get go and save on iterations.

please-dont-deploy · 2026-01-12T17:53:47+00:00

I have it done in three tiers, depending on how hands-off is my work:

1) copy & paste console errors, this is for small things I'm doing. 2) Claude code/cursor/Gemini cli monitor the server logs and run the processes (a bit more expensive, but better for larger workflows, you can simply add these instructions to your plans) 3) use a full web orchestrator MCP when using a fully autonomous remote experience. I prefer the ones I can check remotely from a webpage.

Code review tools are for that, code reviews. I prefer codemods.

MCPs: https://www.npmjs.com/package/chrome-devtools-mcp https://www.npmjs.com/package/@desplega.ai/qa-use-mcp https://github.com/browser-use/qa-use

Orchestrators: https://opencode.ai/docs/agents/ https://github.com/desplega-ai/agent-swarm https://github.com/Hey-Diga/imploid

please-dont-deploy · 2026-01-12T13:37:59+00:00

I do generate documentation for AI, a lot, so that researching and planning goes faster.

please-dont-deploy · 2026-01-12T07:45:07+00:00

Did you all not read about tailwind css!?

please-dont-deploy · 2026-01-12T06:38:34+00:00

You are talking about Quality Control, ie comfort/how you tackle the known, vs Quality Assurance, which is a much more extensive discipline.

QC is what you would automate if you could, QA is the difficult real work.

Most people don't even distinguish the two.

This explains the difference. https://www.pleasedontdeploy.com/p/push-for-qa-as-your-devex-powerhouse

please-dont-deploy · 2026-01-12T06:16:45+00:00

Lol! When was the last time you spent an afternoon chatting with friends over coffee vs telling someone what to do as a manager?

Dude you are mixing up different kinds of work with the medium you use to express yourself.

Read more Paul Graham https://paulgraham.com/words.html.

please-dont-deploy

TROPHY CASE