it’s probably a known issue that when you run part...

# spek

[codeslubber]

it’s probably a known issue that when you run parts of a spec (click the green arrow next to a describe, e.g.), it still runs other parts of the test.. ?

[hhariri]

are you using our test runner or something else?

[codeslubber]

Yes. I have the plugin installed, using the runner. Cedric came on one night and I shared an example repo and of course his solution was to just port it to kobalt and back to Junit 4.x and sure enough from the command line tests ran in < 1s. (I knew that.)

[codeslubber]

but I want to write some code, hit a key combo, rerun… rinse/repeat..

[codeslubber]

wait sorry Hadi, I was thinking maybe you were asking because of my earlier comment about incremental compilation not working.. (idiot)

[codeslubber]

ok on this other one

[codeslubber]

I have a test that dumps a large doc to the console, from inside a describe block, I run this other test and that file still goes to the console...

[codeslubber]

Also, why not let me rerun individual tests from inside the runner? think that would be useful

[minivac]

Same problem, you can't run a test it("...") { ... } in isolation, everything inside the class is executed

[raniejade]

Are the `it`s inside an on block? If yes, it's a known issue.

[codeslubber]

yes they are inside an on block

[codeslubber]

ok thanks