Postman is a great tool for API testing during development. It’s GUI is simple to learn and ubiquitous. However, manually writing test cases for local development gets tedious fast if you have a lot of endpoints. Meticulously entering every detail for every use case takes forever. Also, if you get one HTTP Header or parameter wrong, it can take hours to diagnose. And even when it’s done, the API tests are almost immediately out of date because the API contract changes.

On Nov 13, 2019 Github made it’s CI/CD solution GitHub Actions generally available to the world. Since then tens of thousands of shared workflows have been published. It is now the default for most Github projects given how easy it is to integrate with an existing repo. Projects of all sizes have adopted it from our homegrown Terraform module to the Docker Cli. This is why at Speedscale we’ve published a template for how to use Speedscale in conjunction with GitHub Actions.

Speedscale is excited to join the AWS Partner Network (APN), the global community of partners who leverage Amazon Web Services (AWS) to build solutions and services for customers. AWS Partners are uniquely positioned to help businesses take full advantage of all that AWS has to offer and accelerate the journey to the cloud. As part of this achievement, Speedscale has completed the AWS Foundational Technical Review (FTR).

Will your software perform well during peak hours? Can it handle the load during sales periods? Is your infrastructure valid if you double your sales by the end of the year? These are just some of the questions that scalability testing can help you answer. Scalability testing evaluates the activity level of your application by upscaling and downscaling the number of users.

Speedscale is proud to announce its Centralized Log Collection capability. When diagnosing the source of problems in your API, more information is better. For most engineers, the diagnosis process usually starts with the application logs. Unfortunately, logs are usually either discarded or stored in Observability systems that engineers don’t have direct access to. Compounding this issue is that the log information is typically not correlated to what calls were made against the API.

One of the most important phrases of DevOps practices is “Test early, test often.” It’s crucial to perform functional testing early with unit tests and integration tests. But it’s equally important to perform non-functional testing. That means you should have performance tests. As markets become more saturated with each passing day, you no longer have the luxury to postpone performance testing until all features are developed.

gRPC is a remote procedure call framework that has been widely adopted among cloud native applications. It is an attractive choice for engineers needing more capabilities than what REST APIs provide. However, observability and testing tools for gRPC are few and far between. Because of this, triaging or understanding application behavior is potentially time-consuming and overly burdensome.

Modern-day applications aim to cover a wide range of users’ needs in a flexible and scalable manner. The software development landscape is moving at a fast pace, and the competition is so fierce that a business simply can’t afford to offer a low-quality product. Thorough testing of both functional and non-functional aspects of a software application has become an essential step in the software development process. It ensures that users get the best version of your product.