junitmax : Messages : 224-266 of 545

To use NUnit in your project, install NUnit to your computer. Then in Visual
Studio 2005, create a new Class Library project. After project opens, add new
reference.I got this tool from www.macrotesting.com . I hope you can get useful
resources from this site .I macrotesting , lot of resources are there such as
ebooks , documents , applications , Job alerts, etc,....

Reply | Messages in this Topic (1)

#238

From: Kent Beck <kentb@...>
Date: Wed Jun 30, 2010 1:50 pm
Subject: Relaunch of JUnit Max

kentlbeck

Those of you who were subscribers will have already received the following. Please pardon the duplication.

Dear JUnit Max supporter:

While we developed JUnit Max using Lean Startup concepts and suspended our development last year, we find that we may have been hasty in our decision. The truth is that we miss Max when we don't have it. There has been continued interest in JUnit Max and we have decided to once again offer this tool for sale and continue with its development at a sustainable pace. We are commited to supporting JUnit Max and continued development of the tool for at least the next two years.

Since you were an early adopter of JUnit Max we wanted to thank you for your support and continue to offer you this product at the early adopter price of $50 per year. This price is only available to earlier subscribers. Our target price for new users of JUnit Max is $100 per year.

Our commitment is to keep developing JUnit Max and we will continue to need your feedback and support. As someone helping us refine our product, we promise that this early adopter price will continue for you through two more renewals. (Monthly pricing transaction fees consumed too much of our revenue, thus the current yearly pricing structure.)

In order to take advantage of this offer, please order from this page: http://www.junitmax.com/. We have recently checked in a fix for the Mac update problem, the first of many improvements to come.

This offer will be available for the next 60 days after which we will revert to our regular pricing schedule.

Sincerely,

Kent Beck

Three Rivers Institute

Reply | Messages in this Topic (1)

#239

From: "Karl The Pagan" <karlthepagan@...>
Date: Thu Jul 1, 2010 1:18 pm
Subject: Test timeout and debugging

karlthepagan

I find myself frequently writing performance tests and guarding against writing
infinite loops using the JUnit 4 timeout parameter.

What would be the best approach for disabling the timeout when I launch a
JUnitMax debug session?

#240

From: Kent Beck <kentb@...>
Date: Thu Jul 1, 2010 2:30 pm
Subject: Re: Test timeout and debugging

kentlbeck

I have run into the same problem. I don't have a better solution than editing the source file. I'm open to suggestions, though.

Kent

On Jul 1, 2010, at 6:18 AM, Karl The Pagan wrote:

I find myself frequently writing performance tests and guarding against writing infinite loops using the JUnit 4 timeout parameter.

What would be the best approach for disabling the timeout when I launch a JUnitMax debug session?

#241

From: David Saff <david@...>
Date: Thu Jul 1, 2010 10:44 pm
Subject: Re: Test timeout and debugging

dsaff

http://kentbeck.github.com/junit/javadoc/latest/org/junit/rules/Timeout.html

// TestName just because it has no side effects. �Maybe JUnit should have a built-in noop rule.

public final static MethodRule NOOP = new TestName();

@Rule public MethodRule globalTimeout= inMax() ? NOOP : new Timeout(20);

