Repository navigation
Implement Parallel Unit testing #9467
Description
Activity
Thanks for opening this issue!
- 🎉 We are excited about your ideas for improvement!
Regarding parallel execution, it seems that jasmine 5 supports this, so there should be no need to switch to a different framework.
Related:
I think it would be worth having a key distinction though as the current test suite would be hard to parallelise due to the e2e nature of it.
IMO, a new folder of unit tests where we test individual methods of code (with jasmine) would be the deliverable here
I think that really depends on how parallel execution is implemented in jasmine. Parse Server and MongoDB could be parallelized as well, I think it wouldn't even be necessary to spawn up child processes, they could just run on different ports and the tests could cycle between them.
My suggestion is to re-look at how we do testing - whilst we can do e2e parallel testing with jasmine, I would suggest starting fresh and evaluating the best e2e framework to make it clear the difference between the e2e and unit tests.
New Feature / Enhancement Checklist
Current Limitation
Our current testing approach is more or less e2e testing. A full server and database is built in memory.
This makes test comprehensive, but slow. For a simple test like asserting that cloud functions register, there's no reason why this needs to run across all the different environments.
Feature / Enhancement Description
Implement a seperate folder of unit tests. This could still utilise Jasmine, but the focus being on mocking all external dependencies to the test. This means that the unit tests can be ran in parallel, reducing our build times. Will also make it easier to debug - theoretically, one line that breaks tests should only break one unit test.
Example Use Case
Alternatives / Workarounds
3rd Party References
Would also suggest testing standards uplifts: