Systems | Development | Analytics | API | Testing

TL;DR: Unity does give you the test reports but not in a format that is readable by CI/CD. We write a C# script that transforms the NUnit XML format to JUnit XML that Codemagic can read and use to present you with a report on how your tests went. A few weeks ago, I wrote an article about unit testing Unity projects in which I discussed why testing is so valuable for game devs and showed how to re-create a basic Pong game with some unit tests.

We are excited to announce our collaboration with LambdaTest, a leading cross-browser testing platform. You can now perform mobile app testing on LambdaTest’s real device cloud as part of your Codemagic CI/CD workflow.

It’s hard to imagine developing apps for iOS without a Mac computer. There is no sign of this changing any time soon, but there are still ways to build the app for iOS and release it to the App Store even if you don’t have a Mac. With Flutter and Codemagic, you can build and distribute iOS apps without buying a Mac computer yourself.

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.

Create and maintain dev, test and prod modern data stack deployments with Fivetran’s Terraform provider.

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.