in reply to Re: Test Harnesses Meditation of Dissatisfaction
in thread Test Harnesses (in general) -- Meditation of Dissatisfaction

When I asked why this dept was using a CPU heavy/Java test harness rather than one written (and written well, ot course) in C, I was told (under the table) that long ago, it was a political decision! It would have hurt more people's feelings to choose the C one over the Java one!

Well if the code being tested is Java I'd go the Java route too. Keeping the testing framework and the code being tested in the same language usually makes things much easier.

If I were you I'd just start things moving to one of the decent Java frameworks. TestNG is very nice, and the latest JUnit is pretty good too.

  • Comment on Re^2: Test Harnesses Meditation of Dissatisfaction

Replies are listed 'Best First'.
Re^3: Test Harnesses Meditation of Dissatisfaction
by jffry (Hermit) on Mar 27, 2006 at 23:52 UTC
    I'll go ahead and suggest that our current test harness maintainer take a look at these Java test harnesses. Maybe he can get something useful from them.

    Again, I can't make major architectural decisions on the test harness. About the most I can do is request features if I can justify them. Although, in the next few years I might be able to make a case for those other Open Source harnesses you suggested.

    As for writing the tests in Java just because the harness is writen in Java, well, it doesn't really matter. The harness-to-test interface is language independent. It has it's own syntax, and coding in Java gains no added benefit.

    But thanks again for suggesting JUnit & TestNG. That may very well turn the corner for our dept in the years to come. I mean it. Sincerely.

[reply]

In Section Meditations