I don’t know if this is pure or orthodox but: Start with one or two high-level interfaces that should meet the functional requirements. It defines the informat

I don’t know if this is pure or orthodox but: Start with one or two high-level interfaces that should meet the functional requirements. It defines the information you need to send in and/or receive. Non functional. Then capture some basic behavior of one of the methods/properties in the tests, then implement the solution. Then start capturing edge-cases the same way. If you’re asking yourself “how” or “should” I test this, then you’re doing great. Apply SOLID principles to separate meaningful concerns into separate classes; and iterate there. Take my viewpoint with a large grain of salt.