User Tools
teaching:reverse:2016:basesdecodes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
teaching:reverse:2016:basesdecodes [2017/02/16 17:06] blay |
teaching:reverse:2016:basesdecodes [2017/02/16 18:17] blay |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| * II. What are the impacts of Test-Driven Development on code quality, code maintainability and test coverage ? | * II. What are the impacts of Test-Driven Development on code quality, code maintainability and test coverage ? | ||
| * https://mireillebf.gitbooks.io/uca-students-on-software-maintenance/content/what-are-the-impacts-of-test-driven-development-on-code-quality-code-maintainability-and-test-coverage-.html | * https://mireillebf.gitbooks.io/uca-students-on-software-maintenance/content/what-are-the-impacts-of-test-driven-development-on-code-quality-code-maintainability-and-test-coverage-.html | ||
| + | * Le projet reposait plutôt sur de la configuration d'environnement. Excepté pour CodeMaat dont le script python est mis en lien dans sa partie. Ce script permet de récupérer toutes les données liées aux métriques choisies. | ||
| + | * Un exemple de configuration du plugin de JaCoCo (Java Code Coverage) a aussi été présenté dans le rapport. Ce plugin était rajouté dans le fichier de configuration maven (pom.xml) ou graddle. Sonar aussi, nous avions produit un fichier de configuration standard qu'il fallait adapter selon le langage ou la structure du projet. | ||
| * III. What is the relation between adding functionality, bug fixing, and code quality | * III. What is the relation between adding functionality, bug fixing, and code quality | ||
teaching/reverse/2016/basesdecodes.txt · Last modified: 2017/02/16 18:20 by blay
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
