Hi,
That is excellent news. Time to freshen up my Python.
I thought the best way to contribute to Nominatim is to try and fix
a couple of outstanding issues. I don't have a specific data- or logic-
issue in mind.
marc tobias
On 28/10/2013 08:17, Sarah Hoffmann wrote:
Hi,
On Sun, Oct 27, 2013 at 10:54:32PM +0100, Marc Tobias wrote:
Given how many open bugs/defects/feature requests I see in TRAC/github
I wonder if there is an automated test suite?
How are the test cases on
http://wiki.openstreetmap.org/wiki/Nominatim/TestCases used? The wiki
history shows only 9 additions during 2013.
They are not really used. Filing a trac/github issue is definitely a
better way to get a developer's attention (although not necessarily a
developer's time, I'm afraid).
If there isn't, what would be the best approach? PHP tests running
against a local installation? Or something which runs against
nominatim.openstreetmap.org because the full planet data is required?
There are the humble beginnings of a test suite here:
https://github.com/lonvia/test-nominatim
This needs an installation with a fairly recent planet.
These are only functional API tests, so they do not test if OSM data is
processed correctly, which is what the TestCases wiki page actually want.
In the long run, I'd like to see these tests extended to functional tests
of the backend as well. I had in mind to follow the approach of OSRM[1].
Have small snippets of data imported and run tests against the API
or check DB contents directly.
Sarah
[1] e.g.
https://github.com/DennisOSRM/Project-OSRM/blob/master/features/foot/roundabout.feature
_______________________________________________
Geocoding mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/geocoding
