Level 48
You could write a use case and see what is need to test.
I'm starting to work through the "Let's Build A Forum with Laravel and TDD" series but one thing I'm wondering (not sure if it's answered later on in the series) is how do you know what to test? I can think of so many different things to test, how do you decide what to actually write a test for?
Also, bonus, how do people calculate the "test coverage" of their packages?
Please or to participate in this conversation.