My approach to software product delivery revolves around discovering the least amount of work we need to do to:
1. Validate & understand the problem.
2. Solve the problem.
3. Delight the customer.
Often we have to iterate through step 1 many times before we get to step 2.
#blogged: Harmonising Selenium with Playwright and Cypress: A Journey Through Network Event Handling. I presented this at Test Talks Wales last week and received positive feedback. What do you think? #softwaretesting#qa#selenium https://t.co/QoqDiDth8y
@zkochan Many JavaScript quirks like this aren't mindblowing when you check the docs. "The default sort order is ascending, built upon converting the elements into strings, then comparing their sequences of UTF-16 code units values." https://t.co/qfF0YdSivz
Even if proprietary software has a greater market share, OSS will always come out on top. You're going to have the rug pulled out from under you. Postman to limit collection runs to 250/month (including those run on your own infra) w/ professional license. https://t.co/GqpP0B5YGz
@joe_jag I’ve softened my response to e2e test focus these last few years. Write the test that needs to be written, be that from a technical/integration/stakeholder management point of view.
@webtesthub I feel like people who “cheat” an interview will be quickly found out and word of mouth will spead. Particularly if they’re an agency candidate where the fee is then refunded.
@ckenst Not in a tweet. 😅 Looking for code that has non-mockable cyclomatic complexity is one that comes to mind, i.e code with paths with collaborators that can’t be swapped with test doubles (for whatever reason).
@heather_reiduff My shortest post is not worth mentioning, just an idea to copy and paste things I wrote in Slack if I thought they warranted hanging on to (they didn't). Analytics wise, my most 'popular' post is probably this one that talks about testing practices. https://t.co/dh4tPMSnqS