Content deleted Content added
DavidMCEddy (talk | contribs) m add a reference ~~~~ |
DavidMCEddy (talk | contribs) m add a reference ~~~~ |
||
Line 18:
| title = Creating R Packages: A Tutorial
| url =http://cran.r-project.org/doc/contrib/Leisch-CreatingPackages.pdf | }}
</ref>
</ref> checks for errors of various types. Examples included in the documentation files are tested and produce error messages if they fail. This can be used as a primitive form of [[unit testing]]; more formal unit tests and [[regression testing]] can be included in a "tests" subdirectory.▼
<ref> {{cite presentation
| last1 = Graves | first1 = Spencer B. | last2 = Dorai-Raj | first2=Sundar
| title = Creating R Packages, Using CRAN, R-Forge, And Local R Archive Networks And Subversion (SVN) Repositories
| url =http://cran.r-project.org/doc/contrib/Graves+DoraiRaj-RPackageDevelopment.pdf| }}
▲</ref> checks for errors of various types. Examples included in the documentation files are tested and produce error messages if they fail. This can be used as a primitive form of [[unit testing]]; more formal unit tests and [[regression testing]] can be included in a "tests" subdirectory. This can improve software development productivity by making it easier to find bugs as the code is being developed. In addition, the documentation makes it easier to share code with others. It also makes it easier for a developer to use code written months or even years earlier.
An interesting research question would be to compare the quality of contributions to different [software repository|software repositories] and try to relate that to features of the package development process, i.e., the degree of formality and enforcement of standards for documentation, code, and testing.
==See also==
| |||