QA Tools

Overview

The code analysis can be split in phases :

• pyflakes : clean and small scanner, it raises major errors.
• pylint : well configured, it shows very small errors and problems. More work to do than pyflakes, more code quality.
• CloneDigger : very useful to stick to XP development, it points all clones and duplicates in the code.
• figleaf : code coverage scanner.

pyflakes : the first pass

• Pyflakes (DEB) -> bon départ (plus simple) avec pylint (plus complet)
•  http://www.divmod.org/trac/wiki/DivmodPyflakes

CloneDigger

• easy_install under Lucid Lynx
•  http://clonedigger.sourceforge.net/
•  http://clonedigger.sourceforge.net/clonedigger_europython2008.ppt

figleaf

•  http://darcs.idyll.org/~t/projects/figleaf/doc/
• installation:

  sudo easy_install http://darcs.idyll.org/~t/projects/figleaf-latest.tar.gz
  

• use :

  cd $DEVDIR
  figleaf /usr/sbin/licornd
  figleaf2html
  Web browser -> html/index.html
  

Unittest

•  http://docs.python.org/release/2.5.2/lib/module-unittest.html

Other tools

They are not used yet. Kept here for archival reasons only.

• coverage.py -> idem figleaf, moins riche (voir doc de figleaf pour comparaison)
  •  http://nedbatchelder.com/code/modules/rees-coverage.html
• Pyntch -> annote le code pour faire apparaître les types des variables. * http://www.unixuser.org/~euske/python/pyntch/index.html
• Pymetrics (DEB) -> implémente la recherche de complexité cyclomatique
  •  http://pymetrics.sourceforge.net/
  •  http://sourceforge.net/projects/pymetrics/
• pychecker -> plus simple que pylint
  •  http://pychecker.sourceforge.net/
• Python Clone Doctor -> même principe, a l'air plus gros.
  •  http://www.semanticdesigns.com/Products/Clone/PythonCloneDR.html
• Complexité cyclomatique (à étudier)
  •  http://www.traceback.org/2008/03/31/measuring-cyclomatic-complexity-of-python-code/