Tester layoffs


Filip Hric

19th November 2024

TESTER LAYOFFS

Hello Reader,
the market has been crazy over last couple of months. Being laid off myself couple of months ago, I know it’s not easy to adjust to the reality of seeking a new opportunity.

I’ve recently read a reddit post telling a story of a tester that has been with a company for 15 years and now getting laid off. He asked about what his next steps should be and whether automation is the next step. I’ve shared my thoughts in a short video as well as a blog.


Blogposts, discussions, events

Laid off as a tester. What now?

With ongoing layoffs in tech, many testers are seeking guidance. In my latest blog, I share strategies and advice for navigating this challenging situation.

Read more →

Is test automation actually manual?

I shared some thoughts on Linkedin recently about the future of test automation. Taking a step back, I’m thing that maybe today test automation is actually quite manual

Read more →

Agile testing days 2024

This week I’m at Agile Testing Days in Potsdam! I will be taking part in a panel discussion today and have my talk on Friday. If you are around, come say hi!


Testing tip:

If you ever needed to wait or multiple requests to finish after a page load, there’s a simple trick that can help you with that. Instead of using cy.wait() you can use cy.get() and use the .all to wait for all matched requests.

 1  it('testing todos', () => {
 2    cy.intercept('**').as('requests')
 3    cy.visit('/')
 4    // set longer timeout
 5    cy.get('@requests.all', { timeout: 30000 })
 6      .should('have.length', 10)
 7      .its('9.response.statusCode') // check last request
 8      .should('eq', 200)
 9  })

Meme of the week


One more thing. If you are currently facing a layoff, hit me up on LinkedIn. My follower count is currently at mid 17k so I can reshare your job-searching post to the wider community. I don’t have the capacity to employ anyone nor have a good overview of current open positions, but I can help you get better visibility. It’s the least I can do.

Stay strong everyone ❤️

Filip Hric

Teaching testers about development, and developers about testing


Twitter
LinkedIn
Bluesky
Discord
GitHub
YouTube

filip@filiphric.sk, Senec, Slovakia 90301
Unsubscribe · Preferences

Filip Hric

Sign up for weekly tips on testing, development, and everything related. Unsubscribe anytime you feel like you had enough 😊

Read more from Filip Hric

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....