The title is fairly self explanatory.
To elaborate: I'm currently updating a suite of unit tests for an application which makes heavy use of Entity Framework. We connect to this via a classic repository interface so it can be mocked out.
We're not doing test first (that's a whole different argument, which I don't want this question to degenerate into). Rather a "code a bit, test a bit" sort of approach. So we're not backfilling a whole application with tests, either.
I appreciate that a whole suite of tests for such an application is likely to require a very complex repository mock. However, I just created a new test class and the very first test required a mock repository with about 5 mocked out repository get/save functions.
It was a fairly simple function that was being tested. The range of mock classes were needed because of operations carried out in the class constructor and suchlike.
Having done so it struck me that that hardly looked like a unit. And that it might be a sign my code was too interdependent. So: is creating a single test that demands a complex mock often a sign of poor architecture?