Would that work? �(I haven't said how to implement inMax() yet)

�� David Saff

On Thu, Jul 1, 2010 at 7:30 AM, Kent Beck <kentb@...> wrote:

I have run into the same problem. I don't have a better solution than editing the source file. I'm open to suggestions, though.

Kent

On Jul 1, 2010, at 6:18 AM, Karl The Pagan wrote:

�
I find myself frequently writing performance tests and guarding against writing infinite loops using the JUnit 4 timeout parameter.

What would be the best approach for disabling the timeout when I launch a JUnitMax debug session?

#243

From: "gpx29" <lawrence.s.tierney@...>
Date: Thu Jul 15, 2010 9:01 am
Subject: RAD

gpx29

Hi,

Will this plugin work with RAD 7.0.0.10 (which is build on Eclipse 3.2)?

Lawrence

#244

From: "gpx29" <lawrence.s.tierney@...>
Date: Thu Jul 15, 2010 8:54 am
Subject: License

gpx29

Hi,

Is the license such that I can pay for JUnitMax once and use it in the office
AND home?

Lawrence

#245

From: Kent Beck <kentb@...>
Date: Thu Jul 15, 2010 1:29 pm
Subject: Re: RAD

kentlbeck

Lawrence,

3.3 is the earliest Eclipse I have tested Max with and it worked fine. I don't know about earlier releases. If you try it, please let me know how it goes.

Kent

On Jul 15, 2010, at 2:01 AM, gpx29 wrote:

Hi,

Will this plugin work with RAD 7.0.0.10 (which is build on Eclipse 3.2)?

Lawrence

#246

From: Kent Beck <kentb@...>
Date: Thu Jul 15, 2010 1:30 pm
Subject: Re: License

kentlbeck

Yes, it is connected to your use of the product.

Kent

On Jul 15, 2010, at 1:54 AM, gpx29 wrote:

Hi,

Is the license such that I can pay for JUnitMax once and use it in the office AND home?

Lawrence

#247

From: "elefevre7" <eric@...>
Date: Tue Jul 20, 2010 3:15 pm
Subject: JUnit Max forces saves while refactoring?

elefevre7

Hi everyone,

I've started using JUnit Max with Eclipse Helios today.

When I'm trying to rename something (a value in a enum in my case) using
Eclipse's refactorings, I get a popup requesting me to save the file, while I'm
in the middle of the renaming (haven't hit Enter yet).

After OK'ing that window, if that value is used in another file, then the code
stops compiling, as that other file is not updated with the latest name. From
that point, the refactoring stops working and I need to update everything by
hand.

The only solution I see so far is to disable JUnit Max when refactoring.

Has anyone seen this/found a workaround?

Thanks,

Eric

#248

From: "elefevre7" <eric@...>
Date: Tue Jul 20, 2010 10:39 am
Subject: How to disable 'passed' warnings

elefevre7

Hi everyone,

Is there any way to disable JUnit Max' warnings in Eclipse (those that tell
whether the test has passed)? They are very distracting.

Maybe I'm missing something, because I see that some are classified as Info, not
Warnings (less distracting, but still).

IMHO, it'd be just as well is JUnit Max was not putting any marks in the border.

Thanks,

Eric

#249

From: Kent Beck <kentb@...>
Date: Thu Jul 22, 2010 11:55 pm
Subject: Re: How to disable 'passed' warnings

kentlbeck

Eric,

Thank you for the feedback. One of the goals I had writing Max was to avoid the obtrusive JUnit runner window. If running tests is truly part of the inner loop of programming, then having a "you've had a failure" window pop up makes no more sense than having a "you've had a syntax error" window pop up while you're in the middle of typing. I went with markers because they are a familiar mechanism for providing feedback, easily extended to the kind of behavior needed to display test results.

The "info" markers are for tests that passed and the "warnings" are tests that are running. I could easily be persuaded that neither type needs to appear if there was some other way of keeping track of whether a test had run already.

So, that's the basic problem: display feedback about running state and draw attention to failing tests but without distracting a programmer from programming in the normal case where all the tests are green or only a single test has failed.

Regards,

Kent

On Jul 20, 2010, at 3:39 AM, elefevre7 wrote:

Hi everyone,

Is there any way to disable JUnit Max' warnings in Eclipse (those that tell whether the test has passed)? They are very distracting.

Maybe I'm missing something, because I see that some are classified as Info, not Warnings (less distracting, but still).

IMHO, it'd be just as well is JUnit Max was not putting any marks in the border.

Thanks,

Eric

#250

From: Kent Beck <kentb@...>
Date: Thu Jul 22, 2010 11:55 pm
Subject: Re: JUnit Max forces saves while refactoring?

kentlbeck

This sounds like a defect. I'll try to reproduce it here. In the meantime, do you have the "always save before launch" preference set?

Kent

On Jul 20, 2010, at 8:15 AM, elefevre7 wrote:

Hi everyone,

I've started using JUnit Max with Eclipse Helios today.

When I'm trying to rename something (a value in a enum in my case) using Eclipse's refactorings, I get a popup requesting me to save the file, while I'm in the middle of the renaming (haven't hit Enter yet).

After OK'ing that window, if that value is used in another file, then the code stops compiling, as that other file is not updated with the latest name. From that point, the refactoring stops working and I need to update everything by hand.

The only solution I see so far is to disable JUnit Max when refactoring.

