Need better workflow when writing many pending tests and using documentation-reporter

[thesoftwarephilosopher]

@slagyr

Usually I'll write all the pending tests I'll need right up front before starting a feature.

However, using the documentation-reporter, each pending test takes up 4 lines[a]. When I start working on one, the pending tests are printed after the failures. If there's enough pending tests, or I'm working on my laptop with a smaller screen, the pending tests easily push the failures way off the screen.

Here are the solutions I've thought of:

1. show the name of the pending test in documentation-reporter, omitting the other 3 lines (this could be a command-line option).
2. print failures results after pending tests.
3. print pending tests before the rest of the tests, but this isn't a good idea because then I'll never see that I have pending tests.

Out of these, I think I like # 2 the best.

Thoughts?

[a]: one for the description, one for the pending-reason (even if not given), one for the file, and one for a space between them

[slagyr]

I don't know.... You have a specific process. Someone else's process may want pending specs showing up last. Speclj will never be able to satisfies everyone's process. I think I have to say "no" to this one.

Oh! You could write a customer reporter to do as you like!