You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this problem when tried to run my project on Jenkins.
Unfortunately, i quickly realised that it cannot find tests.
I tried different combinations and was able to reproduce the problem locally. It's quiet easy. Just re-name project folder from "project" to "project (master)".
First, i though that the reason is "space" but after some debugging i found that path is used first to locate files using "contains" and then, later, regular expression is created from the path specified in "testPathDirs".
Unfortunately, it doesn't escape brackets and it lead's to "no tests found" case.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
I found this problem when tried to run my project on Jenkins.
Unfortunately, i quickly realised that it cannot find tests.
I tried different combinations and was able to reproduce the problem locally. It's quiet easy. Just re-name project folder from "project" to "project (master)".
First, i though that the reason is "space" but after some debugging i found that path is used first to locate files using "contains" and then, later, regular expression is created from the path specified in "testPathDirs".
Unfortunately, it doesn't escape brackets and it lead's to "no tests found" case.
Here is my config:
{
testPathDirs: ['src/test/javascript']
testRegex: '/unit/.*-spec.(js)$'
verbose: true
}
The text was updated successfully, but these errors were encountered: