I'm not sure if you are asking a question here - but if you want more information on the investigation I've been doing into GeoNetwork see this thread from the development list: https://groups.google.com/a/opengeo.org/group/geonode-dev/browse_thread/thread/024afcae8472493b#
-- David Winslow OpenGeo - http://opengeo.org/ On Sat, Apr 16, 2011 at 5:52 AM, Jude Mwenda <[email protected]> wrote: > Updates on geonetwork. > > > 2011/4/16 David Winslow <[email protected]> > >> Hey all, >> >> I just thought since more folks have been expressing interest in GeoNode >> development (especially the testing stuff) I'd try and start sending >> periodic status updates on the project (I will aim for weekly frequency but >> I make no promises since I am easily distracted :) Anyway, this week has >> seen a big push on automated testing, prompted largely by feedback from >> Ariel and the AIFDR crew. (AIFDR is developing a GeoNode-based tool called >> Risiko, and since GeoNode is their foundation its stability is quite >> important to them.) >> >> In that interest, we at OpenGeo have set up a continuous >> integration<http://en.wikipedia.org/wiki/Continuous_integration>server at >> http://geonode-testing.dev.opengeo.org/ which will monitor the software >> repositories and re-run our test suite automatically after changes are made. >> (We still expect developers to test their own code, but having this service >> allows us to make some guarantees.) >> >> While we did have a basic test suite before this week, it missed some >> important pieces of functionality such as file upload and permissions, so >> Jeff has been working with Ariel on improving it. (You'll note this code is >> not yet in the master branch. So far, the tests are dependent on a patch >> Ariel submitted earlier this week which is still pending review; hopefully >> we'll be able to pull this in next week.) Jeff is also developing a more >> extensive test suite (using sample data provided by AIFDR) to verify cases >> which require more extensive setup than the unit tests included with each >> project. >> >> Jeff's unit test branch: >> http://github.com/jj0hns0n/geonode/tree/bulletproof/ >> Jeff's extended unit testing suite: >> https://github.com/jj0hns0n/geonode-tests/ >> >> Beyond improving the automated testing situation for GeoNode, here are >> some other things that happened this week: >> >> - AIFDR-funded development on automatic styling means that someday >> soon raster layers uploaded to GeoNode will have their NODATA values made >> transparent and the coloration based on the range of values present, >> rather >> than our current default which presents several rendering artifacts. For >> the adventurous, the experimental branch is available at >> https://github.com/dwins/geonode/tree/smart-rasters >> - We've spent some time investigating the stability issues affecting >> GeoNetwork, and made some changes to GeoNode to mitigate the problem. >> This >> code has been deployed to the GeoNode demo site for testing and will >> hopefully be released as GeoNode 1.0.1 next week. >> >> Thanks for reading. >> >> -- >> David Winslow >> OpenGeo - http://opengeo.org/ >> > >
