Below are some questions our customers have been asking us about the migration process from Twist to Gauge. We hope the information here will also assist your migration. If you don’t see a question you have here, then please contact us at email@example.com.
Is Gauge a new tool altogether, or it is just a new version of Twist?
Gauge is a completely new tool. It is not a rewrite of Twist. It has been built from the ground up to overcome the issues that stopped us from making Twist bigger and better. Unlike Twist, it supports multiple languages and IDEs. Gauge’s modular, plugin-supported architecture makes it more flexible and scalable than Twist.
Why do I need to migrate?
We have decided to sunset Twist and we will stop all development after 1 December 2015 when Twist will no longer be supported. We would like to see our customers move to our replacement offering, Gauge, which is open source and free. We invite you to migrate from Twist to Gauge.
What happens to our Twist tests?
We have a migration utility that will automatically migrate all your Twist tests to Gauge tests. This utility is available on the Twist update site. You will find instructions to run the utility here.
Do I have to upgrade my Twist version to migrate to Gauge?
We strongly recommend that you upgrade to Twist version 15.2 before you migrate, because we have optimised the migration process for this release.
Do I have to move to Gauge?
No, but we think Gauge’s more powerful and versatile functionality will serve you better in the long run. Twist will not be supported after 1 December 2015. We will stop all bug fixes or enhancements on Twist after the end of life date. We would love you migrate to Gauge before that so we can help you make a smooth transition. We understand that migration and learning a new tool is always complicated so we will support you during the transition.
Can I just continue using Twist?
Yes, but we do not recommend this. There will be no upgrades or support for Twist after 1 December 2015.
What is the plan for migration?
We have an automated utility. This is available on the Twist update site. We have extensive documentation about what needs to be be done before you use it, how to run the utility and what needs to be done post migration. We have provided instructions to help you get your Gauge tests up and running once the migration is done.
How long does the migration take?
We have run it on a project with 600 tests and it took about 10 minutes to complete so you should not have to plan for any major downtime. Nevertheless, we recommend performing the migration at a time when there is typically low (or preferably, no) use of Twist. There will be a some manual effort, for example, hooking up your Gauge suite to CI (this would mean installing Gauge on all agents) or configuring environments on Gauge. This is what you will need to plan for. We can help you with this.
What happens to missing features?
We have tried to strike a balance between achieving Twist parity and implementing features that fit our vision for Gauge. We have outlined the differences between the tools and our reasons in this document. Please have a look and email us at firstname.lastname@example.org if you have any questions.
Any changes in system requirements?
None. Gauge will run in the same environment set that Twist did. We do not have any specific system requirements.
When can I start migrating to Gauge?
You can start right away. We would suggest that you do it one project at a time, so the transition is more seamless.
Will you support Gauge?
Yes. Gauge is open source and we have a public forum where you can post questions. ThoughtWorks Studios has a dedicated development team for Gauge and we are in active development.
If you’re interested, we also have a commercial support offering. You can contact us at email@example.com to get more details about this.
I have a question about migration. Who do I contact?
Please send this to firstname.lastname@example.org.
Please sign in to leave a comment.