Has anyone seen this/found a workaround?

Thanks,

Eric

#251

From: Eric Lefevre-Ardant <eric@...>
Date: Fri Jul 23, 2010 9:27 am
Subject: Re: How to disable 'passed' warnings

elefevre7

hm... having markers strikes me could also imply that JUnit Max sometimes fails to find tests. Might not be the right message to send.

I do understand that they might be helpful to find tests that were not run (for example, because we forgot the @Test annotation), but I don't think it makes it very obvious.

If you really want to help users find which exact tests have been run, then a Details window might be useful (for example when clicking on the Max button). Or maybe a quick way to show/hide those markers.

FWIW, we've been using Infinitest for almost a year. It doesn't show which exact tests have been run, and we have never complained about it.

Eric

On 23 July 2010 01:55, Kent Beck <kentb@...> wrote:

�

Eric,

Thank you for the feedback. One of the goals I had writing Max was to avoid the obtrusive JUnit runner window. If running tests is truly part of the inner loop of programming, then having a "you've had a failure" window pop up makes no more sense than having a "you've had a syntax error" window pop up while you're in the middle of typing. I went with markers because they are a familiar mechanism for providing feedback, easily extended to the kind of behavior needed to display test results.

The "info" markers are for tests that passed and the "warnings" are tests that are running. I could easily be persuaded that neither type needs to appear if there was some other way of keeping track of whether a test had run already.

So, that's the basic problem: display feedback about running state and draw attention to failing tests but without distracting a programmer from programming in the normal case where all the tests are green or only a single test has failed.

Regards,

Kent

On Jul 20, 2010, at 3:39 AM, elefevre7 wrote:

�
Hi everyone,

Is there any way to disable JUnit Max' warnings in Eclipse (those that tell whether the test has passed)? They are very distracting.

Maybe I'm missing something, because I see that some are classified as Info, not Warnings (less distracting, but still).

IMHO, it'd be just as well is JUnit Max was not putting any marks in the border.

Thanks,

Eric

#252

From: Eric Lefevre-Ardant <eric@...>
Date: Fri Jul 23, 2010 7:41 am
Subject: Re: JUnit Max forces saves while refactoring?

elefevre7

Here are the relevant options I have in the Launching pane of the Preferences (Eclipse Helios).

Save dirty editors editors before launching: Prompt
Wait for ongoing build to complete before launching: Always
Continue launch if project contains errors: Always
Build (if required) before launching: Checked

AFAIK, those as the default options when installing a fresh copy of Eclipse (I have installed vanilla Eclipse Helios 3 days ago. We have automated the settings of some Eclipse preferences, but I don't think those are affected).

Eric

On 23 July 2010 01:55, Kent Beck <kentb@...> wrote:

�

This sounds like a defect. I'll try to reproduce it here. In the meantime, do you have the "always save before launch" preference set?

Kent

On Jul 20, 2010, at 8:15 AM, elefevre7 wrote:

�
Hi everyone,

I've started using JUnit Max with Eclipse Helios today.

When I'm trying to rename something (a value in a enum in my case) using Eclipse's refactorings, I get a popup requesting me to save the file, while I'm in the middle of the renaming (haven't hit Enter yet).

After OK'ing that window, if that value is used in another file, then the code stops compiling, as that other file is not updated with the latest name. From that point, the refactoring stops working and I need to update everything by hand.

The only solution I see so far is to disable JUnit Max when refactoring.

Has anyone seen this/found a workaround?

Thanks,

Eric

#253

From: Klaus Wuestefeld <klauswuestefeld@...>
Date: Mon Jul 26, 2010 10:50 pm
Subject: Re: How to disable 'passed' warnings

klauswuestefeld

Max still has the markers for "running" and "ok" tests? Just drop them.

On Fri, Jul 23, 2010 at 6:27 AM, Eric Lefevre-Ardant <eric@...> wrote:

�

hm... having markers strikes me could also imply that JUnit Max sometimes fails to find tests. Might not be the right message to send.

I do understand that they might be helpful to find tests that were not run (for example, because we forgot the @Test annotation), but I don't think it makes it very obvious.

If you really want to help users find which exact tests have been run, then a Details window might be useful (for example when clicking on the Max button). Or maybe a quick way to show/hide those markers.

