> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to test changes to an app version without affecting people using it day to day
- URL: https://blog.jestor.com/test-app-versions-no-impact-users/
- Published: 2026-07-12T00:32:38.000Z
- Updated: 2026-07-12T00:32:38.000Z
- Author: Bruno Bannach

The fear of causing instability ends up stalling a process's evolution: a simple layout change, made mid-shift, and the team sees the app "broken" in the middle of a task. Jestor solves this by isolating the version being tested from the version end users see.

## What is isolation between staging and production, and why does it exist?

Environment isolation is the separation between the version locked as stable (**production**), seen by everyone, and the version being edited (**staging**), visible only to the builder — changes in staging don't leak into production.

| Example                       | What happens                          | Uptime for the end user              |
| ----------------------------- | ------------------------------------- | ------------------------------------ |
| **Locked version (e.g., V4)** | What every regular user sees and uses | Preserved, no interruption           |
| **Test version (e.g., V9)**   | Visible only to the builder           | Not applicable, isolated environment |

## How to test a new version without affecting users in Jestor

- **Automatic publishing by default:** the app publishes the latest version, unless manually locked.
- **Manually locked version:** the builder pins a specific version (e.g., V4) as stable.
- **New version on every refresh or save:** every saved change generates a numbered version.
- **Switching the published version:** once the adjustments are validated, the builder publishes the new version to everyone at once.

**How to configure it in Jestor:** lock the current version as stable in build mode and keep testing — the switch only affects users once you decide to publish.

## Why choose Jestor for this kind of testing?

The key differentiator is that the **regular user never notices** what's being tested, even while the builder is actively editing a newer version — reducing the rework of redoing changes that didn't pan out.

## Frequently Asked Questions

**Can a regular user see the changes being tested?** No, while the stable version is locked, users keep seeing only that version.

**Do I need to save manually to generate a new version?** Not necessarily — the system saves automatically, but you can also force it via the build button or a refresh.

**How do I go back to an earlier version even after several changes?** All versions remain available to review and restore at any time.

## Reference video

Check out other practical tutorials on the [Jestor YouTube channel](https://www.youtube.com/@jestorbr?ref=blog.jestor.com).

## Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all with no code and with AI support. Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.