Are your tests in Jira growing in complexity? Do you feel you could be more efficient with reusing tests? Does ensuring consistency and standards across projects still feel like a struggle with your existing test management tool? Enter Zephyr Scale, a structured and highly configurable test management solution for teams looking to advance their testing in Jira. Need to see it to believe it? Join us for a quick, around-the-app tour of Zephyr Scale.

Have you ever wondered, while manually creating tests in Loadero, that it would be nice to have some library that you can use to create tests programmatically? Sounds nice, isn’t it? Well, luckily, Loadero does have this option now. In this blog post I would like to introduce you to the recent creation of Loadero’s team — Loadero Java library.

I’ve been testing software professionally since 2001, when I was in my late 20s—when my eyesight was perfect. As I’ve gotten older, I’ve struggled with whether to make the font bigger on my web browser or phone, or to carry my reading glasses everywhere I go. I have to make this choice because some web sites were developed to account for this, and some weren’t. As I get older, this problem is only going to get worse.

This short tutorial shows how to run a k6 test for load testing a database. In performance testing, we often trigger load tests that simulate realistic user flows, particularly those that are most commonly seen in production. This type of acceptance testing usually interacts with various parts of our infrastructure: web servers, microservices, databases, etc. But what if you want to test the performance or scalability of an infrastructure resource in isolation?

The latest release of Klocwork features the launch of JavaScript, which greatly enhances the static analysis and SAST tool’s offerings. In addition, the release includes a number of other significant improvements that greatly enhance the tool’s performance and functionality. Here, we provide an overview of the new analysis engine.

You may have heard the term shift-left testing which is essentially moving the testing to an earlier stage in the project lifecycle, essentially the activity is moved to the left on the project timeline. The benefits of testing earlier have always been understood but not always happened when we consider performance testing which in some cases is still left until the very end of the delivery process.