There are many examples of a QA stepping out of their comfort zone and doing things that, in most cases, shouldn't even be on their plates. This article aims to go through some of the roles or situations you might encounter on your project and hopefully help you better understand and identify those situations.

We bring you the story of Ratko Dodevski, Staff DevOps Engineer at the Skopje engineering hub. His impressive 11-year-long path of discovering different fields and roles resides in his one true passion - technology.

In this article, we are going to talk about git branching models (strategies, workflows), which one to choose for your team depending on the setup, what are the pros and cons, and how to decide which one is for you or why would you even need it in the first place.

QA Engineers write and perform tests. Unit tests, as their name implies, are tests. Shouldn’t QAs write unit tests as well, then? The straight answer to this question should be - absolutely not. Writing of unit tests should be reserved solely for developers.

What is day-to-day business for a QA? What are the processes a QA team relates to? How does the QA team fit an Agile organization? What are the main contributions QAs enable teams with? When and what do you automate? How does a QA Engineer become a bottleneck in delivery?

KEDA is a Kubernetes-based, event-driven Autoscaler. With KEDA, you can drive the scaling of any container in Kubernetes based on the number of events needed to be processed. KEDA is a single-purpose and lightweight component that can be added to any Kubernetes cluster.