stubs | simple modern and intuitive unit testing framework | Unit Testing library

I try to use library cv2 for changing picture. In mode debug I found out that problem in function cv2.namedWindow:

I use kms.decrypt() method from boto3 package. For typing support I use the boto3-stubs package.

The decrypt method has attribute EncryptionAlgorithm, which is typed as

I have an input file

I'm trying to mock bcrypt hash method implementation, but get following error:

I have a test that fails due to me being unable to successfully stub the get method of the Controller:

I am trying to mock this function below by using Mockk library.

I'm writing some code for a class project that sends jobs to a dataproc cluster in GCP. I recently ran into an odd error and I'm having trouble wrapping my head around it. The error is as follows:

I've been working on a project which so far has just involved building some cloud infrastructure, and now I'm trying to add a CLI to simplify running some AWS Lambdas. Unfortunately both the sdist and wheel packages built using poetry build don't seem to include the dependencies, so I have to manually pip install all of them to run the command. Basically I

1. run poetry build in the project,
2. cd "$(mktemp --directory)",
3. python -m venv .venv,
4. . .venv/bin/activate,
5. pip install /path/to/result/of/poetry/build/above, and then
6. run the new .venv/bin/ executable.

At this point the executable fails, because pip did not install any of the package dependencies. If I pip show PACKAGE the Requires line is empty.

The Poetry manual doesn't seem to specify how to link dependencies to the built package, so what do I have to do instead?

I am using some optional dependencies, could that be interfering with the build process? To be clear, even non-optional dependencies do not show up in the package dependencies.

pyproject.toml:

REMARK :

• I use term mocking as a general term meaning all kind of test substitutes inluding spies, fakes, mock, stubs and all the rest.
• In writing my question I have only speak of "use cases" in clean architecture, but my question also concerns "Domain Services" in DDD.

Let's go :

I am currently trying to implement DDD and Clean Architecture principles in a new project. However, it's been 1 week that I have been stuck on ---> How to write my unit test for my use case

In Clean Architecture, when we create a use case (or a Domain service in DDD), it will depend in most cases on a certain number of entities + the rest (repository, api ...)

To write my unit test of my use case, I start with:

- Mock "the rest" of dependencies that interact with the outside (repositories, API ...)

- But next, what should I do with the entities dependencies in my unit test?

Here are the solutions I thought of :

• Solution 1: I'm injecting fake entities

- However, through my reading about unit test best practices, I understand that we should avoid creating mocks as much as possible because they are "Code Smells" and a good design should make it possible to do without them.

- Indeed, mocking my entities implies that I weaken my test. The test will be tightly coupled to my mocked entities.

- In addition, recreating the structure of my entities seems meaningless to me ...

* If my use case uses multiple entity methods: then I should have to recreate the return value of each of those methods.

* If the structure of my entities is complex I end up with complicated fakes to write, therefore my test loses a lot of reliability and there is a more chance that my fake is wrong, rather than my original entity)

* Even worse, if I use a factory, then I will have to make a fake of the factory -> and that fake will have to build a fake entity ...

• Solution 2: I don't mock entities.

- On the other hand, if I do not mock my entities, then I take the way in my opinion into integration tests: testing the interactions between the different entities ...

- Also as specified by some mocking supporters: If I don't mock my dependencies, then even if my tested unit is valid, the test will fail if my dependency causes a bug. This will cause a false alarm signal on my test ...

• Solution 3: Refactoring the production code

- By reading several articles some offer solutions to limit the coupling (Isolate the side effects from the rest of the logic, Isolate the logic from I/O, Use pure functions, Dependency injections, ...) But even by applying all this, a use case will irremediably need these entities to work ... Therefore it is not a solution.

But then how to do? Am I missing something?
How to do a GOOD unit test on a use case (or a service domain in DDD)? : how to manage the entities in a unit test in which the tested unit has entity depenencies ?

To illustrate my question, and to better understand your answers, here is a fictitious example of the problem:

Imagine that I have the following entity: