MacOS Bash Command to Create (empty) Test Files for any JavaScript or TypeScript files in your project.

add-tests.sh

#!/bin/bash
find . \( -iname "*.js*" -or -iname "*.ts*" \) \
  -and \( ! -path "*/__mocks__/*" ! -name "*.test.*" ! -name "*.spec.*" \) \
  -exec sh -c \
  'b=$(basename $1);f=${b%.*};d=$(dirname $1);e=${b##*.}; mkdir -p $d/__tests__ && > $d/__tests__/$f.test.$e' \
  sh {} \;

Thanks @szepeviktor, but your version of the script doesn't run on my iMac within the terminal on VSCode.

I see.
Which part needs GNU find? -iname "*.[jt]s*" ??

What is the difference between using sh in my script and bash in yours?

In my script, I want all .[jt]x files not currently in __mocks__ folder and who are already not named a *.test.* or *.spec.*. I've updated to also exclude __tests__ folder and node_modules folder.

The result of find goes all the way through to the end.

I've updated it to the following:

find . -iname "*.[jt]s*" \
  -and \( \
    ! -path "*/__mocks__/*" \
    ! -path "*/node_modules/*" \
    ! -path "*/__tests__/*" \
    ! -name "*.test.*" \
    ! -name "*.spec.*" \
  \) \
-exec sh -c \
  'b=$(basename $1);f=${b%.*};d=$(dirname $1);e=${b##*.}; mkdir -p $d/__tests__ && > $d/__tests__/$f.test.$e' \
sh {} \;

What is the difference between using sh in my script and bash in yours?

bash starts Bash, sh depends on some settings.