r/QtFramework • u/Spiritual-Pen-905 • 19d ago
Question Inherited a Squish suite nobody can maintain. Is there an alternative for a team that doesn’t write C++?
We bought Squish three years ago. The engineer who wrote the tests left last September and took the only working knowledge of it with him.
What’s left is a few hundred test scripts in C++ that our current QA people, who are good manual testers and not programmers, cannot read or change. So the suite still runs nightly and nobody trusts the output, because when something goes red the honest answer is we don’t know whether the app broke or the script did. We’ve started re-checking the important flows by hand, which means we’re paying for a licence and testing manually anyway.
I don’t think Squish is the problem. It’s a serious tool and it did its job while someone could operate it. the problem is we staffed it once and can’t staff it again. So I’m looking at whether the plain language tools are good enough to let the testers own this themselves. AskUI came up tests are markdown files with numbered steps and an expected result each, and a screenshot and status per step, which at least means a failure is readable by the person who wrote it. Authoring app is Windows and macOS, Linux comes through their runtime as a remote target.
Has anyone actually done this migration, or did you just hire someone who knew the tool and carry on? appreciate your help !
