Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Texo/Developing"
< Texo
(→Testing) |
(→Interesting links) |
||
| Line 32: | Line 32: | ||
Here are links related to coding practices: | Here are links related to coding practices: | ||
| − | * | + | * http://www.slideshare.net/srikanthps/practices-for-becoming-a-better-programmer-presentation?src=related_normal&rel=1443810 |
Revision as of 06:16, 30 January 2010
Contents
Introduction
This page outlines how to setup a development environment to develop in Texo.
Setup
Testing
This is by far the most important must-do. Code and functionality must be supported with Junit test cases. Each plugin should have an equivalent *.test plugin which contains testcases which test the functionality.
Although many developers like testng, Texo uses Junit because it is slightly better supported by Eclipse and Eclipse build environments.
Texo currently does not use code coverage tools. There is however the wish to add this in the future.
JDK 1.5
Texo should be compiled for the JDK 1.5 platform.
Code Formatting
It is mandatory to set the coding
Copyright and headers
Documentation
The following guidelines should be followed when documenting code:
- rather use clear and describing variable and
Interesting links
Here are links related to coding practices: