During your Android developer career, you may reach a point where you will have to develop Android libraries or Gradle plugins. In this article, we will discuss the most important aspects and differences of testing these!

Many software companies have no formal quality assurance strategy, and those that do take one of two inherently flawed approaches: Either they (a) ask developers to do QA or (b) delegate QA to a siloed team, whether it’s internal or outsourced. Having been in the QA space for a decade, we’ve learned that both approaches are deeply flawed.

Evolution is perhaps the most common norm in the world of software development. Of course, automation is no stranger to this process of evolution. Globally businesses have evolved from the conventional Waterfall model to the modern Agile and DevOps, thereby embracing digital transformation. We’ve come quite far in terms of automation testing too.

Most software development organizations now follow agile scrum methodology. In most cases, they divide their work in sprints – a repeatable fixed time-box during which all tasks for a deliverable are planned and executed. After each sprint, the target is to complete as many planned tasks as possible and come up with a deliverable. A user story is the smallest unit of work in an agile framework. A user story is further divided into tasks to be taken up in a sprint.

In this article, we’ll showcase how to use k6 for performance testing within CI/CD pipelines. We’ll be using a playground we set up for this purpose and lead you through the necessary steps to get a feel for how it works, and hopefully by the end you’ll start thinking about how to implement this in your own projects.