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
Currently, many of the Gardener tests use custom, promitive mocking mechanism. An example of that can be found in ExecuteReadyRequestsUseCase.spec.ts . They look like this: const fetchDataUseCase = () => ({ fetchData: () => Promise.resolve('fetchedData'), });
In scope of this task, refactor entire gardener-server codebase to use some standard mock mechanism instead. A specific technnique to be used is left to be researched but this looks promising: https://jestjs.io/docs/en/es6-class-mocks#automatic-mock .
The text was updated successfully, but these errors were encountered:
Currently, many of the Gardener tests use custom, promitive mocking mechanism. An example of that can be found in
ExecuteReadyRequestsUseCase.spec.ts
. They look like this:const fetchDataUseCase = () => ({ fetchData: () => Promise.resolve('fetchedData'), });
In scope of this task, refactor entire
gardener-server
codebase to use some standard mock mechanism instead. A specific technnique to be used is left to be researched but this looks promising: https://jestjs.io/docs/en/es6-class-mocks#automatic-mock .The text was updated successfully, but these errors were encountered: