One of the basic ingredients of any software is that before you deliver it to the end user you want to make sure that it works properly. The question is how we need to adapt our approach to testing to take account of the cloud-based, highly distributed nature of serverless architecture.

So you want to A/B test your web app. The idea is simple, but the details can get messy, and you don’t want to re-invent the wheel. Services like Optimizely are pretty good, but they can be expensive and full of features you don’t need immediately. In this post, we’ll share how Sentry wrote an experimentation system with minimal work.

Like any other creation in progress or in the making, serverless applications, need to be tested and monitored. How else would you know if what you’ve created is providing desired results? Before putting your “newborn child” out into the world, you must make sure that it’s ready for the world. Software or even hardware of any sort will first be tested before it goes to mass production, and the same goes for your serverless applications.

Ecommerce companies completely dependent on the internet for revenue experience increased pressure to provide an always-available, always-working shopping experience for customers. Nasdaq puts estimates for ecommerce-facilitated transactions to be up to 95% by the year 2040. During Black Friday through Cyber Monday 2018, Shopify reported their merchants sold up to $37 million per hour through their ecommerce platform.

We know Node.js for its lightning-fast performance. Yet, as with any language, you can write Node.js code that performs worse for your users than you’d like. To combat this, we need adequate performance testing. Today, we will cover just that with an in-depth look at how to set up and run a performance test and analyze the results so you can make lightning-fast Node.js applications.

Quality assurance is a priority at Evolution Gaming, the world leader in live casino gaming, and as Andrejs Kalnacs, Lead Software Developer in Test, said during his GrafanaCon EU talk in March, Grafana has been a game changer. While Kalnacs and his team have found Grafana to be invaluable in many areas, here are three best practices they’ve learned throughout their journey.

So much of our world has moved away from the slow and methodical, towards the agile and iterative. In transport, for example, everything is “on demand”, constantly changing and adaptable. The same is true for developers. With movements and philosophies such as CI/CD, everything is about moving quickly, yet smartly. Test automation is an integral part of this development philosophy.

Recently we’ve had a lot of requests for examples of how add new tests through the StatusCake API using the popular Postman tool. In this article we’ll take you through some of the steps required to get you going with this method, below you’ll find an example for each test type we offer, taking you through the process of adding a test.