Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parametrised tests ignored in report when using constant in @Row annotation #16

Open
GoogleCodeExporter opened this issue Mar 19, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

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.

Original issue reported on code.google.com by albertof...@gmail.com on 19 Sep 2012 at 3:23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant