Test features end-to-end before merging
Test one or more Pull Requests in Kubernetes using lightweight Sandboxes
/ how do sandboxes work?

Sandboxes are test environments that consist of one or more "under test" versions of microservices. These microservices have their dependencies fulfilled by a stable, baseline environment that runs stable versions of other services. To separate test requests for Sandboxes, traffic labeling and routing is utilized. This allows for the creation of multiple environments within a Kubernetes cluster, each with its own independent flow of traffic through various microservices.

/ use cases

Integration Testing

Run integration tests for any service in a Kubernetes cluster with the latest versions of dependent services. Fully realize Continuous Delivery.

Feature Testing

Enable developers to collaborate on a change to one or more microservices to test functionality before merging back into master.

End-to-End Testing

Test the impact of a change to every service in your stack on end-to-end flows. See what your end users see.

Performance Testing

Discover performance and other non-functional regressions before merging.

Preview Environments

Share early previews of new features with product managers, quality engineers and user experience teams.

API Testing

Automate API testing for your microservices using Sandbox URLs with tools like Postman, RestAssured, JMeter and others. Sandbox URLs support http and gRPC APIs.

/ sandbox lifecycle

Create Sandbox

Create a Sandbox by "forking" one or more baseline workloads. Customize "forked" versions with specific docker images and environment variables.

/ features
Centralized management portal

Install the Signadot Operator in your Kubernetes cluster on any cloud. Workloads deployed for Sandbox testing run securely in your own infrastructure.

YAML specifications

No need to maintain separate Kubernetes manifests for baseline and Sandbox deployments. Specify what stateful resources should be included in Sandboxes via simple YAML specification.

Sandbox Resources

Isolate Sandbox environments when there are stateful components involved like databases and message queues. Resource Plugins are installed directly into the Kubernetes cluster using a Kubernetes CustomResource and are invoked during the creation and deletion of Sandboxes that reference them.

Istio / Distributed Tracing

Bring your own Service Mesh, and distributed tracing to enable dynamic routing of requests to specific versions of Services. Use integrations, or our built-in sidecar container, to enable End-to-End testing, feature testing, Preview URLs, and more.

Bring your own CI

Automate the creation of Sandboxes using the Signadot CLI in your CI pipelines. Create Sandboxes for every Pull Request, branch or commit. Refer to specific documentation for GitHub Actions, Jenkins and BitBucket for more details.

Sandbox Analytics

Track the usage of sandboxes to assess adoption by various teams and projects as well as change in usage over time.

/ take signadot for a whirl
Learn more about how to scale pre-merge testing with microservices