From test suite to narrated demo

Making application demo videos used to be a long and painful process. We made it easy and enjoyable.

All of the applications made with the Suite Resources AI Application Manager platform contain an enormous amount of data. Every feature and every amendment to a feature is highly documented, and both a back and front end test suite is generated by default with every application build.

Enough to produce demo videos automatically.

Getting started Back to Video Director

How a video is made

1 · The app lists what it can do

Each application's tests define a list of named actions. Each action has settings, a description, a note on whether it can be filmed, and the checks it runs. Every build publishes that list alongside its recording.

2 · You put the video together

Pick actions from the list, put them in order, fill in their settings, and write one line of narration for each. Set how long to pause after each step, in seconds as they'll appear on screen, and choose the voice and language for the video.

3 · Video Director checks it

A step that uses an action the app no longer has, a line of narration with no step, or a step with no narration: each is caught here in the editor, where it's quick to fix.

4 · It renders on request

Press Render and the job goes to the build servers, which already have the browser and video tools it needs. The finished video comes back with narration and subtitles, plus a record of exactly which version of the app it shows.

When the app changes

Applications change all the time, and a video stays honest only if someone notices. Video Director compares each new build's list of actions with the list a video was made from, and looks for an action that:

  • has disappeared, so any video that uses it can't be rendered
  • does something different now, so it no longer proves what it did previously
  • takes different settings, so a video may be feeding it the wrong values
  • is new, so there may be something worth adding

It reports each change in a sentence you can act on: which app changed, in which build, which action, and which part of which video describes it. A banner at the top of every screen lists the apps that have changed, so you don't have to check them one at a time.

Where the videos are made

Making a video takes a browser, video encoding and plenty of memory. The server that hosts the applications doesn't have those to spare, so Video Director doesn't try to render there. Instead, it hands the render to the build servers, stores the result, and manages everything around it.

Built on AI Application Manager

Video Director gets its list of applications from AI Application Manager instead of keeping its own. It works with any app the platform builds, because each one comes with automated tests and a starter demo walkthrough already in place. Writing each app's actions is real work, done once. It pays off with the second video and the second language, not the first.

Want a demo of your application?

It starts with the application itself.

Getting started