[#IDEA-18808] Ability to create executable groups of unit tests

IDEA: Feedback

Ability to create executable groups of unit tests

Created: 19 Jul 08 19:12 Updated: 22 Jul 08 17:10

Component/s:

Unit Testing. JUnit

Build:	8,526
Severity:	Low

Description

« Hide

Id like the ability to be able to specify multiple test classes and/or packages in a unit test configuration.
Currently, you can only group tests based on the package hierarchy, and this rarely meshes well with reality on a project developed over many years, by multiple developers, with 10,000 unit tests.

Example:

I modify a base "date" class. I know that I want to run the DateTests. I also want to make sure that I haven't broken any Coupon/Dividend math across the financial packages. While I could cover all bases by running the unit tests at the com.* level, running large numbers of unit tests, no matter how quick they are (and some unit tests just dont run that fast), is prohibitive.

The ability to specify multiple classes / package groups in the unit test configuration would be very helpful.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dmitry Jemerov - 21 Jul 08 12:35

You do have this possibility, by means of writing a JUnit TestSuite class.

[ Permlink | « Hide ]

Nick Pratt - 21 Jul 08 17:14

Yes, I do have the option of writing additional code to do this. I also have this option for almost every single thing that IDEA does for me.
I also have the option of using Windows Notepad or Emacs to edit Java code, but I choose to use an editor that makes life easier for me.

This would make life easier - why could we not select classes/packages in the project view and simply "run selected tests" or even in the run configuration, simply allow a multiple line input box rather than just the current single line class/package specifier TextField?

[ Permlink | « Hide ]

Nick Pratt - 22 Jul 08 17:03

Outside of logging this issue, I had another IDEA 7.0 developer assume that he could run arbitrary tests by multi-selecting test cases in the project viewer, and then assume that he could "Edit Configurations" to enter in multiple test case classes by hand.

I never mentioned this issue, but I watched him try and do this and when he seem surprised that he couldnt, I mentioned this issue. This is a very logical thing to do - in the package that we were working in, we have over 500 test classes, all testing separate data providers in a hierarchy (objects that feed data values to a finance related GUI). We dont want to run all these tests every time we touch one data object, but we do want to run several that we know about (some composite objects, some separate ones etc).

I think this would be a very valuable and used feature