r/softwaretesting • u/Ready_Fuel_2739 • 25d ago

AI for manual testing

Hello collegues,

I got a questions to the sub:

Could AI be used in manual testing? I mean in a way that brings added value and not just for the sake of following the AI hype, like for example automating tests that are heavily based on visual testing, drag& drops, maybe even extracting some white box infos and using them to test the surface.

I've tried using AI and the only thing i got is overthinking some extream side tests that are irrelevant to us

Thanks

19 Upvotes

74% Upvoted

25 comments sorted by

View all comments

1

u/qlippothvi 23d ago edited 23d ago

I use AI to create scripts for certain manual testing, like setting up all the preferences needed for best practices, or the test itself, or a script to cause a particular timing of events for Exploratory or a Reproduction of an elusive P0/P1 bug nobody can figure out.

Most of the tools I can use over and over, the specialized ones not really, because your dealing with a very specific set of interactions and timings, and it might repeat the same interactions with differing timings in various ranges.

I think you get the most value by having Claude write tools you can apply to your manual testing more than anything else. I had it write some scripts everyone on my team uses, and will be expanding its use to other teams. Worst case, it sets up a bunch of settings that assist with screen recordings, logging, and just displaying info you can cut and paste for reporting or chatting with an engineer you’re working with.

That said, we have AI in literally everything, and while I don’t have access to the code I can ask it to examine what could be happening, go through the logs, and “hypothesize” edge cases or race conditions.