[eoxserver-dev] how to run autotests

Novacek, Milan milan.novacek at siemens.com
Thu Oct 13 12:44:02 CEST 2011


In my own -> I created one with create_instance.py.
How do I create an autotest instance then?  

Milan

-----Original Message-----
From: dev-bounces at eoxserver.org on behalf of Stephan Krause
Sent: Thu 10/13/2011 11:39 AM
To: dev at eoxserver.org
Subject: Re: [eoxserver-dev] how to run autotests
 
Hi Milan,

Are you running the tests in the autotest instance or in your own?

Stephan

On 2011-10-13 11:20, Novacek, Milan wrote:
> Agreed, should be moved in the SVN.
> Also, the instructions don't mention needing a link to autotest/data/meris:
>    cd data
>    ln -s ../../autotest/data/meris .
>
> Next, it looks like all we need is to load "initial_rangetypes.json" for the tests:
> (and yes I loaded them into the db:
>     python manage.py loaddata  .../eoxserver/resources/coverages/fixtures/template_initial_data.json
> )
>
> I get errors like:
>      ...
>      File "/home/novacek/o3s/work/eoxserver/resources/coverages/wrappers.py", line 223, in _get_create_dict
>        "Unknown range type name '%s'" % params["range_type_name"]
>    InternalError: Unknown range type name 'RGB'
>
>
> Regards,
>
> Milan Novacek
>
> -----Original Message-----
> From: dev-bounces at eoxserver.org on behalf of Stephan Krause
> Sent: Thu 10/13/2011 9:11 AM
> To: dev at eoxserver.org
> Subject: Re: [eoxserver-dev] how to run autotests
>
> Hi Milan,
>
> you can find the file in the eoxserver/conf directory; you can copy it
> to autotest/data. Actually I think we should move it there in the SVN ...
>
> cheers,
> Stephan
>
> On 2011-10-12 20:04, Novacek, Milan wrote:
>> Hi dev,
>>     It seems I'll need some updated instructions on how to setup and
>> run the autotests. The HOWTO there does not seem to map to the current
>> structure too well.
>> Tried using the instance created by "create_instance.py"... but
>> then when trying to run
>>          python manage.py test services
>>
>> First it can't find "No module named eoxserver.core", then when
>> manually by brute force added the appropriate path to say manage.py,
>> I don't really get much further:
>>
>>     ...
>>     File "/usr/lib/python2.7/site-packages/django/contrib/gis/db/backends/spatialite/creation.py", line 28, in create_test_db
>>       self.load_spatialite_sql()
>>     File "/usr/lib/python2.7/site-packages/django/contrib/gis/db/backends/spatialite/creation.py", line 80, in load_spatialite_sql
>>       'SQL file (necessary for testing): %s' % spatialite_sql)
>> django.core.exceptions.ImproperlyConfigured: Could not find the required SpatiaLite initialization SQL file (necessary for testing): data/init_spatialite-2.3.sql
>>
>>
>> Regards,
>> Milan Novacek
>>
>>
>
>
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3941 bytes
Desc: not available
URL: <http://eoxserver.org/pipermail/dev/attachments/20111013/b4fc30ad/attachment.bin>


More information about the dev mailing list