Operations | Monitoring | ITSM | DevOps | Cloud

To release reasonably secure products, vendors must integrate software security processes throughout all stages of the software development lifecycle. That would include product architecture and design; implementation and verification; deployment and monitoring in the field; and back again to design to address the changing threat landscape, market needs, and product issues.

Picking the right performance testing tool can be a challenge. What should you look for and what is important? Performance testing is a phrase many developers have come across at some point, but what is it exactly? In simple terms, performance testing is a software testing practice used to determine stability, responsiveness, scalability, and most important, speed of the application under a given workload.

So, you’re interested in reaping the rewards of API and automation, but you don’t know where to start? Have you heard people using the term “API” and wondered what it is? Maybe you have a vague idea, but you still have no clue what to do with one? You’ve come to the right place! We pulled together this terminology to help you gain a basic understanding of web services and web API, which will also help you grasp the major concepts of API Testing.

Security testing is a key component of software quality. A program may meet functionality and performance requirements, but that does not guarantee security. In this blog post I will present different security testing methods and provide a few tips for conducting a more secure code review. But first, let’s understand what software security is intended for.

The widespread adoption of the cloud has transformed the way applications are developed just as much as it has transformed the way they are deployed and consumed. In this blog we look at how Network-as-a-Service (NaaS) can help developers support the complete application lifecycle by unlocking the value of PaaS (Platform-as-a-Service).

Any software development project will almost certainly have through several tests by the time it is finished, especially in an Agile testing environment where testing and development occur simultaneously. But, no matter how many tests you've conducted, there's really only one way to tell if your software can handle the actual demands your army of end-users will be throwing on it once it's nearly finished. It's known as load testing.

Today’s software testing trends show the growing demand for more efficient and automation-oriented API testing. Many of the current test automation solutions focus on the UI, while most API-level testing is still done manually. As a result, testers are in need of easy-to-use, intelligent automation tools for testing APIs — improving their productivity and efficiency, while also reducing time-to-market.

On the last day of GrafanaCONline in June, our CEO Raj Dutt announced that Grafana Labs had acquired k6 , the company behind the open source load-testing tool. In fact, our relationship with k6 had started more than two years earlier. At the beginning of 2019, we were working on replacing Grafana’s “remember me” cookie solution with a short-lived token solution for the Grafana 6.0 release.

Cloud native API Testing comes with a lot of challenges. In this video see how to overcome these challenges with the novel approach of traffic replay.