Systems | Development | Analytics | API | Testing

The first time I learned about snapshot testing was in the context of front-end testing. It made a lot of sense. Writing an assertion-based test to check if a component was correctly rendered as HTML is tricky. And difficulty grows with the complexity of the output. Snapshot testing seemed a reasonable technique to get the job done, even with some caveats.

This blog post is about testing microservices and distributed systems with JMeter. It will focus on the principles of performance testing applications that are architected this way. We will not look at which JMeter samplers to use in order to generate a load against microservices or how to configure these samplers. This post will consider best practise and consideration in designing your performance testing when faced with these applications.

We are thrilled to announce the release of Vera™ 2024.1! In this new version, we are introducing significant enhancements focused on audit history of domain role changes, streamlined Single Sign-On (SSO) login improvements, and improved Jira formatting support. We understand that maintaining stringent regulatory compliance while enhancing user experience are paramount concerns for any organization.

Measuring the success of quality assurance (QA) and software testing can be a complex task that requires going beyond surface metrics. It’s a nuanced process that needs an in-depth understanding of how every decision and action your team takes translates into tangible benefits for the product, the team, and, ultimately, the end-users. However, with so many data points available, identifying which metrics truly matter can feel like finding a needle in a haystack.

Ready to write functional test cases that testers can action on and that, combined, thoroughly cover the product? Let’s first define functional software testing. Broadly, functional software testing is defined as a type of black-box testing method that focuses on the functionality of a software product. Functional testing is designed to ensure a web or mobile software application meets its requirements and specifications by executing test cases from the user’s perspective.

Testing is not just writing test scripts and executing them. While not usually considered as an official step in the software testing life cycle, test case management is a crucial activity whose presence can be found in almost any stage of the testing process. The simple act of choosing which test case to execute is already test case management. Done right, test case management can make a real difference.