On Monday 13 July 2009 06:56:15 Ovid wrote:
> We currently have over 30,000 tests in our system. It's getting harder to
> manage them. In particular, it's getting harder to find out which TODO
> tests are unexpectedly passing. It would be handy have to some option to
> force TODO tests to die o
* On Mon, Jul 13 2009, Ovid wrote:
> How would Smolder (which we're not using since we use Hudson) help
> with this? With over 15,000 tests being reported for t/aggregate.t, I
> think a drill-down would be problematic here. Plus, tying the TODO to
> the appropriate test file being aggregated is ne
Gabor Szabo wrote:
AFAIK due to the number of tests it won't work well in Smolder - but I
have not tried it.
I was referencing to a future version of it ;-)
It's worth a try. Our main test suite at $work has 23,000+ tests and Smolder
handles it just fine.
--
Michael Peters
Plus Three, LP
On Mon, Jul 13, 2009 at 5:10 PM, Michael Peters wrote:
> Gabor Szabo wrote:
>
>> I think it would be better to have a tool (Smolder) be able to display
>> various drill-downs from the aggregated test report.
>
> If you want to see what Smolder would do to your tests, create a TAP archive
> and then
Gabor Szabo wrote:
I think it would be better to have a tool (Smolder) be able to display
various drill-downs from the aggregated test report.
If you want to see what Smolder would do to your tests, create a TAP archive and
then you can upload it to the "Junk" project at http://smolder.plusth
- Original Message
> From: Gabor Szabo
>
> I think it would be better to have a tool (Smolder) be able to display
> various drill-downs from the aggregated test report.
> e.g. list of all the TODOs
> list of all the TODOs that pass
> etc...
How would Smolder (which we're not using since
On Mon, Jul 13, 2009 at 4:56 PM, Ovid wrote:
>
> We currently have over 30,000 tests in our system. It's getting harder to
> manage them. In particular, it's getting harder to find out which TODO tests
> are unexpectedly passing. It would be handy have to some option to force
> TODO tests to
We currently have over 30,000 tests in our system. It's getting harder to
manage them. In particular, it's getting harder to find out which TODO tests
are unexpectedly passing. It would be handy have to some option to force TODO
tests to die or bailout if they pass (note that this behavior M
