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, shared by your whole organisation: every member reads and writes the same messages there. Each change the assistant makes is installed on it by itself. 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 in the live app's conversation: at the top, beside its name, until its first publication, then in the red banner once it has been published (on a phone, tap the banner to unfold it).

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.

In “Applications”, it has its own row under the application's card: its name, its state, its address, who created it and its last activity. The row carries “Open” right of its state once the test version is up, then “Publish” (or “Close again”, “Reopen”), “Edit”, and a “…” menu with “Rename”, “Retry the creation” after a failure, and “Delete…”, or “Remove” for a published test version. When a test version's tests failed, its row adds “Fix”: the assistant reads their report and fixes the test version, without you leaving the page.

A test version starts from the app as the “Preview” of its conversation shows it: a change saved but not published yet is already in it, and the window says so. The test version keeps it even if the application drops it later with “Abandon the changes”: then ask the test version's assistant to take it out too. For an application whose code stays on GitHub, a test version starts from what is on GitHub: a change not published yet will not be in it. The window says so; publish the change first to have it in the test version. Its tests run on GitHub at each send of the assistant: “Publish” then offers to publish at once or after them (see “Publish” below), and a Kanban card waits until they have passed (see The Kanban).

Rename a test version

“Rename”, in the “…” menu of its row in “Applications”, changes a test version's title. The same “Rename” pencil sits on its Kanban card and at the top of its conversation, at the end of the line “Test version of …”; the test version's “Settings” tab offers “Change the title”. Once the test version is ready, its title also gives its address: the “Rename the test version” window shows the new one under the field, and the old one stops answering. Its conversation and its data stay; it installs itself again at its new address, for the time of a preparation. If another test version of the application already has that name, nothing changes, neither the title nor the address. While the assistant works on a ready test version, its address cannot change: the pencil is greyed until its work is done. A published test version keeps its pencil: only its title changes, the one it takes back if you reopen it.

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. The same goes for its settings: another service's keys saved in your live app do not carry over, so enter test keys there.

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 “Updating the test version…”, which turns into “Test version up to date” once installed, and “The tests passed.”. If the tests or the start fail, it turns into “Update sent at” followed by the time. 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.

When the live app changes

After each change of the live app, through “Publish” in its conversation or the publication of another test version, its test versions update themselves: each one receives those changes while keeping its own, then is installed again. Its conversation says so: “Test version updated with the live app.” They go one at a time: the next one waits until the previous one is installed, and follows within five minutes. Only the test versions used in the last 14 days are updated; an older one waits until you write in its conversation again.

A test version waits while the assistant works on it, while it is being published, tested or installed, while a change in it waits for “Update the test version”, or while its “Preview” is open. It is updated in the minutes that follow.

If the live app changed the same files as the test version, nothing is changed in the test version, and its conversation says so: “The live app changed the same files.” Click “Combine both versions”, at the bottom of the conversation: the assistant combines both versions, then the test version updates itself. Without that click, “Publish” will do the same combining.

When the live app and the test version have both added database changes, the test version is left as it is: “The live app added database changes: this test version will receive them when it is published.” “Publish” takes care of it.

Publish

The “Publish” button is in the bar at the top of the page, after the test version's name. When it is greyed out, hover over it to read the reason; on a phone, it is written under it: “Nothing to publish: this test version has no change yet”, or the live app being updated, for example. It unlocks by itself as soon as the reason goes away.

While the test version's tests are running, the bar says “Up” and “Tests running”: the test version is up, on the version its tests check. “Publish” stays clickable and opens “The tests are still running” with two choices. “Publish now” sends a version the automated tests have not validated yet. “Publish after the tests” schedules the publication: the button becomes “Published after the tests”, and the publication starts by itself as soon as the tests pass; if they fail, nothing goes out. If a new change is sent meanwhile, it waits for that change's tests, and after two hours without a result, it stops. To cancel it, click “Published after the tests”, then “Cancel the publication”. For an app whose code stays on GitHub, a plain “Publish” waits the same way when the tests have not validated the latest version yet, for instance after the update with the live app: the button becomes “Published after the tests”, and the publication goes out by itself as soon as they have passed.

Click “Publish”. Kedalia asks for confirmation: “Publish to the live app?”. The window closes at once, the “Preview” too, which does not reopen until publishing ends, and the publication is followed in the conversation, in a “Publishing into” frame followed by the application's name, in four steps: “Combining with” the application, “Tests”, “Start-up”, then “Live”. Allow about four minutes; meanwhile, the site stays up on the previous version, and you can leave the page: publishing carries on. Once combining is done, the test version and its test data are removed, and the conversation stays on screen, read-only. On a phone, while you read the bottom of the conversation, the frame comes down to one line stuck at the top of the screen, which follows publishing to its end; tap it to go back to the frame.

