Hi Peter,

Thanks for your email! We don't have any unit tests written yet. We would love 
to produce some.
We have a large geolocation dataset here [1], that I was thinking could serve 
as a basis for 
unit testing. 

Do you have any ideas in mind that you'd like to help us out on? Help and 
patches are most
welcome! To get started, scan SIS's JIRA instance [2], and see if there are 
issues that you'd like
to work or, or report (e.g., a new JIRA issue requesting unit tests). Then, you 
can start working
on them by:

0. Create JIRA issue
1. checking out the SIS trunk
  svn co http://svn.apache.org/repos/asf/incubator/sis/trunk ./sis
2. edit files in sis
3. cd sis; svn status
  - make sure the files you edited show as edits
4. svn diff > SIS-xxx.<yourlastname>.<yyMMdd>.patch.txt where xxx is the JIRA 
issue ID of 
the issue you're working on
5. attach the patch from #4 to #0

Thanks for any help you can provide! If you don't get around to writing some 
tests, I plan on
trying to write some as part of the next SIS release (0.3).

Cheers,
Chris

[1] http://svn.apache.org/repos/asf/incubator/sis/trunk/sis-data
[2] https://issues.apache.org/jira/browse/SIS

On Mar 15, 2012, at 2:33 PM, Peter K wrote:

> Hi there,
> 
> where can I find unit tests for the sis (core) project? Doesn't it
> contain substantial amount of code to be tested (e.g. the quad tree)?
> How do you guarantuee that it works in some months with more/different
> developers (e.g. me ;)) ? Or am I searching in the wrong repo?
> http://svn.apache.org/repos/asf/incubator/sis/trunk
> 
> Kind Regards,
> Peter.


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to