Tests doesnt work outside of libs and apps scope

Current Behavior

If you add a test file inside tools/generators directory, jest throws:

No tests found, exiting with code 1

Expected Behavior

Tests should work as expected

Steps to Reproduce

Create a test file in tools/generators/sum.spec.ts

describe('some test', async () => {
  it('test sum', function () {
    const num = 1 + 1
    expect(num).toBeGreaterThanOrEqual(2)
  })
})

Failure Logs

No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0

Environment

Node : 14.17.4 OS : darwin x64 yarn : 1.22.11

nx : Not Found @nrwl/angular : Not Found @nrwl/cli : 12.8.0 @nrwl/cypress : 12.8.0 @nrwl/devkit : 12.8.0 @nrwl/eslint-plugin-nx : 12.8.0 @nrwl/express : 12.8.0 @nrwl/jest : 12.8.0 @nrwl/linter : 12.8.0 @nrwl/nest : Not Found @nrwl/next : Not Found @nrwl/node : 12.8.0 @nrwl/nx-cloud : Not Found @nrwl/react : 12.8.0 @nrwl/schematics : Not Found @nrwl/tao : 12.8.0 @nrwl/web : 12.8.0 @nrwl/workspace : 12.8.0 @nrwl/storybook : 12.8.0 @nrwl/gatsby : Not Found typescript : 4.3.5

[jaqua]

@vsavkin I also created some scripts and generators in the tools directory. Of course I added all the needed unit tests for those scripts, but they won’t be tested by nx test or nx affected:test - although those files will have affect on the whole project, if the scripts have any bugs. I do not understand your suggestion to create a project. Do you mean an application or a library? And if yes, what kind of library?

[vsavkin]

Hi there.

We don’t encourage folks to run jest from the root and instead encourage them to use nx affected --target=test. The command then will only test the affected projects instead of all of them. I imagine you are running the jest command directly. You can do it but in this case you rerun all tests on all PRs.

What I would suggest instead is to create a project in workspace.json and set its root to tools/generators.

Does it make sense?