Difference between revisions of "CRV2 CodeReviewAgile"

From OWASP
Jump to: navigation, search
m
Line 2: Line 2:
  
  
=Some definitions about Agile=
+
==Some definitions about Agile==
  
 
...
 
...
Line 18: Line 18:
 
==LifeCycle==
 
==LifeCycle==
 
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.
 
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.
  
  

Revision as of 18:58, 19 June 2013

Charly, remember that it's "code review guide", not "testing guide"


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

Peer Programming

This technique consists of ...

Peer Review

This one is enforced by the usage of tools like .... that ask another user for a code review before commiting to the versioning system.

LifeCycle

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

continuous integration

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

....