Systems | Development | Analytics | API | Testing

Test automation is here to stay. That’s because good test automation reduces manual effort through repeatable, stable processes, increases ROI on testing, accelerates testing and feedback, and in the long run reduces business expenses.

In recent years, there’s been a shift towards broader adoption of JavaScript test automation frameworks. Today our customers are using Cypress, TestCafe, Puppeteer, and most recently, Playwright. Plus, they are often using these alongside existing Selenium and mobile test automation frameworks. The options for testing have increased, and depending on your unique testing needs, you may be adopting one or many solutions in your organization.

In order to learn how to test your APIs, especially how to load test your APIs, let’s first find out some essential info on APIs and RESTful APIs.

Performance Testing coverage needs to be defined from the application under tests functional requirements and this does not change regardless of whether you are following an Agile or a more Planned approach.

Getting quality bugs is only half the QA battle—you need issue reports showing actual testing session insights that could negatively impact your users. And if you have skilled manual testers to help you find these bugs, the next problem becomes…how do you fix them? For that, you need contextual information about the steps and environmental conditions leading up to the bug.

Standard Deviation is an important metric in performance testing analysis and informs us how stable the application under test is. In other words, it tells us if the requests that occur during the test are consistent or not. Standard Deviation measures how the response times are spread out around the average response time (mean). A small standard deviation means that the response time of all the requests are close to each other.