as "mockist" tdd practitioner, should i ridicule methods same category slight underneath test?

after reading martin fowler's , i've detected i've practicing tdd "mockist" fashion.

but i'm wondering even mockist tdd take scathing too far.

here's an updated instance python-style pseudo-code:

def sync_path(self):
    self.confirm_or_create_connection():
        self.sync(self.dirpath)

the confirm_or_create_connection() slight creates tie server.

i tested slight identical twin tests, both ridicule confirm_or_create_connection() sync() (even nonetheless they're both methods same class). exam ridicule confirm_or_create_connection() advantage loyal exam confirms sync() called, ridicule confirm_or_create_connection() advantage fake exam confirms sync() called.

is reasonable? should i ridicule objects confirm_or_create_connection() sync() call? (i have tests both methods already this.)

please don't answer doubt explaining i should practicing "classical" tdd instead. that's an answer another question: