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
A first PR: #2183 aims at mocking the Fetch in the unit tests using the package sinon.
It was done in the optics to get the units test independent to the network and to know when a test is failing because of it.
But to go further, and implement 'better' units test we should use sinon (or something else) to mock everything that might be use to test a specific fonctionality.
For instance to test dataSourceProvider we should mock the layer that are needed instead of mocking the fethc that weill be use to instanciate that same layer.
The text was updated successfully, but these errors were encountered:
ftoromanoff
changed the title
[Improvment] Unit Tests - mocking and reel unit test
[Improvment] Unit Tests - mocking and real unit tests
Mar 13, 2024
ftoromanoff
changed the title
[Improvment] Unit Tests - mocking and real unit tests
[Improvment] Unit Tests - mocking and implementation of true unit tests
Mar 13, 2024
A first PR: #2183 aims at mocking the Fetch in the unit tests using the package sinon.
It was done in the optics to get the units test independent to the network and to know when a test is failing because of it.
But to go further, and implement 'better' units test we should use sinon (or something else) to mock everything that might be use to test a specific fonctionality.
For instance to test dataSourceProvider we should mock the layer that are needed instead of mocking the fethc that weill be use to instanciate that same layer.
The text was updated successfully, but these errors were encountered: