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

Updates to naming conventions and default prefix #96

Open
mmilbrath opened this issue Jul 10, 2016 · 0 comments
Open

Updates to naming conventions and default prefix #96

mmilbrath opened this issue Jul 10, 2016 · 0 comments

Comments

@mmilbrath
Copy link

Would it be feasible to also remove parenthesis from browser name to make easier to work with? The function writeXmlForBrowser currently replaces spaces with underscores and the default parenthesis in the name make it more difficult to work with on command line since they need to be escaped when copying, etc.

Example:
surefire-reports/TESTS-Chrome_51.0.2704_(Windows_10_0.0.0).xml

In addition would it possible to make an additional parameter to override the default prefix 'TESTS'. The default conventions for java surefire plugins is to use a prefix of 'TEST' (singular) and we would like to get the naming more consistent so just a bit easier to match on patterns when using the JUNIT files for other workflows.

Example
/surefire-reports/junitreports/TEST-com.mycompany.test.server.service.echo.EchoServiceTest.xml

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

No branches or pull requests

1 participant