Charly, remember that it's "code review guide", not "testing guide"
- 1 Some definitions about Agile
- 2 Peer Programming
- 3 Peer Review
- 4 LifeCycle
- 5 Clean Code and "Smells"
- 6 The role of testing
- 7 continuous integration
- 8 The role of automatic static code analysis in the Agile Methodologies
- 9 Test Driven Development
- 10 Behavior Driven Development
- 11 Domaing Driven Design
Some definitions about Agile
Agile Development is well suited for code review, as two of its best practices are "peer programming" and "peer review". AD incorporates code review in itself
This technique consists of ...
This one is enforced by the usage of tools like .... that ask another user for a code review before commiting to the versioning system.
AD tries to keep the code review as near as possible to the development phase, there is no such thing as develop, test, code review cycle.
If you are going to review an Agile Team project code, the best thing that you can do is give this guide to that Team as early as possible and most of your work will be done for you.
Clean Code and "Smells"
The role of testing
It is so fundamental, that the xDD pervades Agile, test first, test earlier
it can trigger static code analysis
The role of automatic static code analysis in the Agile Methodologies
Test Driven Development
It aims at code simplicity due to the need of making it testeable
Behavior Driven Development
Domaing Driven Design