Loading ...
Sorry, an error occurred while loading the content.

Continuous Testing Eclipse Plugin

Expand Messages
  • Williams, Chris
    An earlier thread discussed the viability of a continuous testing plugin or tool that would automatically run xUnit tests whenever a new compile was
    Message 1 of 1 , Sep 7, 2004
    • 0 Attachment
      An earlier thread discussed the viability of a continuous testing plugin or
      tool that would automatically run xUnit tests whenever a new compile was
      successful.

      The Continuous Testing plugin by David Saff for Eclipse does just this and
      also creates markers and annotations in the text to mark failures. My
      biggest complaint was that its options for tests to run was either: all,
      none, or a specific suite. In response I sent an e-mail to David asking for
      a more intelligent test selection and here's what he has to say:

      The latest release (1.1.0) creates
      an extension point in Eclipse that allows Eclipse extenders to implement
      what we call "Test Selectors", with the exact same intent that you
      specify below: the test selector is a class that, based on testing
      history and recent changes, identifies only those tests that need to be
      run this time through.

      So now it should be easy for anyone with time and some fairly intimate
      knowledge of Eclipse to write their own test selector. Where we're
      behind is in offering a good assortment of test selectors (or even just
      one good one) out of the box, for two reasons: 1) I wasn't sure what
      would work for any significant set of JUnit-using developers. 2) My
      strategy right now has been to encourage two developers that have been
      working on test selection in JUnit to port their tools into my
      framework, but that encouragement hasn't been successful yet. In the
      meantime, I think your suggestion is a good starting point that would
      fill in an important gap for many developers.

      I've added your suggestion to our bugzilla database:

      http://daikon.csail.mit.edu/bugzilla/show_bug.cgi?id=173
      <http://daikon.csail.mit.edu/bugzilla/show_bug.cgi?id=173>

      Feel free to add yourself to our bugzilla to watch progress on this bug,
      or encourage your colleagues to vote for it. :) We're currently in a
      bughunting phase leading up to 1.2.0 sometime mid-month.


      So anyone else who uses this plugin and would like to see some nice "test
      selectors" that would more intelligently find the matching test cases for
      code currently being edited, please join in and vote this one up! Or do one
      better and write a test selector that can find out via reference tracking
      which tests directly or indirectly affect the modified code...

      Thanks!
      Chris



      [Non-text portions of this message have been removed]
    Your message has been successfully submitted and would be delivered to recipients shortly.