Just read this now and coincidentally I told my team today that we need to do better at writing test code so we can improve our our own lives. Plus we'd become a more productive team, and not work as hard to read, write, and change code including tests. And, of course, we would avoid some of the defects that slip through.
Just read this now and coincidentally I told my team today that we need to do better at writing test code so we can improve our our own lives. Plus we'd become a more productive team, and not work as hard to read, write, and change code including tests. And, of course, we would avoid some of the defects that slip through.
Recommended a BDD-style approach. My main points about using BDD:
1) We verify and refine requirements up front.
2) We end up with a better design (because we approach it from the outside in).
3) We get more readable tests because we focus on the test cases first.
Pull-based thinking...start at the end and work your way backwards.
Just read this now and coincidentally I told my team today that we need to do better at writing test code so we can improve our our own lives. Plus we'd become a more productive team, and not work as hard to read, write, and change code including tests. And, of course, we would avoid some of the defects that slip through.
Recommended a BDD-style approach. My main points about using BDD:
1) We verify and refine requirements up front.
2) We end up with a better design (because we approach it from the outside in).
3) We get more readable tests because we focus on the test cases first.
Pull-based thinking...start at the end and work your way backwards.