Test versions

A test version is a copy of your application, to add a feature or fix a problem without touching the live app. It has its own address, its own test data and its own conversation with the assistant. Once you are happy with the result, “Publish” puts its changes into the live app.

On this page

Create a test version

In “Applications”, click “Create a test version” on the application's card. The same button sits at the top of the live app's conversation, beside its name.

In “Title”, write in a few words what must change, for example “Add the floor of each room”, then click “Create the test version”. Its conversation opens at once. Its address is the application's, followed by two hyphens and the start of the title. Within a minute, the test version is “Live” at that address.

A test version starts from the live app: a change saved in the application's conversation but not deployed yet will not be in it. The window says so; deploy the change first to have it in the test version.

Its data and its test account

A test version starts from test data, not from your live app's: what you enter there stays in the test version. To get in, click “Sign in with Kedalia” on its sign-in page: each member of your organisation gets an administrator account in their own name the first time. The “Sign-in details” button, at the top of its conversation and on its row in “Applications”, also gives an administrator account and its password: for the test version of an older application, which does not create those accounts, or for someone outside the organisation.

Make the change

A test version's conversation goes like any other: describe the change, answer the assistant's questions, click “Request the plan”, read it, then click “Execute the plan”.

When the assistant is done, the change is installed on the test version by itself: the conversation shows “Changes delivered”, then “The tests passed.”. For a small addition, allow a few minutes in all. Then open the test version's address to try the result: the live app has not changed.

Publish

The “Publish” button is at the top of the test version's conversation. As long as the test version has no change, it stays greyed out; hovering it shows “Nothing to publish: this test version has no change yet”.

Click “Publish”. Kedalia asks for confirmation: “Publish to the live app?”. The changes join the live app, which updates within one to two minutes; meanwhile, the site stays up on the previous version. The window stays open on “Publishing…” until the publication is done. The test version and its test data are then removed.

The conversation stays on screen, read-only. At the top, “The live app” follows its update: “Tests”, “Deployment”, then “Live” with its address. In “Applications”, the test version's row stays, with “Published into” followed by the application's name, until you remove it: click its bin, then “Remove”. Its “AI assistant” button opens the conversation again, read-only.

“Publish” is also on a test version's row in “Applications”, with the same window.

If the live app changed since, Kedalia first adds its changes to the test version. When both changed the same files, nothing is published: the conversation says so, and the assistant combines the two versions. Check the result in the “Preview”, then click “Publish” again.

Reopen a published test version

To ask for more changes in the same conversation, click “Reopen the conversation” at its top, or “Reopen” on its row in “Applications”. The test version is recreated at the same address, from the live app, with fresh test data; it counts again in your number of applications and test versions. Once it is ready, the conversation carries on with the assistant, where it had stopped.

Delete a test version

To give up on a test version, click the bin on its row in “Applications”. Kedalia asks “Delete this test version?”: it will be deleted, along with its address and its test data, and the live app is untouched. This cannot be undone: type its name, shown in the window, then click “Delete”.

Several at once

An application can have several test versions at the same time, each with its own address and conversation: one per change, published or deleted independently of the others. How many depends on your tier, and they count together with your applications. Once the limit is reached, Kedalia refuses the next one: “Your tier allows no more applications or test versions. Delete one before creating another.”