Gradient Lights

Zero-compromise Azure testing

Say 👋 to brittle tests, sandbox provisioning & grueling CI cycles by running Azure locally

Join Waitlist

Test Azure apps locally

Use LocalSandbox as a drop-in replacement for Azure in testing & development environments.

> az servicebus queue create --name my-queue \
     --endpoint http://localhost:7329

"my-queue"

> █

Cut dev time by running locally

Cut dev time by running locally

Testing against cloud sandbox environments is an operational nightmare.

LocalSandbox removes the burden of flaky tests, janky sandbox provisioning setups and long CI runs by running cloud services locally. Install with docker or npm1 and be ready in seconds.

Still want synchronization? Check out Template and Sync .

Diagram showcasing how moving from using cloud sandboxes to local sandbox helps the flow of requests occur more smoothly; dashed dimmed gray lines are presented, which flow in a choppy way to logos of cloud providers; green lines are also presented, flowing instead smoothly to a logo of LocalSandbox.

Never write a mock again

Never write a mock again

Mocks abound despite only instilling partial confidence in critical paths.

LocalSandbox provides rigorously tested2 stateful fake cloud vendors that run locally, so you can replace mocks and reap the benefits of end-to-end testing at zero-cost.

Plus, use Scenario to test non-IaC flows such as creating Microsoft accounts or testing MFA.

mock-based state-based
containerClientMock.Verify(client => client.UploadBlob("profile.png"), Times.Once);Assert.Contains( containerClient.GetBlobs(), blob => blob.Name == "profile.png"); Assert.Contains( containerClient.GetBlobs(), blob => blob.Name == "profile.png");
Diagram showcasing how LocalSandbox takes a basic sample test from needing cumbersome mocks to being much more intuitive, instead requiring assertions on the "scenario" or state of the world; two blocks of code are showcased, one above labelled "mock-based", and one below labelled "state-based", where the top one makes use of jest's mocks features, and the bottom one makes use of LocalSandbox's "scenarios" feature by contrast; a bright green arrow is depicted, crossing the gap between the two, and suggesting a move from mock-based tests to state-based tests.

Cover outages & delays no sweat

Cover outages & delays no sweat

Most cloud integration code is highly susceptible to errors from outages and delays in cloud providers. For sensitive domains, this is unacceptable.

To solve this we built Chaos , a tightly knit toolset for chaos engineering that makes testing service degradations a cinch.

localSandbox.chaos.simulateDelay()localSandbox.chaos.simulateDelay()
Diagram showcasing the "simulate delay" feature of LocalSandbox, allowing the developer to call a function so that every request made has a certain amount of delay before LocalSandbox responds; at the top is a line of code which calls this simulate delay function; an arrow is depicted from that line of code to a subdiagram with a computer, a stopwatch, and LocalSandbox's logo; an animation proceeds in sequence: first, a request is made from the computer to LocalSandox; second, the stopwatch makes a full rotation; finally, a request is made from LocalSandbox back to the computer.
Book a Demo

1 LocalSandbox is available both as a standalone executable (via Docker or NPM) or to be run programmatically in Node.JS - see the docs for more details
2 All integrations we support are regularly parity tested against the real APIs - check out our status page which gives live updates if integrations ever fail

LocalSandbox's logo
LocalSandbox
Product Documentation Pricing Preview Contact Sales
Company Contact Careers Blog Security
© LocalSandbox 2024