> > <http://docs.djangoproject.com/en/dev/topics/testing/> > > We're already using the Django test suite (sort of; the tests are not very > well maintained.) >
Oh, ok, my bad. In that case, Ariel: yeah, definitely write whatever tests you think would be helpful! This probably should be common practice for the project, but we have been on such tight timelines that we've cut these corners. But yeah, tests are great. Yay tests! > I am more interested in figuring how the JavaScript tests will be set up; > particularly given that testing the scripts in the site will probably > require standing up a GeoServer alongside of Django. > > We've basically had this discussion before and the JS gurus from OpenGeo > have opined that manual testing will be the same or less work as maintaining > an automated test suite, so I would want to get Andreas' input on a JS test > environment before implementing it. > > > >> > What's involved in adding a project profile to Pinax? Are we going to >> have >> > to convince the Pinax guys that SDI is a useful profile for their social >> > networking toolkit (might be a hard case to make)? >> >> The case has already been made, there have been talks of a "geopinax" >> for a lot of time and even some integration of "foursquare type" >> applications. They are very inclusive and I know already a lot of the >> folks in the community. In the remote case that they don't like our >> geonode profile, we can just create a geonode-admin.py script that >> mimics or extends pinax-admin.py, just as pinax-admin.py extends >> django-admin.py. >> > > Are there Pinax community lists or IRC communities we should be getting > familiar with if we are going to start working with them more closely? > > > Good question. > -- Sebastian Benthall OpenGeo - http://opengeo.org