At the end, the frame says “Your changes have been live since” followed by the time, with “Open the app”. If the tests or the start-up fail, it says “The tests failed: nothing changed live.” or “Start-up failed: nothing changed live.”. The site still runs the previous version, but the changes are already in the application: its next update will carry them. “See the error” shows the end of the tests' log, and “Fix in” followed by the application's name opens its conversation, where “Make the tests pass” hands the fix to the assistant. The application's state then says “Live · latest update failed”. When it is the start-up that failed, Kedalia first retries it by itself, twice at most: the frame says “Attempt” followed by the number, and going live can take a few minutes longer. If it fails again, the frame shows “Retry the start-up”, which puts the same version live again, changing nothing, in place of “Fix in”; if it fails again, ask the assistant or write to support.

In “Applications”, the test version's row follows the publication in one line. Once the app is live, it stays, with “Published into” followed by the application's name, until you remove it: choose “Remove” in its “…” menu, then confirm. Its “Read back” button opens the conversation again, read-only.

“Publish” is also on a test version's row in “Applications”, with the same window; it is greyed out there for the same reasons, which a tooltip gives when you hover the button. Once publishing has started, a message says so: “Publishing started: tests, then going live, about 4 min.”

If the live app changed since, Kedalia first adds its changes to the test version. When both changed the same files, nothing is published: publishing pauses on its first step, “Paused: combining both versions”, and the assistant combines the two versions in the conversation. When it is done, the frame shows “Ready to resume”: click “Resume publishing”. If the live app changes during the publication itself, Kedalia starts again by itself, up to three times; if the publication does not go through, the frame says so and offers “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 app as the “Preview” shows it, 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. Kedalia first asks “Reopen this test version?” and recalls these consequences. A “Conversation reopened” line in the conversation separates what is already live from what comes next: “Publish” waits for a new change.

As long as nothing has been done in it since, “Close again” replaces “Publish”, at the top of the conversation as on its row in “Applications”. The test version goes back to published, without changing anything in the live app, and no longer counts in your number of applications and test versions; a “Closed again without any change” line ends its conversation, and you can reopen it again. Kedalia first asks “Close this test version again?”. If the test version could not be recreated, “Close again” stays on its row, and “Retry the creation” is in its “…” menu. For an application whose code stays on GitHub, “Close again” is not offered.

Delete a test version

To give up on a test version, open the “…” menu of its row in “Applications”, then click “Delete…”. Only the person who created it and the organisation's administrators can delete it: for others, the entry is greyed out, with “Reserved for its author and the administrators”. 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: once the assistant has built something in it, type its name, shown in the window, then click “Delete”. As long as it has built nothing, “Delete” is enough, except for a test version that failed.

Requiring test versions

An administrator of your organisation can decide that the live application is changed through test versions only: in the application's “Settings” tab, “Changes” section, they switch on “Change only through a test version”. The setting applies to everyone, administrators included. The live application's conversation is then closed: it shows “Changes to … go through a test version.” and the “Create a test version” button. On the Applications page, “Edit” and “Make the tests pass” disappear from its line. Every change is prepared in a test version, then published with “Publish”.

Work the assistant is already doing in the live application's conversation goes on to the end, and its change is saved: the next test version starts from it. Only its resumption after Kedalia restarts is refused. An automatic repair of failed tests is no longer made in the live application's conversation: its line says the app is changed through test versions only. An application taken over from GitHub cannot be set this way while the assistant is working on it, or while it has changes saved and not published yet: wait for the work to end, then publish or discard them.

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.” If none of them is yours, Kedalia sends you to an administrator of your organisation, who can delete one.

A paused test version does not count in that limit: see “Paused”, below.

In “Applications”, beyond three test versions, the quiet ones, up or published, fold behind a button such as “2 more test versions”; the failed ones and those in progress always show.

Paused

On the Kanban, a test version whose card is set aside in one of your team's columns is paused (see The Kanban). It stops and no longer counts in your tier; its test data and its conversation are kept. It shows “Paused” on its card and on its line in “Applications”.

Its address shows “This test version is paused”, with a link to its conversation. Its conversation can be read but takes no message: in place of the message box, “Test version paused: it no longer counts in your tier.” Its preview still opens, and “Publish” is still possible.

“Relaunch”, on its card, in its conversation or on its line in “Applications”, puts it back online as it was, with its data; allow a few minutes. If your tier is full, the relaunch is refused and it stays paused. If its card stays set aside, it pauses again after 12 hours with no activity: no message, no preview opened, no sign-in to the test version.