Systems | Development | Analytics | API | Testing

Imagine you’re a miner with a canary in a cage. If the air is toxic, the canary reacts first, giving you a heads-up. Canary testing works in a similar fashion for your software. Instead of releasing the whole flock (users) into a potentially toxic or buggy environment, you release just one canary (a small subset of users) to test the waters.

According to a study by Stack Overflow, developers spend approximately 50% of their time debugging and fixing issues in their code. As a software engineer, I understand the problem first-hand. We pour our heart and soul into building applications, yet bugs persist despite our best efforts. While some are caught during compilation, others lurk undetected, potentially causing damage and financial woes. That’s why rigorous testing of applications becomes crucial before market launch.

It’s no secret that the expectations for public sector digital services have changed significantly over the past few years; services need to be rolled out fast to ensure usable and secure software that can help agencies deliver on their mission. These expectations can be met by combining DevSecOps with codeless automated software testing.

Testing software is like putting it through a series of challenges to make sure it’s tough enough for real-world use. Whether we’re testing each piece individually (unit testing) or how they all work together (integration testing), we need to be prepared for different situations. Sometimes, testing is tricky.There are times, when we need to isolate parts of our code from their dependencies.

In the dynamic landscape of software development, where agility and precision are paramount, testing reports emerge as a cornerstone for quality assurance, tracking progress, and fostering effective communication among stakeholders. Let's embark on a journey to explore the intricacies of testing reports, unraveling their significance, types, content, and the tools that can elevate your reporting game.

Performance testing scripts need to go through authentication in order to access target services with the right authorization. They also need to validate that the authentication servers are able to handle the target load. OpenID Connect(OIDC) has become a popular authentication and authorization protocol for securing web applications. This article will present the OIDC protocol and how to implement a JMeter script to performance test it.