Open sofer opened 9 years ago
If we delay until week 3, we'll get the situation we did in FAC 4 where no one did TDD at all because they started it too late and had a taste for non-TDD development already.
@sofer Created a FAC7 label in the repo so we can begin to prioritise (it's only week 2, this is going to get out of hand otherwise!)
TDD is a tricky one because on one hand you have that in order to write tests before writing the program, you need quite a good idea of the actual functions you'll be using etc; but by the time you can conceptualise and break down exactly what functions you'll need, you've become a bit set in your ways about non-TDD development.
I think earlier better though with TDD (as someone who is struggling to incorporate it into my workflow).
Could this be a pre-req? https://www.codecademy.com/courses/testing-your-code/0/1
@mantagen Good call on making TDD a pre-req, I'd fully support that :+1:
We should choose what we add to the pre-reqs depending on the outcome of this issue (i.e. if we stick with TDD, then https://github.com/dwyl/learn-tdd is aimed at that).
Could we do a TDD repo as a prerequisite to test not client-side code, but some simple js functions?
Re-frame the QUnit repo as a "testing tools" tutorial? Delay testing until Week 3?