In a repository pattern I've been following for a while (...example...), I've always had Add, Delete, etc. methods which use a "new" DbSet (e.g., ...DbContext.Set<T>.Update(entity).... In testing, this seems to, thankfully, always return the same DbSet ob...