« Return to Thread: JUnit 4 XML schematized?

Re: Reporting test parameters

by dsaff :: Rate this Message:

Reply to Author | View in Thread

The Description should contain only those things about a test that are
available before the test is run.  I think we're closing in on a
request that additional information discovered during the test run can
be reported through the listener--this is already possible for failed
tests; it looks like we need ignore reasons for ignored tests, and
possibly parameters for parameterized tests.

   David Saff

On Nov 28, 2007 2:17 PM, dfabulich <dan@...> wrote:

> David Saff wrote:
> > That said, I am neither producer nor consumer of the XML syntax, so my
> > only interest is in whether anything we're currently doing makes the
> > XML generation harder than it feels like it needs to be (on which
> > point, the earlier discussion about Ignore reasons is appreciated).
>
> There's another similar issue I noticed just now, namely that it's
> impossible to extract the parameters passed to a Parameterized test.
>
> Instead, the index of the parameter array is packed into the test name
> in brackets, like this: "testFoo[0]" "testFoo[1]" "testFoo[2]".  This
> is true even if the parameters are strings.  There is no way to find
> out what the strings are/were.
>
> It would be better if the runner could add metadata (like parameters)
> to the Description; the metadata could then be handled/interpreted by
> RunListener reporters.
>
> -Dan
>
>
>
>
> Yahoo! Groups Links
>
>
>
>

 « Return to Thread: JUnit 4 XML schematized?