|
Hello Reader, It took me some time to realize, but you actually can run your Cypress tests locally in parallel. This part is the most criticized one among Cypress users, and I can’t believe how easy it is actually to set up. All you need to do is to use these two packages: 1. concurrently - to run your tests in parallel 1 // package.json 2 "scripts": { 3 "cy:parallel": "npx concurrently 4 \"cypress run --env split=2,splitIndex=0\" 5 \"cypress run --env split=2,splitIndex=1\"" 6 }, And that’s all there’s to it! New Cypress Course ProgressI've been heads down over the weekend, pushing forward on my upcoming Cypress course! While I’m running a bit late, I did manage to sneak in a little creative break designing the course logo. It’s starting to come together—can't wait to share more with you! Advanced Cypress InterceptingI've discovered how to run Cypress tests in parallel locally using the cypress-split and concurrently packages—a game-changer for handling large test suites. 1 Cypress.Commands.add("waitAlias", function (this: any, pattern: RegExp) { 2 return cy.wrap(null, { log: false }).then(function () { 3 const matchingAliases = Object.keys(this).filter(alias => 4 pattern.test(alias), 5 ); 6 7 if (matchingAliases.length === 0) { 8 throw new Error(`No aliases found matching pattern: ${pattern}`); 9 } 10 11 return cy.wait("@" + matchingAliases[0]); 12 }); 13 }); Meme of the week Take care! |
Sign up for weekly tips on testing, development, and everything related. Unsubscribe anytime you feel like you had enough 😊
Hello Reader, If you’ve been reading this newsletter for a while, you know that quality engineering is the hill I’ll always choose to stand on. And this week, I get to share something personal that ties directly into that. I’m joining Qodo I’ve been following Qodo for almost a year now, and I’ve been getting more and more impressed every day. So I’m thrilled to share that I’m joining Qodo as a DevRel engineer. Qodo is an enterprise multi-agent platform for AI-driven code reviews. As AI...
Hey Reader, An interesting thought is popping up in conversations around AI agents: the environment around the thing matters more than the thing itself. Last week I read about Harness engineering and it felt very familiar. As if it was tapping into instincts I already had. If you’ve ever debugged a flaky test only to find the problem was in the setup, not the assertion, that instinct will feel natural. But at the same time it also feels like an unfamiliar territory. It borrows the same...
Hello Reader, AI can generate code, arguably with a pretty decent quality. That’s not news anymore. The question that’s been forming in my head all week is different: how do we decide what should go into production? Writing code is not the hard part (arguably, it never was). The hard part is making sure the right code ships and the wrong code doesn’t. And right now, that selection problem is becoming the defining challenge of AI-assisted development. Last week has definitely showed this....