Nearly a decade back I wrote a lot of browser CI tests with headless chrome as well as browser stack. I loved the idea, but they just didn’t handle things being a bit outside of perfect IRL, like taking a moment longer to load etc. They ended up having a lot of waits in them, taking a long time to write and were prone to being flakey. The tests basically lacked “common sense” and it made me think that one day someone would figure out how to make them work better.

I’m wondering if there are new frameworks, workflows, startups that have made this stuff easier and better. I’m not really in tech anymore but I wouldn’t mind writing some tests if the experience was better.

  • MajorHavoc@programming.dev
    7·
    2 months ago

    RobotFramework is pretty nice.

    The core challenges still exist, particularly with web automation. But RobotFramework at least has much better helper methods, syntax and quality of life tools than a few years back.

    I still don’t typically see teams maintaining anything deeper than a few smoke tests, for most projects.

    Edit: I also see a decent number of folks using PlayWright pretty happily.

    Source: I consult with various dev teams on this kind of thing.

    • Paige@lemmy.caOP
      2·
      2 months ago

      Sounds like just a few integration tests for the core use cases is the ticket, just like before. Real unfortunate, I would have bet that by now that there would be some startup that had made an automated user that you trained to do tests with a chrome extension or something.