What’s New in ThoughtWorks ALM Suite update?
ThoughtWorks Studios have recently updated their Adaptive ALM suite. We find out what’s new in Twist and Go 2.3.
ThoughtWorks Studios recently updated their Adaptive ALM suite, bringing their Twist Agile testing solution and the Go Agile release management tool, to version 2.3. We caught up with Vishy Nagarajarao and Chad Wathington, to find out what these updates mean for ThoughtWorks’ ALM users.
JAXenter: Twist 2.3 includes Selenium 2 support. What specific benefits does this bring, to existing Twist users?
Vishy Nagarajarao: Selenium 2.0 in a sense marks the consolidation of two drivers, Selenium and Webdriver. With Selenium 2.0, existing Twist users now have the ability to leverage Webdriver capabilities to test mobile web applications, and expand the scope of the application categories they can test with Twist. In addition, existing Selenium users who upgrade their test suites to Selenium 2.0 can now take advantage of Twist’s capabilities which promote reuse, support refactoring, improve recording etc. and significantly enhance productivity around test suite creation and maintenance
JAXenter: In your opinion, what are the most important new features of Go 2.3?
Vishy: We’ve made auditing and traceability in Go a lot more powerful. Go automatically compares the md5 checksum of your build artifacts to make sure they haven’t been tampered with. Go now allows you to view the full job history of each agent on your grid, letting you see when and where something was built. It also lets you see Go’s historical configuration at the time something was created or deployed.
JAXenter: Overall, what updates have been made to the suite in this release, in the area of Continuous Delivery?
Chad Wathington: In general we’re trying to make Continuous Delivery easier and more visible. Aside from the above changes to Go and Twist, we’ve also added a new stage duration visualization and some improvements to our deployment pipeline compare features, which allow you to see exactly what’s in the binaries you’re deploying. We want to make it simple for teams and organizations to see what’s happening in their release management processes.