FWIW, we've been using Infinitest for almost a year. It doesn't show which exact tests have been run, and we have never complained about it.

Eric

On 23 July 2010 01:55, Kent Beck <kentb@...> wrote:

�

Eric,

Thank you for the feedback. One of the goals I had writing Max was to avoid the obtrusive JUnit runner window. If running tests is truly part of the inner loop of programming, then having a "you've had a failure" window pop up makes no more sense than having a "you've had a syntax error" window pop up while you're in the middle of typing. I went with markers because they are a familiar mechanism for providing feedback, easily extended to the kind of behavior needed to display test results.

The "info" markers are for tests that passed and the "warnings" are tests that are running. I could easily be persuaded that neither type needs to appear if there was some other way of keeping track of whether a test had run already.

So, that's the basic problem: display feedback about running state and draw attention to failing tests but without distracting a programmer from programming in the normal case where all the tests are green or only a single test has failed.

Regards,

Kent

On Jul 20, 2010, at 3:39 AM, elefevre7 wrote:

�
Hi everyone,

Is there any way to disable JUnit Max' warnings in Eclipse (those that tell whether the test has passed)? They are very distracting.

Maybe I'm missing something, because I see that some are classified as Info, not Warnings (less distracting, but still).

IMHO, it'd be just as well is JUnit Max was not putting any marks in the border.

Thanks,

Eric

#254

From: Francisco Laguna de la Vera <fla@...>
Date: Mon Jul 26, 2010 11:09 pm
Subject: Re: [bulk]: Re: How to disable 'passed' warnings

fla_synapps

Hm. I'll chime in on the "I like" side of the discussion. I'm rather fond of the "passed" markers, make me feel all warm and fuzzy, which does a lot for my motivation (not joking here!). The only thing topping this would be MMORPG-like achievements, like a cool badge for a certain test coverage...

On 27.07.2010, at 00:50, Klaus Wuestefeld wrote:

Max still has the markers for "running" and "ok" tests? Just drop them.

On Fri, Jul 23, 2010 at 6:27 AM, Eric Lefevre-Ardant <eric@ericlefevre.net> wrote:

hm... having markers strikes me could also imply that JUnit Max sometimes fails to find tests. Might not be the right message to send.

I do understand that they might be helpful to find tests that were not run (for example, because we forgot the @Test annotation), but I don't think it makes it very obvious.

If you really want to help users find which exact tests have been run, then a Details window might be useful (for example when clicking on the Max button). Or maybe a quick way to show/hide those markers.

FWIW, we've been using Infinitest for almost a year. It doesn't show which exact tests have been run, and we have never complained about it.

Eric

On 23 July 2010 01:55, Kent Beck <kentb@earthlink.net> wrote:

Eric,

Thank you for the feedback. One of the goals I had writing Max was to avoid the obtrusive JUnit runner window. If running tests is truly part of the inner loop of programming, then having a "you've had a failure" window pop up makes no more sense than having a "you've had a syntax error" window pop up while you're in the middle of typing. I went with markers because they are a familiar mechanism for providing feedback, easily extended to the kind of behavior needed to display test results.

The "info" markers are for tests that passed and the "warnings" are tests that are running. I could easily be persuaded that neither type needs to appear if there was some other way of keeping track of whether a test had run already.

So, that's the basic problem: display feedback about running state and draw attention to failing tests but without distracting a programmer from programming in the normal case where all the tests are green or only a single test has failed.

Regards,

Kent

On Jul 20, 2010, at 3:39 AM, elefevre7 wrote:

Hi everyone,

Is there any way to disable JUnit Max' warnings in Eclipse (those that tell whether the test has passed)? They are very distracting.

Maybe I'm missing something, because I see that some are classified as Info, not Warnings (less distracting, but still).

IMHO, it'd be just as well is JUnit Max was not putting any marks in the border.

Thanks,

Eric

#255

From: "elefevre7" <eric@...>
Date: Tue Jul 27, 2010 3:13 pm
Subject: Re: Excluding not-unit tests

elefevre7

Kent,

Has there been any update on that front?
I'm finding that JUnit Max runs our functional tests (which are slow and
somewhat error prone, as they do remote HTTP calls and various other things that
require a full build).

Ideally, I'd like to exclude class names that end in *TestFunctional.

