Nice article, easy to read, suitable for all programming languages. I work in a similar way, and I usually select some boundary tests. I like to draw clear boundaries regarding what the system under test will work with and what it will not.
Thanks! I am actually curious to see how those boundary tests look like. Can you share an example?
Mikalai Kardash "It's nothing fancy. I wrote a bit about that in my blog post easytdd.dev/easy-way-to-start-tdd. It's not clearly distinguished in the text as a section, but with 'find-in-page' functionality, you can search for 'ThrowsExceptionWhenExpressionIsInvalid' or 'CallbackThrowsArgumentExceptionWhenRequestIsNotValid' tests. It's more of a thinking strategy rather than a very valuable test per se.
This is a great write-up, Mikalai. Thank you for putting it so clearly. If you think the article's url will be stable, I'd love to link to it from my blog post.
Kazys Račkauskas
Tdd
Nice article, easy to read, suitable for all programming languages. I work in a similar way, and I usually select some boundary tests. I like to draw clear boundaries regarding what the system under test will work with and what it will not.