Testing Challenges with `Effect.Service` and Dependency Injection

I noticed that

Effect.Service

Effect.Service

makes it arguably difficult to write tests for business logic in the application layer, specifically when I add

Repository.Default

Repository.Default

to the

dependencies

dependencies

of my service. I can easily provide

Service.Default

Service.Default

to the test program, but it automatically uses the default implementation of the repository due my explicit entry in the

dependencies

dependencies

array: https://effect.website/play#da29dce1e38a

Does this imply I have to stop passing dependencies and wire them up manually for my runtime in order to be able to test them?

Effect Community•10mo ago

Near

Testing Challenges with `Effect.Service` and Dependency Injection

I noticed that

Effect.Service

Effect.Service

makes it arguably difficult to write tests for business logic in the application layer, specifically when I add

Repository.Default

Repository.Default

to the

dependencies

dependencies

of my service. I can easily provide

Service.Default

Service.Default

to the test program, but it automatically uses the default implementation of the repository due my explicit entry in the

dependencies

dependencies

array: https://effect.website/play#da29dce1e38a

Does this imply I have to stop passing dependencies and wire them up manually for my runtime in order to be able to test them?

Testing Challenges with `Effect.Service` and Dependency Injection

Similar Threads

Testing Challenges with `Effect.Service` and Dependency Injection

Similar Threads

Similar Threads

Similar Threads