Closed Noriller closed 1 year ago
We've created a sample repo, but unfortunately, we were unable to reproduce the issue there. Could you please try the repo and see if you can reproduce the issue?
Please take note that we had to modify your config in order to resolve the ambiguity between the files
and tests
patterns.
[Info] Started Wallaby.js Core v1.0.1423
[Info] Wallaby App (realtime reports) is available at: http://localhost:51245
[Error] File/pattern src/Issue.test.js is specified in the files list but also found in the tests list: **/*.test.js.
[Error] If it's a test, make sure to exclude it from the files list, for example by adding { pattern: '**/*.test.js', ignore: true } to the files list.
[Error] If it's not a test, remove it from the tests list.
[Error] No files with tests found, check your tests list patterns.
[Info] Can't determine tests to run for the change.
[Info] To run all tests when can not determine tests to run, use `runAllTestsWhenNoAffectedTests: true` configuration option.
Same thing.
But one interesting thing is the wallaby.js
.
My current one is as follows:
module.exports = () => ({
name: 'React',
autoDetect: true,
workers: {
initial: 6,
regular: 4,
},
delays: {
// run: 1500
},
ignoreFileLoadingDependencyTracking: true,
// files: [
// 'src/**/*.js',
// ],
// tests: [
// '**/*.test.js',
// '!node_modules/**/*',
// ],
runMode: 'onsave',
maxLogEntrySize: 999999,
});
Did the commented out configs were actually applied? (In any case, both and even deleting the file had the same effect)
Sorry, I hadn't noticed that files
and tests
were commented out in the original config. Ignore them. How do you reproduce the issue in the sample repo? I've tried to simply start Wallaby and change the file, everything works perfectly well for me(natively on Windows and in WSL).
I can see that, I opened it on my personal computer, this one with Ubuntu and it worked perfectly fine.
I'll try checking some things on the other one and maybe I can find out something.
So, I've tried again at work and it started working (the example).
Last time I tried the example I couldn't make it work with our internal mirror of npm, then I tried bypassing and using the npm mirror.
I think it's related, but not sure why or how.
Does your internal mirror of npm
limit the versions of dependencies that are available? If so, this may be the cause of your problem if you are using old or incompatible versions of dependencies.
Next time you have the problem, you could send us your package-lock.json
or yarn.lock
and that would help us work out why. Also, next time it occurs, try cloning to a fresh directory and install the dependencies by bypassing the internal mirror. If that works, you can diff the files to determine what's different, which should help identify the cause.
I'm going to close this issue for now because I don't think any further action is required from us. If/when you get the problem again, please either reply to this issue (and we can re-open it) or create a new issue.
If you work out the root cause after examining your dependencies when you have the problem again, please let us know what the cause is; we may be able to check for it to help others in the future.
Issue description or question
It's inconsistent, on some places I tried nesting it deeply (like 5+ levels of describe and then a test) and it worked, but on some files it just doesnt show any action. Control click to navigate to tests take me to the beforeEach of the describe block the test is in, or sometimes above in the tree.
I then tried right click on the test, but it shows "Line is not covered or covered not by tests" but in the beforeEach above it takes me to a test.
I couldn't really reproduce the "line not covered", but for the actions and navigate. Going to the
output
tab and control click on the test is taking me to the "import userEvent" line. Errors are also showing only up there.Image of how the error is showing:
Wallaby diagnostics report