For the moment, I can mostly get by by disabling JUnit Max on the projects that
contains almost all our functional tests. However, I'm losing the unit tests
that are there as well (in sub-packages, compared to the packages that contain
the functional tests).

Thanks,

Eric

--- In junitmax@yahoogroups.com, "kentb" <kentb@...> wrote:
>
> I've always felt that test selection is best dealt with by tools not by the
> framework. The plan in Max is to include/exclude tests either by source
> folder or by package. I'd like to keep the mechanism as simple as possible
> consistent with meeting the goal of not running tests that aren't helpful.
>
> Regards,
>
> Kent
>
>   _____
>
> From: junitmax@yahoogroups.com [mailto:junitmax@yahoogroups.com] On Behalf
> Of Dmitry Kandalov
> Sent: Sunday, March 15, 2009 2:59 PM
> To: junitmax@yahoogroups.com
> Subject: [junitmax] Excluding not-unit tests
>
>
>
> Hello Kent,
>
> Given that junit is sometimes used to write functional tests, wouldn't it be
> a good idea to filter out these tests (by
> annotations, for example)?
>
> Dima
>

#256

From: Kent Beck <kentb@...>
Date: Tue Jul 27, 2010 3:54 pm
Subject: Re: Re: Excluding not-unit tests

kentlbeck

Eric,

Each project has JUnit Max properties which allow you to enable/disable source folders and packages (presented as a tree) for running by Max. Select the project, choose "Properties", select "JUnit Max", and you should see the tree.

Does that meet your need?

Kent

On Jul 27, 2010, at 8:13 AM, elefevre7 wrote:

Kent,

Has there been any update on that front?
I'm finding that JUnit Max runs our functional tests (which are slow and somewhat error prone, as they do remote HTTP calls and various other things that require a full build).

Ideally, I'd like to exclude class names that end in *TestFunctional.

For the moment, I can mostly get by by disabling JUnit Max on the projects that contains almost all our functional tests. However, I'm losing the unit tests that are there as well (in sub-packages, compared to the packages that contain the functional tests).

Thanks,

Eric

--- In junitmax@yahoogroups.com, "kentb" <kentb@...> wrote:
>
> I've always felt that test selection is best dealt with by tools not by the
> framework. The plan in Max is to include/exclude tests either by source
> folder or by package. I'd like to keep the mechanism as simple as possible
> consistent with meeting the goal of not running tests that aren't helpful.
>
> Regards,
>
> Kent
>
> _____
>
> From: junitmax@yahoogroups.com [mailto:junitmax@yahoogroups.com] On Behalf
> Of Dmitry Kandalov
> Sent: Sunday, March 15, 2009 2:59 PM
> To: junitmax@yahoogroups.com
> Subject: [junitmax] Excluding not-unit tests
>
>
>
> Hello Kent,
>
> Given that junit is sometimes used to write functional tests, wouldn't it be
> a good idea to filter out these tests (by
> annotations, for example)?
>
> Dima
>

#257

From: Eric Lefevre-Ardant <eric@...>
Date: Tue Jul 27, 2010 4:03 pm
Subject: Re: Re: Excluding not-unit tests

elefevre7

That's what I did when I mentioned I had disabled JUnit Max on some projects.

I couldn't disable it just for functional tests, because they either are in the same packages or in packages above unit tests (apparently, it is not possible to disable Max on a sub-package and allow it in higher-level packages).

So currently some of my unit tests are not run. Not a huge deal, but still.

Eric

On 27 July 2010 17:54, Kent Beck <kentb@...> wrote:

�

Eric,

Each project has JUnit Max properties which allow you to enable/disable source folders and packages (presented as a tree) for running by Max. Select the project, choose "Properties", select "JUnit Max", and you should see the tree.

Does that meet your need?

Kent

On Jul 27, 2010, at 8:13 AM, elefevre7 wrote:

�
Kent,

Has there been any update on that front?
I'm finding that JUnit Max runs our functional tests (which are slow and somewhat error prone, as they do remote HTTP calls and various other things that require a full build).

Ideally, I'd like to exclude class names that end in *TestFunctional.

For the moment, I can mostly get by by disabling JUnit Max on the projects that contains almost all our functional tests. However, I'm losing the unit tests that are there as well (in sub-packages, compared to the packages that contain the functional tests).

Thanks,

Eric

