You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
unit testing folder structure should reflect the source code
each unit tests should be focused on testing one thing and one thing only
verbose, over complicated tests should be replaced by simpler, easier to understand tests.
The text was updated successfully, but these errors were encountered:
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.
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:
The text was updated successfully, but these errors were encountered: