Issue 16 in yatspec: Parametrised tests ignored in report when using constant in @Row annotation

[yat...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 16 by albertof...@gmail.com: Parametrised tests ignored in report
when using constant in @Row annotation
http://code.google.com/p/yatspec/issues/detail?id=16

What steps will reproduce the problem?
1. Create a String constant "static final" with name MY_CONSTANT and
value "my value"
2. Create a parametrised test using @Table and @Row
3. Name the test parameter String myParam
3. Just fill it with Assert.fail()
3. Run your build.

What is the expected output? What do you see instead?
Expected result: Build fails, report should show "Scenarios myParam "my
value" with the test failed in red

Actual: Test fails the build. Report shows test not run (orange).
Under scenarios table you can see the name of the constant MY_CONSTANT
instead of the value

What version of the product are you using? On what operating system?
yatspec-198, Windows7, Eclipse, Maven

Please provide any additional information below.
I think QDoxto returns the name of the constant when parsing the
annotations in the test files.