
Improve your automated tests
How to test software using Gherkin? The tests are built using phrases that even a non-technical person can easily understand.
Go to content|Go to the main menu|Go to search
You probably know that joke where a tester walks into a bar, orders 0, 1, -3, and 9,999 beers, a lizard, leaves for the bathroom, and the bar bursts into flames. It’s not actually all that far from the truth. However, it’s always better to have quality assurance in a project right from the very start. The ability to understand requirements and anticipate issues is something we encounter daily in software development.
Quality management can easily apply to other areas of life too — which is why I prefer using the broader title QA instead of SQA. Dropping the word "software" from the acronym might seem like a tiny detail, but it expands your scope to completely different fields. Like buying a child's bike, for instance.
During a home grooming session, we decided that a balance bike was no longer cutting it as a means of transportation for our little one, and it was time to upgrade to a "higher caliber."
Clear requirements and specifications are absolutely vital to a project's success. So, we conducted precise measurements, did a bit of market research, and logged everything into our project management system of choice: WhatsApp.
Even though we, as stakeholders, had our own ideas, we had to leave one critical element entirely up to the end user. Picking the color plays a massive role, and we didn't want to leave anything to chance.
Some parameters are purely technical, while others are more emotional. In both cases, however, they play a crucial role, and at the end of the day, it's the user who decides whether the project is a success or a flop.
With the main parameters — frame size and color — fully defined, we had to ask ourselves: is that enough? Initial analysis revealed that there were other critical factors to consider, such as user experience and the overall UX of the vehicle itself.
While the vehicle's total weight turned out to be a secondary metric, the ability to easily strip off the pedals — allowing us to convert it back into a balance bike during the transition period — was a non-negotiable feature. Don't get me wrong, the tools and know-how for a teardown were readily available, but it all comes down to time: there is a big difference between a 1-minute "on-site" hotfix and a "next-day" turnaround!
When planning, you need to look at things from every possible angle, envisioning exactly how the product will be used and what scenarios might play out. Defining potential risks and bottlenecks early on — and actively working to mitigate their impact — should be a top priority for any project manager.
We also had to factor in safety. Before even purchasing the bike, we decided to secure a critical security component: it’s much better to have the helmet ready to go while looking forward to the new bike than to stare at a new bike sitting in the garage while waiting on a helmet. Getting the timing right for each phase of a project is everything.
A handlebar basket is a fantastic feature. It looks great, and the option to bring along a stuffed animal can sometimes be the deciding factor in whether the ride happens at all. However, historical data from the previous vehicle showed that a basket is a massive distraction; monitoring the stuffed animal's comfort level consistently took priority over steering. Consequently, we decided to drop the basket for the initial launch and move it to the backlog. You don't always need to ship every single feature with the first version — sometimes it pays to hold back and roll them out incrementally based on real-world conditions.
Sizing up and testing the right model happened alongside the helmet purchase. The timing here was perfect: being on our way to a festival with a car already packed to the brim with musical gear gave us a rock-solid, easily explainable excuse for why we couldn't take the bike home right then and there. This bought us the perfect buffer zone to make our final decision. It’s always better to schedule a release with a bit of breathing room rather than rushing it!
Plus, with Children's Day right around the corner, there was a solid chance the retailer would drop a discount on kids' gear. Capitalizing on a chance to lower project costs is always a win.
Deployment day is finally here. The bike is reserved and waiting at the shop. There's plenty of trunk space cleared out for transport, and the weather outside is perfect — an ideal day for testing a new vehicle.
Just to be safe, though, I'm doing a double-check on our home first-aid kit and putting the finishing touches on a mobile "pocket-sized" version. Having teddy-bear band-aids and sting-free disinfectant spray on hand is always a smart move. We have to plan for the fact that beginnings are usually rocky, and a child's first bike ride — much like a major software release — is no exception.

How to test software using Gherkin? The tests are built using phrases that even a non-technical person can easily understand.
Thank you for your interest in subscribing to our newsletter! To complete your registration you need to confirm your subscription. We have just sent you a confirmation link to the email address you provided. Please click on this link to complete your registration. If you do not find the email, please check your spam or "Promotions" folder.
