Aside Automated Testing

Inspecting Chrome elements requiring focus

In the web app I work on we have some elements which are only rendered when their parent element has focus (such as a select list with options) but the child elements disappear when focus is lost (I don’t think this is great behaviour but that’s another story).

I had trouble inspecting these elements in Chrome devtools since using the inspect tool would remove focus, and even using F8 to pause the debugger would also lose focus before it was paused.

I found this code snippet online that can pause the debugger 3 seconds after posting it in the devtools console – which is enough time to put the element in focus and at that point the DOM is paused or frozen so you can inspect the elements in devtools as much as you like.

The script is pretty simple – change the number of milliseconds to suit you but I’ve found 3000 ms is a good amount of time:

setTimeout(function() {
}, 3000);

Microsoft Teams

Most of my meetings nowadays are held online.

I hate being late to meetings, but I also like getting things done. When my calendar gives me the reminder about a meeting 10 mins before I’ve developed a habit of joining the meeting straight away so I am already in the meeting when other people join. That way I can continue my work without forgetting to join right on time. I’ve found if I don’t do that I’ll dismiss the notification, get caught up in my work (flow) and forget to join.

This was all well and good at my previous company where we used Google Meet. But my current company uses Microsoft Teams and when I join 10 mins early everyone else invited to the meeting gets a notification telling them I’ve started the meeting! Who designed Microsoft Teams thinking that was a good idea!?!

Any ideas how I can work with this?

Aside Software Testing

Quality Advocates

“What I’m seeing more and more of, is the test-always, or test-as-quality-accelerant  – or maybe, with a nod to Atlassian, the quality-assistance school. In more and more teams, testers are taking on the role of quality assistant, quality coach, or quality experts. Rather than existing in a separate team, they are members of feature teams and take on the responsibility for ensuring that the entire team embraces a quality culture. Yes, they absolutely bring testing expertise to their product or feature area, and they test the product more than anyone else on the team; but they also help other developers write and improve their own testing and think a lot about the customer experience. Good developers are extremely capable of writing tests (including service monitoring and diagnostic tools) for their own code, but testing experts ensure that the end-to-end experience and other big picture items (e.g. load or perf) are covered as part of the daily work.

Teams with testers like these typically do not have a release phase since they are (typically) releasing often or always.”

Alan Page – April 2017 #

Many years later I still think a small development team with a product owner and a single strong tester/quality advocate/paradev is the best way to produce software consistently and predictably.