[GRASS-dev] Backport gunittest and tests to 7.0?

Vaclav Petras wenzeslaus at gmail.com
Mon Nov 17 05:46:40 PST 2014


I forgot to mention this but incompatibility with 2.6 is another argument
against backport. See the Tests down to 65% (from 86%) thread for further
details.

However, nothing should stop you from adding gunittest to PYTHON_HOME and
running trunk tests with release branch GRASS.

Vaclav

On Wed, Nov 12, 2014 at 11:28 AM, Sören Gebbert <
soerengebbert at googlemail.com> wrote:

> Hi Vaclav,
> i think the testing framework should go into 7.0.0 directly. Since, as
> Pietro mentioned, it will not harm GRASS users. IMHO the testing
> framework is a key feature, very valuable, it works well and is
> utterly useful to detect backport issues. Hence, using the testing
> framework a new release policy may be to reduce test failures to zero
> on Linux platforms.
>
> Best regards
> Soeren
>
> 2014-11-11 23:32 GMT+01:00 Vaclav Petras <wenzeslaus at gmail.com>:
> >
> > On Tue, Nov 11, 2014 at 5:05 PM, Luca Delucchi <lucadeluge at gmail.com>
> wrote:
> >>
> >> I don't understand if gunittest will be backported before 7.0 release,
> >> if we backport we can leave that line, otherwise it should be removed
> >
> >
> > I also don't know. It is an addition or feature, so it should not
> (doesn't
> > have to) go to release. It is nor really mature either, although it
> > apparently runs and works. The distribution is still not solved. Will the
> > tests be included in installation? What about compiled C test programs
> (now
> > compiled and added to standard modules)? So far, it has been tested just
> on
> > Ubuntu as far as I know. (More discussion on that should be on GSoC
> project
> > page)
> >
> > From the point of view of testing, it would be good to have it in release
> > branch as soon as possible, so I don't know.
> >
> > Maybe it can go to GRASS GIS 7.0.1 but not to 7.0.0.
> >
> > Vaclav
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20141117/7111f07b/attachment.html>


More information about the grass-dev mailing list