I have a class that has the responsibility of importing contracts from a CSV to database.
The class itself has only one public method that starts the import and the
In theory, your private methods are being used ultimately by one of the public methods, or else they're not used at all. So typically you setup your tests to call the public methods with the necessary context so that it hits your private methods.
The unit tests are primarily testing the compilation unit (i.e. the class). You can unit test methods directly but then they have to be public, which goes against having a nice clean API.
So test your public method enough to hit all the private methods. Private methods are internal mechanics of the class, they don't need to be tested directly.