Testing public/internal/private methods about xcodeserversdk HOT 8 CLOSED

Yes. I'm even tempted to make everything private and then make what needs to be internal and public, so that we have a minimal public interface. Can you use @testable on private methods as well? Or is it just for internal?

from xcodeserversdk.

Just for internals... 😭
I even started this twitter conversation once.

from xcodeserversdk.

Ok, so let's do this: keep indirectly tested methods as private and directly tested ones as internal or public. In a way treat internal and public as things you'd put in a header file. But, always default to internal and only make it public iff you have a usecase outside of the current module.

And we will try to test all internal and public methods. So this task is mainly about removing the public modifier to make it internal again. Does that make sense?

from xcodeserversdk.

Yes sir, I think that's the right way! Now, Beats1 and get back to work 😉

from xcodeserversdk.

Haha same here. Loving the London style that's on right now.

from xcodeserversdk.

Oh man... Wish I'm in London right now 🇬🇧 Love this city so much 😻

from xcodeserversdk.

It's fucking boiling here right now though. 😓

from xcodeserversdk.

Even though... 😆

from xcodeserversdk.