Hi Chris, thanks for your reply!
> 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] I more meant single unit tests which simply ensures the raw functionality of one a tiny part of the system and are often written when or before the piece of code is written. I think, what you have in mind are more integration tests (not sure though :) !) which tests performance and more complicated bugs when the units play together... The 'problem' without unit- and only integration-tests would be that you see a test is failing, but you'll need a lot of time to dig into the real reason of the bug. Also executing the unit tests should not take a long time to load values, also IMO unit tests are a great resource for other developers or could even replace documentation ... > Do you have any ideas in mind that you'd like to help us out on? I'm especially interested in an memory efficient datastructure for a Map ala Map<lat+lon, AnyValue> I've already implemented a very rough prototype of such a Map using a ByteBuffer but now I think a datastructure with 'getNeighbour' would give a huge benefit and I'm looking about possibilities. > Help and patches are most welcome! Yeah, I'll definitely have a look into SIS as I'm more digging into graphs and geo stuff now. Regards, Peter. > 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.
