Systems | Development | Analytics | API | Testing

In today's competitive market, you can’t afford to risk poor product quality and software failures. Unfortunately, many companies still use outdated methods to manage their tests like Excel, Word, Google Sheets, or other spreadsheet tools. Without a proper test management app, your quality suffers and testing remains archaic and at the most basic level, tracking and logging tests.

With the rise of virtual production, creative pipelines are becoming increasingly complex, and dispersed. Team members around the globe need to collaborate remotely. This can create security vulnerabilities, which can range from misconfigured SSL settings to expiring certificates. To help studios protect what matters most, the Trusted Partner Network (TPN) created an evaluation process to standardize fundamental security protocols, across the industry.

An automated testing strategy answers the who, what, when, why, and how of software test automation. While automation can be used for many kinds of software testing, in this post, we’re going to focus on the steps you should take when developing a strategy for functional UI testing (also known as end-to-end testing). End-to-end testing simulates real user conditions to test the functionality of an application from the front-end user interface.

Over the past few months, I’ve been redesigning and writing StatusCake’s SSL monitoring feature from Node to Go. This blog post describes one of the more subtle challenges we came across to help you master it if you find yourself with it too! Writing a Go client that fetches an SSL certificate isn’t a new problem. A common approach is to use a http.Client. This limits you to just certificates served over HTTPS, when technically anything running TLS can have a certificate.