Optional support for line numbers #114
Description
Apologies for bringing up what might feel like a dead horse to you.
First off I want to say I have read the existing issues on this such as: #109
and the PR here: #110
Question
The question I have is about choice:
If adding the line numbers breaks some consumers would you consider a feature where we could optionally turn this on with documentation stating the risks? Ensuring the core functionality of the library (serving compliant JUnit XML) stays intact while allowing those who can to extend it to better suit ruby and rspec.
Why am I bringing this up?
- Someone has already proved it's possible to set this up with CircleCI:
- https://discuss.circleci.com/t/example-of-splitting-by-test-name-for-rspec-rails/51459/16
- I have not yet checked but this probably feasible on other CI's utilising JUnit XML.
- Will add a small amount of flexibility to the gem to give it a greater utility.
- I'm going to implement this for my own codebase. If I can contribute something of value back when I'm doing the work already I want to.
- This gem is listed in the CircleCI docs as the method to collect test data but the results do not allow for proper parallel test execution.