What defines a "Valid Jest Workspace"

[airtonix]

vscode-jest Setup Tool

[info] Setup Tool Guide: https://github.com/jest-community/vscode-jest/blob/master/setup-wizard.md

=== starting monorepo task  ===


Validating 11 workspaces:
"pkgs/content" is NOT a valid jest workspace
"apps/web-with-remix" is NOT a valid jest workspace
"apps/with-remix-test" is NOT a valid jest workspace
"pkgs/core" is NOT a valid jest workspace
"pkgs/core/remark-nomnoml" is NOT a valid jest workspace
"pkgs/core/extract-props" is NOT a valid jest workspace
"pkgs/ui-web-components" is NOT a valid jest workspace
"pkgs/ui-web-blog-components" is NOT a valid jest workspace
"pkgs/ui-web-uikit" is NOT a valid jest workspace
"github" is NOT a valid jest workspace
"repo" is a valid jest workspace 

Validation Result: valid: 1, invalid: 10

Excluding 10 workspaces via "jest.disabledWorkspaceFolders": [pkgs/content, apps/web-with-remix, apps/with-remix-test, pkgs/core, pkgs/core/remark-nomnoml, pkgs/core/extract-props, pkgs/ui-web-components, pkgs/ui-web-blog-components, pkgs/ui-web-uikit, github]

Updating setting "jest.disabledWorkspaceFolders" in vscode workspace 
All updates saved successfully

[info] Please review and adjust config if needed: "/mnt/Store/Projects/Mine/Github/zenobi.us/zenobi.us.code-workspace"
Need more help? Please checkout FAQ: https://github.com/jest-community/vscode-jest/blob/master/setup-wizard.md#faq

=== monorepo task completed with status "success" ===


setup-tool exit with status "success"

I feel like the linked documentation isn't mouth-breather friendly. I can say this with great authority, what with being the preeminent mouth-breather; I would suggest we lower the bar to accommodate my peasant brain.

So the question someone will have is:

What really makes a workspace a "valid jest workspace"?

what is it and can we get these mysterious failed conditions that vscode considers printed out in the setup tool?

"pkgs/content" is NOT a valid jest workspace
  > no tests found
"apps/web-with-remix" is NOT a valid jest workspace
  > threw error while resolving config "rootdir not resolved"
"apps/with-remix-test" is NOT a valid jest workspace
  > something? 
"pkgs/core" is NOT a valid jest workspace
  > no tests found
"pkgs/core/remark-nomnoml" is NOT a valid jest workspace
  > no tests found
"pkgs/core/extract-props" is NOT a valid jest workspace
  > no tests found
"pkgs/ui-web-components" is NOT a valid jest workspace
  > etc
"pkgs/ui-web-blog-components" is NOT a valid jest workspace
"pkgs/ui-web-uikit" is NOT a valid jest workspace
"github" is NOT a valid jest workspace

my pkgs/content actually has a valid jest setup but no tests:

zenobi.us on git feat/web-with-remix [$x!?] via .NET via nodejs v20.12.1 
x just app content test                                          

> nx run content:test

No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In /mnt/Store/Projects/Mine/Github/zenobi.us/pkgs/content
  6 files checked.
  testMatch: **/?(*.)+(spec|test).[jt]s?(x) - 0 matches
  testPathIgnorePatterns: /node_modules/ - 6 matches
  testRegex:  - 0 matches
Pattern:  - 0 matches


 >  NX   Ran target test for project content (956ms)
 
    ✖    1/1 failed
    ✔    0/1 succeeded [0 read from cache]
 
error: Recipe `app` failed on line 26 with exit code 1

so even after running the test again to allow no tests, the monorepo setup tool still considers this package an invalid jest workspace.

zenobi.us on git feat/web-with-remix [$x!?] via .NET via nodejs v20.12.1 took 2s 
> just app content test

> nx run content:test

No tests found, exiting with code 0

 ————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Successfully ran target test for project content (849ms)