Automation Spec Testing w/CLI: Skip shaders, etc?

So let’s say I am wanting to run automation spec testing via CLI - something similar to this:

Each time, I get “14000 shaders left to compile…”

I don’t even see the editor for these tests; what are some commands to SKIP compiling certain things for CLI testing only?

PS: Any CLI-specific docs for automation spec testing? Seems like this doesn’t exist. Other forum members have been looking for such a doc, too. Since it was a few years later - figured I’d ask. Half of the -switch commands are buried/undoc’d, too (found a doc for cmd args somewhere, but not specific to testing).

1 Like