Description
Command
test
Description
We're in the process of trying to move away from Jest through a non-Angular maintained library to the Vitest managed process, but our project is encountering a lot of errors (including needing 16GB of memory to run tests).
We'd like the ability to run the tests against single unit tests files instead of the whole project so we can narrow down incompatibilities with the testing infrastructure we're coming from and to try and squash the ridiculous memory usage we're experiencing.
Describe the solution you'd like
Allow for something similar to the following:
ng test src/app/app.component.spec.ts
Allow adding a unit test file to the ng test script to just run that specific test.
Describe alternatives you've considered
We've considered going back to our Jest runner, as that allows us to specify single test files to run the testing apparatus on.