In Jest 30, the CLI parameter testPathPattern was changed to testPathPatterns. See here.
The JestTaskOptions structure in the latest version still uses the old name. This is making it difficult to filter tests on a project using Jest 30.
I'm not familiar with the Just standard versioning strategies for tasks, so I don't have a pull request to provide with this issue. The new parameter allows for one or more pattern matching strings, separated by spaces, so it's not as easy to parse.
No known work-around at this point for filtering tests using testPathPatterns in Jest30.