Allow test files to have different extensions with transform

[ldesplat]

1. Since we specify transform, our tests themselves could be transformed.
2. Document a pitfall, which is to not transform too many files so the user has to check for that in transform method.

[geek]

I think this can be ===

[gergoerdosi]

This will create a wrong regex ( .(js|)$ ) if the transform module exports an empty array. Also, the dot should be escaped, below and above too.

[ldesplat]

Thank you so much @gergoerdosi for spotting those issues.

I have fixed the code review issues and file extensions can now include some crazy stuff :). Tested a whole bunch of special characters on Mac, quite interesting!

[geek]

@ldesplat do we need any new tests for any of the edge cases you were considering with this change?

[ldesplat]

don't merge

[ldesplat]

Ok, I am sorry. All should be well now.

Thanks for telling me to add tests.
There was a bug where applying transforms with the no code coverage path was different than the coverage path. They are now using the exact same code and it is consistent behavior. This is covered in the 2 new tests.

I had to resort to way too many PRs to add this feature in. Next time I'll hold on a bit longer no matter my enthusiasm! Thanks for all your support.

[AdriVanHoudt]

@ldesplat thanks for all the effort to add this feature!

[lock]

This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.