Turbo

What do you like best?

Turbo has been an effective component of our testing programs for the last 8 years for the Autodesk Inventor product. It enables the QA team to run multiple versions of Inventor concurrently on the same computer for testing purposes & regression analysis. There is zero install/uninstall requirements so all concerns of potential conflicts from side by side use or other software components are mitigated.

We have been able to automate the Turbo build process for a 20yr old, 12GB desktop application (Inventor) so that a new build can be created in about an hour & results in a single, self-contained 4Gb executable. Different to other similar technologies, Turbo allows us to virtualize/containerize only the application required without the need to virtualize the entire operating system. After first run there is no noticeable performance impact from running the Turbo build. Turbo can access/leverage all local resources (RAM, disk, CPU, GPU, USB).

The exact same Turbo build can be either be run locally as an exe on your computer, or it can be streamed in either graphics or full application mode using Turbo.net running on the Azure cloud. When streaming local client tools enable full access to local resources for both windows & mac OS. Extremely flexible - something we rely on throughout our Inventor development test processes.

What do you dislike?

The initial build process can be quite complex but once solved it is easily automated through Turbo scripting. The excellent team at Turbo will likely just do this for your application as part of their consulting services.

Recommendations to others considering the product:

Understand your product manual build/install processes & then automate the Turbo build using their scripting - this takes a bit of time upfront but the paybacks are immediate.

What problems are you solving with the product? What benefits have you realized?

Hundred's of our customers leverage Inventor Turbo builds to pre-release test Inventor as part of our Alpha/Beta activities. This enables them to test with confidence so that they can compare multiple builds concurrently without any concerns of their local production computers being polluted with pre-release code. Some Inventor customers also use Turbo builds for their final production use as opposed to deploying the normally installed software product. The use of Turbo ass part of our pre-release test activities enables our customers to test the new versions in their own production environment to know that their can upgrade with confidence. Turbo enables us to release Inventor with confidence knowing that it has been properly tested by our customers