smcenlly
commented
3 years ago I can see from your diagnostics report that you are explicitly setting the files and tests sections for your project:
wallaby.js configuration
module.exports = function (wallaby) {
return {
autoDetect: true,
files: [
'libs/shared/src/**/*.ts',
'apps/carrier/src/**/*.ts',
'apps/customer/src/**/*.ts',
{ pattern: 'libs/shared/src/**/*spec.ts', ignore: true },
{ pattern: 'apps/carrier/src/**/*spec.ts', ignore: true },
{ pattern: 'apps/customer/src/**/*spec.ts', ignore: true },
],
tests: [
'libs/shared/src/**/*spec.ts',
'apps/carrier/src/**/*spec.ts',
'apps/customer/src/**/*spec.ts',
],
};
};Is there a reason for you doing this? This may be the cause of your problem. For projects that use automatic configuration, your files and tests properties will be automatically set based on your project’s configuration. There are two ways to configure different or additional files and tests when using automatic configuration:
Modify automatic configuration files and/or tests You may modify the files and/or tests properties that are automatically set by Wallaby’s automatic configuration by creating a files or tests property with an object containing an override function:
module.exports = () => ({
autoDetect: true,
// modify `files` automatic configuration settings
files: {
override: (filePatterns) => {
// TODO: modify `filePatterns` array as required
return filePatterns;
}
},
// modify `tests` automatic configuration settings
tests: {
override: (testPatterns) => {
// TODO: modify `testPatterns` array as required
return testPatterns;
}
}
});Replace automatic configuration files and/or tests You may force Wallaby to completely ignore the files and/or tests properties that are automatically set by Wallaby’s automatic configuration by creating a files or tests property with an array of patterns.
module.exports = () => ({
autoDetect: true,
// modify `files` automatic configuration settings
files: [
"src/**/*.js",
],
// modify `tests` automatic configuration settings
tests: [
"test/**/*.spec.js",
]
});In your case, you are completely replacing the configuration which may be missing some files that Wallaby needs to successfully run your tests.
Please try removing the files and tests sections of your configuration to see if that fixes the problem. If you still need overrides, you may also try to modify the configuration instead of replacing it.
sdrowe
NikGovorov
Issue description or question
Wallaby diagnostics report