[ 
https://issues.apache.org/jira/browse/SUREFIRE-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071701#comment-17071701
 ] 

Simon Levermann commented on SUREFIRE-1766:
-------------------------------------------

testAddBadly[1] is not *quite* what I'm looking for.

I'm looking for something like testAddBadly[10,4] (3), similar to as it 
displayed in the IDE, that is the .toString() representation of the actual 
parameters passed to the test, as well as the invocation count. Is it 
acceptable to just pass that as the "test name" to the ReportEntry constructor?

Two Questions regarding contribution:

1) Do I just build my contribution against the master branch, or is there 
another branch that I should be targetting?

2) Is there a maven goal or similar (maybe a style guide that can be imported 
into IDEs) so I can format my code according to the maven coding standard? It's 
quite exotic as standards go with the spacing and the like.

> Surefire does not display TestNG data provider values on command line
> ---------------------------------------------------------------------
>
>                 Key: SUREFIRE-1766
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-1766
>             Project: Maven Surefire
>          Issue Type: Improvement
>          Components: TestNG support
>    Affects Versions: 3.0.0-M4
>         Environment: Maven 3.6.3
> Surefire 3.0.0-M4
> TestNG 7.1.0
>            Reporter: Simon Levermann
>            Priority: Minor
>         Attachments: testng.png
>
>
> When using Surefire's DataProvider annotation, TestNG also exposes the actual 
> parameters that were used for each invocation. These parameters are stored in 
> the testng-results.xml file, and as such, should be available for consumption.
> It looks like they end up in the report HTML files, but they are not shown 
> when running the tests on the command line.
> I've created a small POC repository at 
> [https://github.com/sonOfRa/testng-surefire-poc]. A simple "mvn test" 
> invocation should yield some succeeding and some failing tests. When looking 
> at the  generated HTML reports, they contain the full information. When 
> looking at the command line output, the exact problems are not visible.
> When running the tests in an IDE like IntelliJ IDEA, the parameters are shown 
> alongside the test name. I've attaced a screenshot of this for reference.
> SUREFIRE-382 may be related to  this issue.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to