Twistpublic

Feature Requests

Use this forum to post things that you would like to see in future versions of Twist

This is a public Discussion Area  publicRSS

Post

    David Mack
    Folder support for scenarios
    Post posted November 2, 2008 by David Mack, last edited May 15, 2012
    2056 Views, 5 Comments
    Topic:
    Folder support for scenarios
    Body:
    Hi, I am writing/have written a large number of Twist tests and I would like to be able to divide my tests not only with the tags but also with a directory structure (still contained with in the scenarios folder). At the moment you can divide them with the folders but Twist can’t find the files to run so you have to move the file to the top level when you want it … which is a pain. Thanks, (100 files is a pain to look at)

    Comment

     

    • Ketan Padegaonkar
      posted November 2, 2008 by Ketan Padegaonkar

      Hi David,

      Thanks for the feedback! We’ll look into this feature request as well.

      As a workaround, you can:
      • find the file in the package explorer view or the navigation view and right click on it to execute it
      • hit CTRL+SHIFT+R (CMD+SHIFT+R on mac) to find the file

      —Ketan

    • James O'Sullivan
      posted June 5, 2009 by James O'Sullivan

      +1 for this feature. Thanks!

    • Matt Jackson
      posted February 4, 2011 by Matt Jackson

      +1 for this feature from me too

    • Wim Heemskerk
      posted May 7, 2012 by Wim Heemskerk

      Well, it works out for scenarios (so far for us). Tags do seem to be the modern way to go. Perhaps its just old school me finding it hard to let go of the 'primary' structure offered by folders.

       

      It's the concepts that are the real mess; no tags, no folders. I'd very much like to order these in some way. I'm thinking packages (a folder structure) just like the fixtures have. Do you have something planned for this?

      Among other things, this should allow multiple concepts with the same name. This is something I'm currently struggling with, as we are getting many scenario's that share some steps, from a functional business perspective (the scenario level), though the flow underneath these steps can be subtly different (the concepts level). Therefore I want to implement the same functional step in several different ways. Right now that takes additions to the natural language name that are rather distracting. (Project is so far 100% WebDriver based. We're using this concept for the layering: http://gojko.net/2010/04/13/how-to-implement-ui-testing-without-shooting-yourself-in-the-foot-2/ )

       

    • Srijayanth Sridhar
      posted May 15, 2012 by Srijayanth Sridhar

      Hello Wim,

       

      With reference to http://community.thoughtworks.com/posts/b584ece04b 

       

      Multiple concepts with the same name is a challenge because we will have to find a way to identify various concepts based on where you use them. This would also have an implication on the types of parameters you use. I understand that you have minor variations to a larger business level, in which case, I suggest using the "Push To Implementation" feature in tandem with Spring's profile features to achieve your case of having the larger domain level having different implementations underneath. 

      Concepts would certainly not help in this regard and aren't meant for that specific use case.

       

      Thank you,

       

      Jayanth