Dynamic test cases raises 'Test file path not found' log message

[mesche]

Currently, path-finder raises an error log message, when creating dynamic test cases with forEach.

['a', 'b', 'c']
.forEach((item: any) => {
it('testcase_' +item, () => {
console.log(item);
});
});

[fadc80]

Yeap! This is a limitation of the approach used to detect test file paths.

Karma doesn't report them as part of test metadata, but this information is required by sonarqube.

Actually, pathFinder tries to look for test file paths using regular expressions based on "describe" and "it" comments.

In your example you generate tests dynamically. Consequently, pathFinder is trying to find test files containing:

• testcase_a
• testcase_b
• testcase_c

However, there aren't any test files containing this comments.

I think a solution would require changing the approach to something like suggested here.

[mesche]

Thank you for your feedback. I understand the problem, but other libraries like 'karma-sonarqube-unit-reporter' have no problem with that. I like your library and would like to use it furthermore. is it planned to fix/change the behavior?

[fadc80]

Sure. I'll try to look at this during the next weekend!

[fadc80]

I tried very hard to solve this but without success. As I mentioned before, I decided to change the approach based on what is suggested here. However, it didn't work as I expected. Check my comments there.

@mesche Are you sure 'karma-sonarqube-unit-reporter' has no problem with this? I didn't test it, but I was unable to see reading its code how this case is handled. It seems to be using regular expressions too.

[mesche]

@fadc80 Yes, I am sure

[fadc80]

@all-contributors please add @mesche as a contributor for bug.

[allcontributors]

@fadc80

I've put up a pull request to add @mesche! 🎉