Systems | Development | Analytics | API | Testing

In an ideal world, you want to have precisely the capacity to manage the requests of your users, from peak periods to off-peak hours. If you need three servers to attend to all the requests at peak periods and just one server at off-peak hours, running three servers all the time is going to drive up expenses, and running just one server all the time is going to mean that during peak periods, your systems will be overwhelmed and some clients will be denied service.

One morning, you realize you have a great idea for an API. You discuss it with your team, then start building out the business case and technical requirements. Where do you go from there? You could write out the business requirements for the API and then code it. Or you could describe your API in a specification language, like OpenAPI, and use that definition to improve your team's understanding of the API and do some early testing. But are either of these the best solution?

Automating your test suite helps get your code to production faster. In this tutorial, you'll learn how to write unit tests for Django and run them with GitHub Actions.

With the introduction of new application platforms like Kubernetes, oftentimes the DevOps tooling around it needs to evolve. Cloud Native technology is powerful but complex. This 5 minute demo video shows how Speedscale provides production simulation capabilities so you can check for resiliency, quality and scalability in your Kubernetes clusters. You can record data and traffic in production and replay sanitized traffic on the fly against a new cluster.

New software has to be thoroughly tested before it can be released to the public. As such, a software test plan is essential. The software development process is not complete without a comprehensive test plan. It details the measures you'll take to guarantee that your product or feature will function as intended and won't fail at the worst possible time for your customers.

The true purpose of Software Testing is to check that a product satisfies its standards or, more generally, to report on any discoveries that diminish the consumer experience. The function of a error in these more ambitious corporate objectives is more complex. Before you can release your application, you must demonstrate that it functions well and is free of bugs In the language of testing specialists, "error" often plays the role of the enemy.

TL;DR: It’s critical to deliver the latest builds of your Unity game to testers and stakeholders. You can automate this process by setting up a Codemagic CI/CD pipeline and either using public Codemagic dashboards to access build artifacts or setting up notifications in Discord with links to builds and release notes. Let’s see how we can use automation tools to share our game builds with QA testers and stakeholders!