In this series, real (and really good) QA practitioners use their experience to support—or debunk what you might know about software quality. James Espie is a test specialist, a quality engineering proponent, and a continuous learner from Auckland, New Zealand. He shares his insights and sporadic bursts of inspiration in a hilarious newsletter called Pie-mail. If you haven’t seen it, you should check it out.

We all want our websites to be responsive and useful. However, the biggest correlation between website performance and business results is seen by improving the performance and speed of your website. Users get bored if they have to wait for too long to load your website or application. Performance Testing and Load Testing your website and restful APIs will help you understand better how your website and web services behave when a lot of users access your website at the same time.

When someone new joins the company, they're encouraged to do what is called a "Week of Testing" - taking k6 for a spin and presenting your findings to the rest of the team. This article will show you how you can make your test scripts more readable and maintainable. To do that, I'll test a demo application with a custom DSL. DSL is short for a Domain Specific Language, and in this case, it allowed me to write meaningful code specific to our business requirements.

The Kingdom of Quality is in disarray. Everyone works in silos – developers, testers, and other stakeholders. Communication between teams has faltered, making project collaboration nigh impossible. It’s as if goblinkin are at the helm. The damage is inevitable. Buggy releases, missed deadlines, and – worst of all – disappointed customers. It’s time for a quest. It's time for Zephyr Quest.

Did you know that an average user takes only 0.05 seconds to form an opinion on a website? Yes, Sweor’s study on website statistics shows that users decide whether they want to use a website or not in a fraction of a second. We can also note that about 57% of the global population doesn’t recommend non-responsive websites in the same study. In general, most websites or web apps run into errors because of a solitary reason: solid cross-browser testing isn’t performed.