

We are pleased to announce the release of Twist 2.3.1. Twist is now based on Eclipse 3.7 Indigo platform. We have also upgraded Twist to support to Selenium v2.5.
Please read the notes below for notes on the 2.3 major release.
We are pleased to announce the release of Twist 2.3 encompassing full support for the recently released, major update to the popular open source browser automation framework Selenium 2(version 2.5).
As well as adding selenium support with recording capabilities for the WebDriver API, we have continued to improve Twist's test authoring and maintenance features.
With this release you can now;
Quickly set up and create tests using the Selenium 2 driver.
Create maintainable tests using Twist's atomic recording for WebDriver.
Play back immediately via the Twist editor or within your continuous integration environment.
Improved configuration means you can quickly change the browser in which you wish to execute your tests.
Twist 2.3 also supports authoring and playback of Selenium tests for mobile browsers on Android or iOS devices.
Record a test on a desktop browser such as Firefox then quickly replay on your mobile device.
Further enhancements to our refactoring support allows you to selectively propagate concepts, inline existing concepts and search for existing concepts.
To upgrade your existing version of Twist go to http://www.thoughtworks-studios.com/twist-agile-test-automation/2.3.1/help/upgrading_twist.html and follow the instructions "Upgrading to Twist 2.3".
To download the Twist 2.3.1 installer follow the link below.
Cheers,
Twist team
Hi All,
I have done all required setting to record the flex object from an application as per http://code.google.com/p/flex-ui-selenium/. And now able to see the flex commands in selenium IDE window & separete names for flex objects .
When I started recording, flex objects doesn't get record where as feilds are showing name when mouse cursor is hover on flex elements. So anyone help me regards to it?
Selenium IDE window has "Flex Explorer" , is it useful for flex object recording?
Looking for guidance to record flex objects ..... plz lets know me solution for this.
--
Thanks,
Gaurav

We've received queries regarding testing Flash applications with Twist.
Twist uses a piece of software called a driver to run your tests. Simply put a driver is a piece of software which drives your tests. In the context of testing web applications, a driver typically embeds or opens up a browser and issues commands to the Application Under Test running inside the browser.
Twist ships with Selenium 0.9.2 and Sahi drivers for testing web applications.
To test Flash applications with Twist, the Flash Selenium driver must be used. Flash Selenium is available at http://code.google.com/p/flash-selenium/ There are instructions on the site that help you setup and going ( at a standalone driver level )
To use Flash Selenium with Twist , please follow the instructions at http://www.thoughtworks-studios.com/twist-agile-test-automation/2.0/help/how_do_i_use_other_selenium_versions_with_twist.html
The Flash Selenium driver is not supported by ThoughtWorks Studios.
NOTE: For testing Flex applications there is Flex Selenium - http://code.google.com/p/flex-ui-selenium/

Record - Analyze - Organize - the better way
Twist 2.2 continues to empower your team with cutting-edge functionality to get to market faster with robust, easy-to-maintain automated test suites. It eases test automation while reducing maintenance effort of large test suites with feature enhancements to test recording, refactoring analysis capabilities and test suite organization. Twist 2.2 provides support to record multiple steps at one go, intelligence for efficient refactoring, improved tagging and filtering, and a host of usability enhancements. With Twist 2.2 you can:

