Hi Troels, The following are tips for good development techniques. If you ever encounter a bug, the first thing is to create a bug report at https://gna.org/bugs/?group=relax. But this is only really needed for the trunk and not the branches. The branches are for development, so there will often be breakages and bug reports by developers is a waste of time ;)
Secondly once you encounter a problem, the first instinct is to quickly fix it. But this is not the best way to approach the problem. It is much better if a system, unit, or GUI test is created to catch the problem (or an existing test is modified to catch it). Then the test suite will fail until it is fixed. This approach allows more and more of relax to be covered by tests and checked as development progresses. For a branch, this will result in much more stable and bug-free code. For an example of this approach, see http://article.gmane.org/gmane.science.nmr.relax.scm/18622 which I used to fix the popup menus in the spectrum list GUI element in the dispersion auto-analysis. Thirdly, if you would like to add a new feature or modify an old one, it is best if a system test is created or modified first. For example see http://article.gmane.org/gmane.science.nmr.relax.scm/18646 - this is not even implemented yet. Then the changes can be made with the aim of having the test pass. Regards, Edward _______________________________________________ relax (http://www.nmr-relax.com) This is the relax-devel mailing list [email protected] To unsubscribe from this list, get a password reminder, or change your subscription options, visit the list information page at https://mail.gna.org/listinfo/relax-devel
