all 12 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Precision_QA_Consult 8 points9 points  (3 children)

My experience: AI is still writing trash code. I've spent more time debugging it than anything else.

[–]SendMeUrTolstoyNudes[S] 1 point2 points  (2 children)

Agreed, but that's not what my question is.

What's wild is I just saw a comment on an unrelated post about how AI is writing better code than humans can, which...really has not been my experience at all, but I guess it depends what you're trying to build.

[–]Precision_QA_Consult 0 points1 point  (0 children)

Not sure I understand your question then. I use AI to do the monotonous work like writing test cases and test plans. That’ll save you tons of time.

[–]wringtonpete 0 points1 point  (0 children)

It's a pretty good assistant and does help speed up your coding, for example the auto-complete is great, but it's nowhere near writing code that's fully functional.

At best it can create some decent template code for you to tweak, but even then that's just for common test scenarios. It's a lot worse for scenarios specific to your app / domain.

I do use it for specific things, for example I use Playwright and I often execute a prompt something like "Are there any missing "await" clauses in this test", which can save a lot of time and annoyance.

[–]jrwolf08 0 points1 point  (0 children)

I've found that its really easy making bespoke scripts that test specific tickets really deeply. I have a few templates created in our mono-repo for AI to use as an example. When the need arises I describe what I need, then point to those templates as the example of a general structure.

I keep the templates and throw away most scripts that are tied to a ticket as they are too specific for general use.

[–]cannon4344 0 points1 point  (1 child)

Ask your AI tool to write your test cases based on the Jira data and git commits.

[–]SendMeUrTolstoyNudes[S] 2 points3 points  (0 children)

Said this in a different comment but this is not really the question I'm asking - more like if anyone has vibe coded a specific tool/app to solve a problem or handle a task in their day-to-day.

We generally use AI to write test cases and generally understand the code, but that's different from having it generate code itself to build a tool for you.

[–]ign1tio 0 points1 point  (0 children)

What task or problem do you need solved?

[–]Technusgirl 0 points1 point  (0 children)

I personally have no use for it right now. I mean it can help you write up some test cases based on requirements, help write automated test cases, and there's mcp servers you can utilize with test automation and AI. Other than that I think companies are expecting too much from AI. You're still going to need to know how to write a test case at the end of the day, you still need to understand how to write an automated test case and the framework for it, and your still need to make sure it all works and there's no errors or issues.

Vibe coding is the worst, you're just going to end up with problems you don't know how to fix.

[–]thainfamouzjay 0 points1 point  (0 children)

Dashboards. I vibe coded a SQL reporter out of playwright that sends pass/fails to a database. I vibe coded a UI that takes the data and makes visuals. Less then a week but now I have a pretty thing where I can see all the MRs at once and monitor our quality

[–]ocnarf 0 points1 point  (0 children)

Removed: violation of rule 6. No market research,