1. Change propagation across project :
In 2.0 Extracting Concepts would affect only the scenario in which the action was performed. In Twist 2.1 we have made both “Extract Concepts” and “Push to Implementation” propagate that change across the whole project, thus bringing it to the desired level of abstraction.
Parallel execution allows multiple twist scenarios to be executed simultaneously. It allows test suites to be executed faster. This feature requires the use of a driver that supports concurrent execution. Sahi and Selenium Grid currently support parallel execution.
Setting up a Sahi project has been simplified in Twist 2.1. The user no longer needs to deal with the nuances of twist.properties. Twist now identifies the platform automatically and populates the necessary derivable properties without the need for user input. Advanced setup requirements such as certificates and proxies would still need to be user configured.
The improved Groovy language support now lets you refactor from code back to scenarios. Twist now supports Groovy version 2.0.2 released on June 28th 2010.
In Twist 2.1, we can now add parameters in a context to a data table, thus extending the scope of data driven testing to even the setup and tear down in Twist.
The Twist team is pleased to announce the release of Twist 2.0. It has a host of new functionality that continues to deliver on the promise of making testing easy, effective, maintainable and sustainable.
Here is a list of features in this release:
Twist 2.0 continues to deliver on the promise of making testing easy, effective, maintainable and sustainable. With the new features in 2.0, you can ensure good test coverage and increase tester productivity.
In short Twist 2.0:
Here’s a list of features and a brief explanation about them.
1. Ensure test coverage with “Table driven scenarios”
Twist 2.0 introduces table driven scenarios, a new feature that lets you ensure test coverage through data driven testing. This allows for a deeper and more thorough testing of your product. This is the first step towards data driven testing capabilities in Twist -- many more to come.
2. Exploratory testing made easy with “Hybrid Execution”
Twist 2.0 has a new mode of executing a scenario called “Hybrid Execution”. This lets you be more productive when performing manual testing and makes tool support for exploratory testing, a reality.
With Hybrid execution, you can now have and execute scenarios that are part automated and part manual. This allows you to efficiently carry out manual & exploratory testing by taking advantage of the automated parts of a scenario. You eliminate the repetitive and cumbersome aspects of exploratory testing like launching the application, taking the application to a desired state and recording the results of your exploratory testing.
3. Lean, readable and maintainable test code in “Groovy”
You now have a choice of implementing the scenarios in a dynamic scripting language – Groovy, within Twist. This provides modern programming features like closures and DSL friendly syntax that makes your code easier to read and maintain. Additionally, using Groovy increases your productivity, as you have to write less code achieve the same functionality.
4. Build abstractions that are right for your domain with “Concepts”
A “concept” is a reusable sequence of steps in your business workflow. This allows you to gradually evolve from an imperative style of expressing test intent to a more declarative style, creating a more meaningful and maintainable expression of your test. This makes creation of additional tests quicker, more robust and removes UI level noise. Concepts are abstractions built at the business layer.
The earlier implementation of “Extract concept” which is now called “Push to Implementation” allows you to build abstractions in the underlying code.
Both Extract Concept and Push to Implementation allow you to easily build the level of abstraction that is right for your domain.
5. Reliable and flexible web-application testing with “Sahi” ©
Twist 2.0 now also supports Sahi for web-application testing. Sahi makes your web testing more reliable and consistent. Sahi has an object oriented and intuitive API that makes writing test scripts simple and easy. It also makes recording possible on Internet Explorer. The Sahi “Accessor Spy” makes it convenient to locate and interact with your web application.
6. Test Eclipse/SWT applications using Twist + SWTBot
With SWTBot, Twist now integrates with the #1 testing driver for Eclipse/SWT applications. Twist, since it's an SWT application itself, uses Twist+SWTBot for its own testing.

The wait is over! Twist 2.0, a major upgrade to Twist, our testing automation solution, will be available for download on March 31st, 2010.
The list of features included in this release includes:
NOTE: Twist 2.0 will be available for download on March 31st, 2010 here.

While test automation unquestionably optimizes the testing process, certain cases like testing visual references and ad-hoc testing are best done manually. Using separate tools to create and manage your automated and manual tests can lead to chaotic and error-prone test management.
Twist 1.1 extends Twist's ease of creating evolving automated tests to manual testing, thus optimizing your testing process. With 1.1, Twist is now your complete testing platform to create, execute and maintain all your manual and automated test scenarios in one central space. In addition 1.1 allows you to debug failing automated scenarios using manual execution and record manual test results.
A quick snapshot of the enhancements in Twist 1.1:
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 |