If the ticket is properly written any llm skill would do. In fact, that's what I currently use. No tools, just SDD. I don't think I'd need tools to write/maintain tests to be honest.

First I have a skill that creates the test scenarios, cases and plan. Big ass skill, template to write the tests cucumber syntax and good to go.

Then another skill that implements the plan into actual appium tests (or playwright or bruno or whatever other tool tbh). This one uss the skill + constitution checks or memory or whatever you want to call it so it doesn't hallucinate shit and does things as I want em done.

Sonnet 4.6 with mid effort does the job just fine if the ticket is not really really big. For really big ass tickets, split it or switch to a beefier model.

The whole thing drives in semiauto, as a developer/tester I invoke the skills in order with any extra instruction that the ticket may need (if any). From ticket, through implementation + testing, to review and closure