--- In junitmax@yahoogroups.com, "kentb" <kentb@...> wrote:
>
> I've always felt that test selection is best dealt with by tools not by the
> framework. The plan in Max is to include/exclude tests either by source
> folder or by package. I'd like to keep the mechanism as simple as possible
> consistent with meeting the goal of not running tests that aren't helpful.
>
> Regards,
>
> Kent
>
> _____
>
> From: junitmax@yahoogroups.com [mailto:junitmax@yahoogroups.com] On Behalf
> Of Dmitry Kandalov
> Sent: Sunday, March 15, 2009 2:59 PM
> To: junitmax@yahoogroups.com
> Subject: [junitmax] Excluding not-unit tests
>
>
>
> Hello Kent,
>
> Given that junit is sometimes used to write functional tests, wouldn't it be
> a good idea to filter out these tests (by
> annotations, for example)?
>
> Dima
>

#258

From: Kent Beck <kentb@...>
Date: Tue Jul 27, 2010 5:40 pm
Subject: Re: Re: Excluding not-unit tests

kentlbeck

Eric,

So as I understand it you have slower tests in parent packages of faster ("Maxable"?) tests. I will put a more flexibile selection scheme on the list, but to be honest it isn't a priority at the moment.

Regards,

Kent

On Jul 27, 2010, at 9:03 AM, Eric Lefevre-Ardant wrote:

That's what I did when I mentioned I had disabled JUnit Max on some projects.
I couldn't disable it just for functional tests, because they either are in the same packages or in packages above unit tests (apparently, it is not possible to disable Max on a sub-package and allow it in higher-level packages).

So currently some of my unit tests are not run. Not a huge deal, but still.

Eric

On 27 July 2010 17:54, Kent Beck <kentb@earthlink.net> wrote:

Eric,

Each project has JUnit Max properties which allow you to enable/disable source folders and packages (presented as a tree) for running by Max. Select the project, choose "Properties", select "JUnit Max", and you should see the tree.

Does that meet your need?

Kent

On Jul 27, 2010, at 8:13 AM, elefevre7 wrote:

Kent,

Has there been any update on that front?
I'm finding that JUnit Max runs our functional tests (which are slow and somewhat error prone, as they do remote HTTP calls and various other things that require a full build).

Ideally, I'd like to exclude class names that end in *TestFunctional.

For the moment, I can mostly get by by disabling JUnit Max on the projects that contains almost all our functional tests. However, I'm losing the unit tests that are there as well (in sub-packages, compared to the packages that contain the functional tests).

Thanks,

Eric

--- In junitmax@yahoogroups.com, "kentb" <kentb@...> wrote:
>
> I've always felt that test selection is best dealt with by tools not by the
> framework. The plan in Max is to include/exclude tests either by source
> folder or by package. I'd like to keep the mechanism as simple as possible
> consistent with meeting the goal of not running tests that aren't helpful.
>
> Regards,
>
> Kent
>
> _____
>
> From: junitmax@yahoogroups.com [mailto:junitmax@yahoogroups.com] On Behalf
> Of Dmitry Kandalov
> Sent: Sunday, March 15, 2009 2:59 PM
> To: junitmax@yahoogroups.com
> Subject: [junitmax] Excluding not-unit tests
>
>
>
> Hello Kent,
>
> Given that junit is sometimes used to write functional tests, wouldn't it be
> a good idea to filter out these tests (by
> annotations, for example)?
>
> Dima
>

#259

From: Dale Emery <dale@...>
Date: Tue Jul 27, 2010 8:53 pm
Subject: Re: Re: Excluding not-unit tests

dalehemery

Hi Eric,

couldn't disable it just for functional tests, because they either are in the same packages or in packages above unit tests (apparently, it is not possible to disable Max on a sub-package and allow it in higher-level packages).

I note that when I have tests in the same package, but in different source folders, JUnit Max offers two check boxes for the package, one under each source folder.

So I tried an experiment. I put functional tests and unit tests in the same package, but different source folders. Given that I could then select the unit tests but not the functional tests, my expectation was that JUnit Max would run only the unit tests.

Unfortunately, when I select the package in one folder but not the other JUnit Max acts as if none are selected. And when I visit the preferences again, none are selected.

If I select the package in all of the source folders where it appears, naturally JUnit Max runs them all.

Dale

�

