Post posted September 28, 2008 by Chad Wathington, last edited February 9, 2012
2219 Views, 9 Comments
Topic:
What other drivers would you like for Twist?
Body:
Currently, Twist “drives” other functional testing tools. It supports Selenium for web testing and Frankenstein for Swing testing. What drivers would people like to see in future releases?
Hi Rafael. For the commercial release, we’ll make it clear how you can use Twist’s scenario runner with Maven and Rake from the command line. In the future, since we’re looking to add Ruby support, out of the box Rake support will be next. I’ll add Maven to the backlog—if we see a fair amount of demand, we’ll make it happen sooner rather than later.
Using Twist as a replacement UI for acceptance tests against business logic (typically done in Fit/Fitnesse) would be the first thing that occurs to me. In fact, when I first heard of Twist, I assumed that this was what it was, and not a driver for UI based functional tests.
I agree with the propostiions here.
Maven is a top selection criteria to us ;o) as it is our build platform
And Fit/Fitnesse import-export would be great, allowing us to combine both Twist with existing test scenarios.
Emmanuel
Comment
- Maven (for Java)
- Rake tasks (for Ruby)
They should be able to drive Twist “out of the box”...
Hi Rafael. For the commercial release, we’ll make it clear how you can use Twist’s scenario runner with Maven and Rake from the command line. In the future, since we’re looking to add Ruby support, out of the box Rake support will be next. I’ll add Maven to the backlog—if we see a fair amount of demand, we’ll make it happen sooner rather than later.
Thanks,
Chad
Support for Fit would be good. I understand that importing FitNesse pages is on your roadmap. I’m just voting in favor of the idea.
Using Twist as a replacement UI for acceptance tests against business logic (typically done in Fit/Fitnesse) would be the first thing that occurs to me. In fact, when I first heard of Twist, I assumed that this was what it was, and not a driver for UI based functional tests.
I agree with the propostiions here.
Maven is a top selection criteria to us ;o) as it is our build platform
And Fit/Fitnesse import-export would be great, allowing us to combine both Twist with existing test scenarios.
Emmanuel
how about some kind of WindowsForms and/or WPF support?
+1 for WPF support
WebDriver! We've created our own driver in our project, which we'd be happy to contribute (all legal arrangements not considered etc)
2nd on drivers for .net and webdriver.