Operations | Monitoring | ITSM | DevOps | Cloud

I remember just about three years ago sitting in a companywide meeting in a conference room at the Museum of Modern and Contemporary Art in Lisbon, Portugal (Museu Coleção Berardo, Lisboa). Our CTO, Bernd Engist, was giving us a presentation about some new features we had recently developed on automating the start/stop process of an SAP system.

Delivering business-critical applications and code relies on two key factors; functionality and efficiency. Mock and Unit tests are a few industry standards that aim to ensure the correct functionality of your code, catching potential bugs and issues before deployment. These tests are vital to workflows, CI/CD pipelines, and the overall build and deployment process. While functionality may be sound, one key aspect that is oft-forgotten is the efficiency and performance of your code.

One difficult challenge in the software development cycle is increasing the speed of development while ensuring the quality of the code remains the same. The data world has adopted software development practices in recent years to test data changes before deployment. The testing process can be time-consuming and prone to unexpected errors.

Website regression testing is a form of software testing that helps to identify and fix problems with website content, functionality, and accessibility. It is a vital part of any testing strategy, as it can help to ensure that the website continues to meet user expectations. Website regression testing typically involves running a series of tests against the website to check for any issues. The tests can be performed by an automated system or manually by testers on the development team.

In this article, you’ll be introduced to two different load testing tools that are both able to work with Kubernetes; Speedscale and K6. Throughout this post you’ll be given a comparative view of how each tool performs in five different categories: Ease of setup, developer experience, working with the CLI, creating tests, and integration into CI/CD pipelines.

“Lead time to deploy” means the interval from when the code gets written to when it’s been deployed to production. It has also been described as “how long it takes you to run CI/CD.” How important is it? It’s nigh-on impossible to have a high-performing team if you have a long lead time, and shortening your lead time makes your team perform better, both directly and indirectly.

In a DevOps environment, continuous testing is essential to success. By automating the testing process, you can release new, bug-free code faster, and more efficiently. In this software development tutorial, we will examine continuous testing, its benefits, and best practices.

According to the 2021 test automation report, more than 40% of companies want to expand and invest their resources in test automation. While this doesn’t mean manual testing is going away, there is an increased interest in automation from an ROI perspective – both in terms of money and time. After all, we can agree that writing and running those unit test cases are boring.