Open banking offers users a way to have easier access to their own bank account information, like via third-party applications. This is achieved by allowing third-party financial service providers access to the financial data of a bank's customers through the use of APIs, which enable secure communication between the different parties involved.

I'm happy to announce that visual regression & snapshot testing for our Playwright powered browser checks is now GA. If you have used these capabilities with your Playwright tests on your local machine or in your CI/CD pipeline, you can now use them 1:1 on Checkly.

Everyone needs observability. If you have a service that users rely on, you need to know if it’s working for your users. Heartbeat monitoring (Also called Synthetic Monitoring) should be a way to truly know how well our site is performing for users.

Step Function added support for testing individual states . Which lets you execute individual states with the following: And returns the following: With the TestState API, you can thoroughly test every state and achieve close to 100% coverage of a state machine. So, does this eliminate the need for Step Functions Local ? Can we do away with end-to-end tests as well? If not, where should this new API fit into your workflow, and how should you use it?

In 2.8, Rancher added a new field to the GlobalRoles resource (inheritedClusterRoles), which allows users to grant permissions on all downstream clusters. With the addition of this field, it is now possible to create a custom global role that grants user-configurable permissions on all current and future downstream clusters. This post will outline how to create this role using the new Rancher Kubernetes API, which is currently the best-supported method to use this new feature.

It is our pleasure to introduce the first officially supported API with Rancher v2.8: the Rancher Kubernetes API, or RK-API for short. Since the introduction of Rancher v2.0, a publicly supported API has been one of our most requested features. The Rancher APIs, which you may recognize as v3 (Norman) or v1 (Steve), have never been officially supported and can only be automated using our Terraform Provider.