Move team to TDD
Bug #622809 reported by
Duncan McGreggor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Open Input Framework |
Fix Released
|
High
|
Duncan McGreggor |
Bug Description
Depends upon:
* bug #622807
We need to embrace TDD in our MT development efforts. Once we've identified a C unit testing framework (bug #622807), we need to start employing TDD best practices. This includes training those who aren't familiar with the approach and then making sure that we all do it. Part of the review process needs to include checks:
* for any new code added, tests are added
* for any code changed, the tests are changed (if applicable)
* for any bugs identified, tests are added
* for every review performed, each reviewer runs the full test suite to make sure everything still passes
Changed in utouch: | |
assignee: | nobody → Duncan McGreggor (oubiwann) |
importance: | Undecided → High |
Changed in utouch: | |
status: | New → In Progress |
milestone: | natty-alpha-5 → none |
Changed in utouch: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Projects converted to TDD:
* GEIS
Projects pending TDD:
* grail - bug #674954
- Henrick has set up infrastructure for testing the stack now
- Chase has started work on a framework for unit testing the stack
* GTK touch/libgrope doesn't have unit tests yet - bug #674950
* no tests for - bug #674949