Home » Language IDEs » Java Development Tools (JDT) » Announce: new plug-in for continuous testing
| Announce: new plug-in for continuous testing [message #145134] |
Tue, 24 February 2004 22:28  |
Eclipse User |
|
|
|
All,
For the last year, I have been researching the idea of continuous
testing. Continuous testing builds on the automated developer support
in Eclipse to make it even easier to keep your Java code well-tested, if
you have a JUnit test suite. With continuous testing enabled, as you
edit your code, Eclipse runs your tests quietly in the background, and
notifies you if any of them fail or cause errors. It is most useful in
situations where you would already have a test suite while you are
changing code: when performing maintenance, refactoring, or using
test-first development.
Continuous testing builds on the following features of Eclipse:
* JUnit integration: Test suites run under continuous testing give
you the same information, in the same format, that you already get from
Eclipse's JUnit integration. However, continuous testing also helps to
automate the choice of when to run tests, which tests to run, and in
which order.
* Compile error notification: As soon as you write code that
contains a compilation error, Eclipse highlights the error in the text
and the margin, and creates a task in the Problems table. This makes it
easy both to quickly find out if what you wrote was wrong, and to step
through and fix problems in an orderly fashion. With continuous testing,
you get the same kind of notification when you write or edit code that
causes one of your tests to fail. However, test failures are different
from compile errors in several ways: test failures can sometimes not
easily be tracked to a single line of code, and test failures also can
provide more information, such as a backtrace, than compile errors.
We have implemented a plug-in that implements continuous testing in
Eclipse. This plug-in is similar to intent to the one developed in
Erich Gamma and Kent Beck's _Contributing to Eclipse_. Gamma and Beck's
plug-in includes an editor for excluding tests from automatic execution.
Ours includes asynchronous test execution through the build framework,
detailed specification of the launch configuration and environment for
automatic tests, test prioritization, and other enhancements. For
installation instructions, documentation, and further information on my
research, please see
http://pag.csail.mit.edu/~saff/continuoustesting.html
To comment and vote on this feature as an enhancement to Eclipse, please
visit
https://bugs.eclipse.org/bugs/show_bug.cgi?id=51292
Thank you for your time,
David Saff
|
|
|
| Re: Announce: new plug-in for continuous testing [message #145150 is a reply to message #145134] |
Wed, 25 February 2004 03:58  |
| Eclipse User |
|
|
|
>This plug-in is similar to intent to the one developed in ... _Contributing
to Eclipse_.
David is too shy here <g> This work goes way beyond what we did in the book.
Definitely worth to give it a try and to provide feedback in the bug report
referred to below.
--erich
"David Saff" <saff@mit.edu> wrote in message
news:c1h4f7$4mc$1@eclipse.org...
> All,
>
> For the last year, I have been researching the idea of continuous
> testing. Continuous testing builds on the automated developer support
> in Eclipse to make it even easier to keep your Java code well-tested, if
> you have a JUnit test suite. With continuous testing enabled, as you
> edit your code, Eclipse runs your tests quietly in the background, and
> notifies you if any of them fail or cause errors. It is most useful in
> situations where you would already have a test suite while you are
> changing code: when performing maintenance, refactoring, or using
> test-first development.
>
> Continuous testing builds on the following features of Eclipse:
>
> * JUnit integration: Test suites run under continuous testing give
> you the same information, in the same format, that you already get from
> Eclipse's JUnit integration. However, continuous testing also helps to
> automate the choice of when to run tests, which tests to run, and in
> which order.
> * Compile error notification: As soon as you write code that
> contains a compilation error, Eclipse highlights the error in the text
> and the margin, and creates a task in the Problems table. This makes it
> easy both to quickly find out if what you wrote was wrong, and to step
> through and fix problems in an orderly fashion. With continuous testing,
> you get the same kind of notification when you write or edit code that
> causes one of your tests to fail. However, test failures are different
> from compile errors in several ways: test failures can sometimes not
> easily be tracked to a single line of code, and test failures also can
> provide more information, such as a backtrace, than compile errors.
>
> We have implemented a plug-in that implements continuous testing in
> Eclipse. This plug-in is similar to intent to the one developed in
> Erich Gamma and Kent Beck's _Contributing to Eclipse_. Gamma and Beck's
> plug-in includes an editor for excluding tests from automatic execution.
> Ours includes asynchronous test execution through the build framework,
> detailed specification of the launch configuration and environment for
> automatic tests, test prioritization, and other enhancements. For
> installation instructions, documentation, and further information on my
> research, please see
>
> http://pag.csail.mit.edu/~saff/continuoustesting.html
>
> To comment and vote on this feature as an enhancement to Eclipse, please
> visit
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=51292
>
> Thank you for your time,
>
> David Saff
|
|
| |
Goto Forum:
Current Time: Sat Jul 19 10:35:08 EDT 2025
Powered by FUDForum. Page generated in 0.07509 seconds |
Home