Introduction
Harnessing Network Events in Testing
Playwright and Cypress are well-known for their ‘autowait’ feature. This neat trick aligns elements seamlessly and avoids many ‘test flake’ issues, like Selenium’s StaleElementException and NoSuchElementException. However, I’m skeptical about this so-called ‘magic’ in testing. A reliable test should avoid unexpected variables that are meant to simplify the process. I don’t like accepting hidden 3rd party logic influencing my tests without scrutiny; I believe in thoroughly dissecting and analyzing everything to ensure test reliability. A deep understanding is also very valuable for troubleshooting and grasping what tests are actually doing with whatever’s under test.
I designed a homepage under 1kB recently. Although I reverted it after a few weeks, I decided to write a blog post on why I made it and the reason behind my decisions.
In addition to verifying software functionality, testing is where we assure that we meet our non-functional needs. If we treat emissions as a non-functional need, is it an appropriate place to hold ourselves accountable for our software’s energy use and emissions?
How do I put this? Sometimes you’ve got to test. Not talk about testing, not agonise over planning, but get stuck into adding value as quickly as possible. In this blog post I investigate the popular restful-booker web service. From first impressions to reviewing the shippable quality of the software. Let’s imagine I’ve dropped into the project late, I know nothing about what’s under test, and I’ve only got two hours. We’ll see how it goes!
Sometimes I write things in Slack conversationally that might be useful to refer to later or reflect on. Going forwards I’ll try to remember to add them here.
