[mapserver-dev] Motion: move autotests into main mapserver repo

[Lime, Steve D (MNIT)]

+1, a good idea…

From: mapserver-dev [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of thomas bonfort
Sent: Wednesday, February 24, 2016 12:11 PM
To: MapServer Dev Mailing List <mapserver-dev at lists.osgeo.org>
Subject: [mapserver-dev] Motion: move autotests into main mapserver repo

Hi,

We initially decided to separate our autotests into a distinct repository, mainly in order to be able to manage commit rights differently on the tests vs. the actual code. With hindsight, this was not an optimal solution as it creates a burden when updating/creating/accepting tests.

After discussion with Even and Stephan, we would like to motion to move the autotests into a subdirectory of the main mapserver repository.

Pros:
- Tests are always in sync with the code they refer to
- Adding tests along with a bugfix or feature is an atomic operation and does not require operating on two distinct commits on two distinct repositories
- Updating tests on older branches will automatically be merged into the newer branches in the same way happening today for code.

Cons:
- The history of the tests will be lost in the main mapserver repo. The exisiting autotest repo will be kept read-only to be able to access this history should this rare need arise.
- The initial checkout of the mapserver repo will be heavier as the tests need to be downloaded. This does not concern our release tarballs as the tests would not be included there.

I would like to act quickly on this while we are still in sprint mode and have the time to iron out any issues.

I'll start with my +1,

Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20160224/0ebbd391/attachment.html>