I'm not too sure how to classify this, but noticed that there may be problems with Jest setups who also want to keep private functions/files &c. out of the documentation. It's more of a fix for future people or possible thing to look for if accepting "jest" as a type.

The "problem" is that one of the ways that Jest looks for tests by default is in the directory __tests__. I couldn't see it documented anywhere, but a solution (other than creating a test of type "jest" or checking if the kind is testFile) is to disable autoPrivate, so the directory isn't set to private and then removed here.

Maybe this will be a dead issue, but I thought someone else having problems with Jest showing in their documents and using the structure of __tests__ would find find this useful and it would save them time investigating the issue.