Systems | Development | Analytics | API | Testing

“Let’s get to the point” is something we’d all love to say in certain situations. The talkative restaurant server. The aunt who tells the same story over and over. The cooking blog that tells the author’s entire life story before the recipe. These people love to talk but they can’t read the room. They make the listener/reader work extra hard to understand the point, like finding a needle in a haystack.

Test Automation is a necessary precondition for high-quality modern development. Testing and test automation must be integrated into the software delivery processes to give the team the right level of feedback, at the right time, and to ensure high-quality software. One of the biggest challenges of building a test automation framework that works on a long-term, scalable basis, is that it requires fundamentally different conditions compared to a predominantly manual testing approach.

Jira is one of the most popular task management products available today, and for good reason: it's been around for a long time. The team at Atlassian is constantly working to improve the way users can utilize their software, but for a long time if you wanted to integrate with Jira as a developer, your options were generally limited to the Jira API.

Automated visual regression testing tools check for style issues and problems with the visual layer of an app or website. The benefit of these tools is that they can catch issues on the visual layer (the user interface of the website or app, which customers see) that may get missed by test scripts that only interact with the underlying code (the DOM).

For those not familiar with the acronym MTTR, ‘Mean Time to Recovery’, is the average time your organization takes to bounce back from a product or system failure. All DevOps stakeholders want this number to be low, as it is a good proxy for your organization’s ability to understand and improve its overall processes. Also, low MTTR scores are strongly correlated with customer satisfaction ratings! But we aren’t talking about DevOps metrics today.

The goal of DevOps is to streamline and automate your whole software delivery lifecycle. A successful DevOps testing plan for most businesses begins with implementing the agile best practice of Continuous Integration (CI), in which developers check code into a common repository numerous times per day. DevOps test engineers are team members that are in charge of testing in a DevOps setting.

We’ve added the functionality to add notes to your load test results. This functionality applies to Load Tests and JMeter Load Tests. It’s super simple to add/edit/remove notes for any of the test runs of the same test in order to caption various changes of your test runs. You can easily compare any test run with a baseline.