Systems | Development | Analytics | API | Testing

SmartBear

Accelerate Your Web Tests With Parallel Execution

It’s September. Students are back to school, whether that is in person or remote. Here in the States, we just celebrated the unofficial end of Summer with Labor Day. Things are likely picking up where you are, which makes it the perfect time to focus on test execution to put yourself ahead. Quality at the expense of speed, or speed at the expense of quality, is likely a challenge you have faced in your development journey.

Enterprise Capabilities in Collaborator to Tackle the New Normal

As Collaborator’s product manager, I speak with a lot of Enterprise customers throughout the year about their peer review processes, and where they see changes coming during this new age of distributed workforce. I noticed two common challenges that I’d like to explore further in this blog post through the lens of Collaborator.

Test Management 101: Integrations make continuous integration go 'round

Launching test automation tools in real time is an essential requirement for testers. That way all your results populate in a one-stop shop for continuous integration. Zephyr Enterprise allows you to integrate with Jira, Confluence, Crowd, and LDAP, continuous integration tools like Jenkins and Bamboo, and automation tools like Selenium and QTP/UFT. These diverse integrations enable you to realize the full benefits of these integrated, best-of-breed systems.

API Load Testing Mistake #5: Not Factoring in External API Calls - @SmartBear Talks

Nowadays, lots of modern API-based applications make calls out to third-party APIs. These APIs can belong to your organization, or they can be located on a partner, customer, etc. side. Today, we will analyze the specifics of calling these APIs during API load testing. Robert Schneider, a software testing consultant from WiseClouds, will help us avoid the mistakes when working with external API calls.

API Load Testing Mistake #3: Failing to Explore Multiple Load Generation Scenarios -@SmartBear Talks

Creating an API load test is only one piece of the huge load testing world. Once your test is ready, you need to integrate it into the business process, simulate different load generation scenarios, and analyze the results. Today, we will continue investigating API Load Testing mistakes you can easily avoid. Robert Schneider, a software testing consultant from WiseClouds, will share exclusive insight into load generation scenarios.

API Load Testing Mistake #4: Simulating GUI Security Integrations via API - @SmartBear Talks

Lots of applications nowadays have robust and complex front-end development - user experience becomes so important! That's why, we need to understand how these front-end features and elements work under load. In this interview, we will talk with Damion White, software testing consultant from WiseClouds, and discuss the issues you can face when creating API load tests for such scenarios and how to avoid them.

API Load Testing Mistake #2: Not Calibrating Virtual Users to Real Users - @SmartBear Talks

A huge part of your strategic plan for load tests built into your app development business processes is understanding and ensuring that the user profiles or the actions that your simulated users take in any testing environment accurately depict what happens in a real-world use case. That's why you need to be very careful with setting up virtual users in your load tests. We will investigate possible issues with Damion White, software testing consultant from WiseClouds, in this video.

API Load Testing Mistake #1: Separating Load Tests from Business Process - @SmartBear Talks

API performance testing becomes highly-demanded in all companies. It's very important to make sure how each single API works, as well as how they work under a different load. Many companies are trying to do API load testing by using the same approaches they use to test single APIs. In this video, we will talk with a world-known API expert, Robert Schneider, about the importance of including API load testing scenarios into a business process.