Software engineers tend to be enamored with complexity. It’s a self-serving instinct, and what do you know, but management falls for the lie. Every. Single. Time.
Unlike app development, QA automation always deals with two codebases in parallel: 1) automation code, 2) the actual application under test. Let’s take a look at the relationship between these two – specifically, stable and unstable branches, and how “cross-targeting” these branches can improve your automation results big time.
Wherein Ruby beats Python. Smashes. You might even say defenestrates. Take it from a QA automation dev who’s used both for years: it’s not even close.
Techniques to improve quality by limiting the number of changes late in a release cycle. Plus sausages, Mercedes-es, and a lesson in Computer Science from the Sweet Science. Let’s get ready to rumble!
Android Espresso tests are pretty unwieldy out of the box. Here’s a take on better architecture through layers.
So long, and thanks for all the code !
QA is boring. Let’s write our tests with bullets !
A modest extention to React Native Web with immodest ambitions.
These days we equate good QA with automated tests. But quality is fundamentally about excellent process. Here’s a common-sense, reality-friendly route to better quality, and better automation as well.
The standup monologue “What I did yesterday, what I’m doing today, am I blocked” is inefficient and sucks up valuable collaboration time. Here’s a metrics-based alternative.
Push your React Native development workflow into the browser and be amazed at the speed and new possibiltiies.
Software executives and managers not knowing enough about technical implementation, means procrastination, smoke + mirrors, and potentially catastrophic wasting of time and money.