Unit test prep painfully slow

Anyone else seeing a problem where preparing the unit tests is PAINFULLY slow? I get this little timer saying "preparing unit tests" and it sometimes counts up to 0:20 (as in twenty seconds). Right now I'm running a single unit test and it takes 9 seconds to "prepare", whatever that means. This is pretty annoying!

Note: I have two VMs open in debug mode while doing this. Not sure if this helps, but whenever I change my test and re-run it, the Make command takes forever as well (usually 5+ seconds). And then if I choose to Hotswap, it sometimes happens instantly but other times takes 3-4 seconds. Add it all up and my test-code-test cycle is getting REALLY delayed.

Pat

5 comments

Is it fast or the same slow if you run it without IDEA e.g. with text
runner?

--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Pat Lightbody" <plightbo@hotmail.com> wrote in message
news:22314080.1075397186125.JavaMail.itn@is.intellij.net...

Anyone else seeing a problem where preparing the unit tests is PAINFULLY

slow? I get this little timer saying "preparing unit tests" and it sometimes
counts up to 0:20 (as in twenty seconds). Right now I'm running a single
unit test and it takes 9 seconds to "prepare", whatever that means. This is
pretty annoying!
>

Note: I have two VMs open in debug mode while doing this. Not sure if this

helps, but whenever I change my test and re-run it, the Make command takes
forever as well (usually 5+ seconds). And then if I choose to Hotswap, it
sometimes happens instantly but other times takes 3-4 seconds. Add it all up
and my test-code-test cycle is getting REALLY delayed.
>

Pat

>


0

I can't find where I can change to the text runner -- it's not where it used to be. :(

0

Oh, sorry, I misread your question.

The test itself runs very fast, but there is usually 5-15 seconds spent on "Instantiating tests..." when I first run the test class. Once they start they fly through.

0

Actually "Instantiating tests..." doesn't mean "tests are still not
instantiated". You may see this until some of them becomes finished. For
instance you may see such message if the first test takes much time to start
up (in spite of test is counted started before TestCase.setUp() method
called).

--

Dmitry Peshehonov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


"Pat Lightbody" <plightbo@hotmail.com> wrote in message
news:8374679.1075411688358.JavaMail.itn@is.intellij.net...

Oh, sorry, I misread your question.

>

The test itself runs very fast, but there is usually 5-15 seconds spent on

"Instantiating tests..." when I first run the test class. Once they start
they fly through.


0

I don't think that this is the case:

public class TestAdd extends TestCase {
public void testAdd() {
assertEquals(4, 2 + 2);
}
}

... TAKES SIX SECONDS TO RUN ...

:P

Also, doing a project build (Make) has this weird delay that is the most obnoxious thing in the world. You guys really need to figure out where these delays are coming from (logging? some lock somewhere?) and get rid of them once and for all. I see delays (maybe related, maybe not) in unit tests, building, and debugging. The three things I do more of than anything else.

0

Please sign in to leave a comment.