re: I needed browser automation for testing, so I obviously wrote my own tool VIEW POST


Have you looked into It is what I moved on to then Phantom when EOL. I'll take a look at what you got here and try it out.


I saw it, although never really worked with it. While it looks like a better alternative than the ones I listed, back when I learnt about cypress I already had wendigo going on, and the scopes seem slightly different, wendigo is just an agnostic browser automation tool while cypress provides a whole framework for testing + CI infraestructure, plus the actions and assertions provided (at least for what I saw in the docs, it may have changed) don't look nearly as varied as what wendigo already has (obviously by now I'm completely biased so take this answer with a grain of salt)

code of conduct - report abuse