We're currently using Cypress for some automated testing on a recent project and its extremely brittle. Considering moving to playwright or puppeteer but not sure if that will fix the brittleness.
787 karma · joined March 18, 2020
We're currently using Cypress for some automated testing on a recent project and its extremely brittle. Considering moving to playwright or puppeteer but not sure if that will fix the brittleness.
I'm still trying to figure out the answer to that question for myself. Maybe the answer is, "Probably not, and it probably doesn't matter" but I'm still trying to figure out what kind of downstream effects that may have later on my judgment.
This leads to fun tech support calls if you use your own equipment where you're basically proving to the support underling that you know how to run your equipment for the first 20-30 minutes before they take your issue seriously (yes, the modem light is green, yes, I've already power-cycled, yes, I'm testing on a wired connection, etc)
How do you reach that conclusion? There is nothing mentioning signals in the docs anywhere.
I do find Claude Code to be really good at exploration though - like checking out a repository I'm unfamiliar with and then asking questions about it.
Are the sensors/fitness programs on Pebble on-par with apple watches?
I wonder if there's a way to migrate over my years of recorded data over.
Apparently influencers get a lot of unsolicited pressure to take stances on things like Palestine even if they're just a crafting influencer.
The best I've found is the github v3 API but it would be nice to review different approaches.
How does it give me a starting point for "Fix bug tickets that came in over holidays" or "run to trader joe's to pick up groceries"? If this isn't a good use case for it, what kind of events are?