Dale Emery
Consultant to software teams and leaders

http://dhemery.com

#260

From: Kent Beck <kentb@...>
Date: Tue Jul 27, 2010 9:19 pm
Subject: Re: Re: Excluding not-unit tests

kentlbeck

That's a defect. I'll get on it.

More generally, I'm hearing from lots of people (we're holding customer interviews right now if you're interested in providing feedback) that there are slow tests and fast tests, and tests that folks rely on for immediate feedback and tests whose feedback folks don't mind waiting for. It would be great if Max could do more to help manage these distinctions.

Now, how to write a test for the folder-shared-between-source-folders case...

Kent

On Jul 27, 2010, at 1:53 PM, Dale Emery wrote:

Hi Eric,

couldn't disable it just for functional tests, because they either are in the same packages or in packages above unit tests (apparently, it is not possible to disable Max on a sub-package and allow it in higher-level packages).

I note that when I have tests in the same package, but in different source folders, JUnit Max offers two check boxes for the package, one under each source folder.

So I tried an experiment. I put functional tests and unit tests in the same package, but different source folders. Given that I could then select the unit tests but not the functional tests, my expectation was that JUnit Max would run only the unit tests.

Unfortunately, when I select the package in one folder but not the other JUnit Max acts as if none are selected. And when I visit the preferences again, none are selected.

If I select the package in all of the source folders where it appears, naturally JUnit Max runs them all.

Dale

�
Dale Emery
Consultant to software teams and leaders
http://dhemery.com

#261

From: Klaus Wuestefeld <klauswuestefeld@...>
Date: Tue Jul 27, 2010 10:24 pm
Subject: Re: Re: Excluding not-unit tests

klauswuestefeld

Hi,

On Byecycle, one of our contributors committed an exclusion scheme based on regular expressions. Very straightforward.

See you, Klaus.

On Tue, Jul 27, 2010 at 6:19 PM, Kent Beck <kentb@...> wrote:

�

That's a defect. I'll get on it.

More generally, I'm hearing from lots of people (we're holding customer interviews right now if you're interested in providing feedback) that there are slow tests and fast tests, and tests that folks rely on for immediate feedback and tests whose feedback folks don't mind waiting for. It would be great if Max could do more to help manage these distinctions.

Now, how to write a test for the folder-shared-between-source-folders case...

Kent

On Jul 27, 2010, at 1:53 PM, Dale Emery wrote:

�
Hi Eric,

�couldn't disable it just for functional tests, because they either are in the same packages or in packages above unit tests (apparently, it is not possible to disable Max on a sub-package and allow it in higher-level packages).

I note that when I have tests in the same package, but in different source folders, JUnit Max offers two check boxes for the package, one under each source folder.

So I tried an experiment. I put functional tests and unit tests in the same package, but different source folders. Given that I could then select the unit tests but not the functional tests, my expectation was that JUnit Max would run only the unit tests.

Unfortunately, when I select the package in one folder but not the other JUnit Max acts as if none are selected. And when I visit the preferences again, none are selected.

If I select the package in all of the source folders where it appears, naturally JUnit Max runs them all.

Dale

�
Dale Emery
Consultant to software teams and leaders
http://dhemery.com

#262

From: Eric Lefevre-Ardant <eric@...>
Date: Wed Jul 28, 2010 9:54 am
Subject: Re: Re: Excluding not-unit tests

elefevre7

OK.

As a side note, it'd be nicer if we didn't have to go through a GUI for this sort of configuration. Having a configuration *file* would make it easier to share it with amongst colleagues.

I agree with Klaus. An exclusion pattern would be nice...

Eric

On 27 July 2010 19:40, Kent Beck <kentb@...> wrote:

�

Eric,

So as I understand it you have slower tests in parent packages of faster ("Maxable"?) tests. I will put a more flexibile selection scheme on the list, but to be honest it isn't a priority at the moment.

Regards,

Kent

On Jul 27, 2010, at 9:03 AM, Eric Lefevre-Ardant wrote:

�
That's what I did when I mentioned I had disabled JUnit Max on some projects.
I couldn't disable it just for functional tests, because they either are in the same packages or in packages above unit tests (apparently, it is not possible to disable Max on a sub-package and allow it in higher-level packages).

So currently some of my unit tests are not run. Not a huge deal, but still.

Eric

On 27 July 2010 17:54, Kent Beck <kentb@...> wrote:

�

Eric,

Each project has JUnit Max properties which allow you to enable/disable source folders and packages (presented as a tree) for running by Max. Select the project, choose "Properties", select "JUnit Max", and you should see the tree.

Does that meet your need?

Kent

On Jul 27, 2010, at 8:13 AM, elefevre7 wrote:

�
Kent,

Has there been any update on that front?
I'm finding that JUnit Max runs our functional tests (which are slow and somewhat error prone, as they do remote HTTP calls and various other things that require a full build).

Ideally, I'd like to exclude class names that end in *TestFunctional.

For the moment, I can mostly get by by disabling JUnit Max on the projects that contains almost all our functional tests. However, I'm losing the unit tests that are there as well (in sub-packages, compared to the packages that contain the functional tests).

Thanks,

Eric

--- In junitmax@yahoogroups.com, "kentb" <kentb@...> wrote:
>
> I've always felt that test selection is best dealt with by tools not by the
> framework. The plan in Max is to include/exclude tests either by source
> folder or by package. I'd like to keep the mechanism as simple as possible
> consistent with meeting the goal of not running tests that aren't helpful.
>
> Regards,
>
> Kent
>
> _____
>
> From: junitmax@yahoogroups.com [mailto:junitmax@yahoogroups.com] On Behalf
> Of Dmitry Kandalov
> Sent: Sunday, March 15, 2009 2:59 PM
> To: junitmax@yahoogroups.com
> Subject: [junitmax] Excluding not-unit tests
>
>
>
> Hello Kent,
>
> Given that junit is sometimes used to write functional tests, wouldn't it be
> a good idea to filter out these tests (by
> annotations, for example)?
>
> Dima
>

#263

From: "david_vanc" <david.vancouvering@...>
Date: Wed Jul 28, 2010 4:21 pm
Subject: Trial version

david_vanc

Hi!  I tried searching this forum, but the search engine appears to be down.

I really would like a try-before-you-buy, or some ability to get my money back
if I don't find it useful.

Of particular concern is the ability to exclude slow tests - we have some *very*
slow tests.  Our pattern is tests with the suffix "UTest" are known to be fast,
individual unit tests, where functional tests end it just "Test".  They are all
mixed together in the same packages.  Some of our functional tests do network
I/O and can take 20 minutes to run, and can break due to environmental issues. 
I really need to exclude these or using JUnit Max is basically a non-starter...

Thanks!

David

#264

From: Kent Beck <kentb@...>
Date: Wed Jul 28, 2010 4:37 pm
Subject: Re: Trial version

kentlbeck

David,

If you aren't satisfied with Max, we will send your money back.

The current include/exclude mechanism uses source folders and packages. Others have suggested regular expression matching, which seems like it would fit your situation well. I don't have a date for implementing this, though.

Regards,

Kent

On Jul 28, 2010, at 9:21 AM, david_vanc wrote:

Hi! I tried searching this forum, but the search engine appears to be down.

I really would like a try-before-you-buy, or some ability to get my money back if I don't find it useful.

Of particular concern is the ability to exclude slow tests - we have some *very* slow tests. Our pattern is tests with the suffix "UTest" are known to be fast, individual unit tests, where functional tests end it just "Test". They are all mixed together in the same packages. Some of our functional tests do network I/O and can take 20 minutes to run, and can break due to environmental issues. I really need to exclude these or using JUnit Max is basically a non-starter...

Thanks!

David

#265

From: "pniederw" <pniederw@...>
Date: Mon Aug 2, 2010 3:38 pm
Subject: Does JUnit Max work with custom @RunWith runners?

pniederw

Does JUnit Max work with custom @RunWith runners, or just with the ones that
ship with JUnit?

Cheers,
Peter

#266

From: Kent Beck <kentb@...>
Date: Mon Aug 2, 2010 4:03 pm
Subject: Re: Does JUnit Max work with custom @RunWith runners?

kentlbeck

Peter,

I hadn't tried it, but I just did and it works fine for the case I used (once I remembered how to write a custom runner).

Kent

On Aug 2, 2010, at 8:38 AM, pniederw wrote:

Does JUnit Max work with custom @RunWith runners, or just with the ones that ship with JUnit?

Cheers,
Peter