[geomoose-psc] Automated testing

[Dan Little]

The 2.X stack does not have an elegant solution for that.

On Mon, Sep 26, 2016 at 11:13 AM, Jeff McKenna
<jmckenna at gatewaygeomatics.com> wrote:
> On 2016-09-26 1:01 PM, Eli Adam wrote:
>>
>> On Mon, Sep 26, 2016 at 8:57 AM, Dan Little <theduckylittle at gmail.com>
>> wrote:
>>>
>>> We do have some automated testing for the server-side services.   It's
>>> a combination of Python UnitTests and the Nosetests test runner.  I'm
>>> just way more fluent in Python for that stuff than PHP.
>>>
>>> Client side, however, we don't have a lot of scripts.  For 3.0 we're
>>> looking at Mocha integration.
>>>
>>> On Mon, Sep 26, 2016 at 10:54 AM, James Klassen <klassen.js at gmail.com>
>>> wrote:
>>>>
>>>> We haven't figured out how to do sensible automated testing with a user
>>>> driven Web app dependent on external data.
>>>>
>>>> Manual testing and automatic building of master is done at
>>>> http://demo.geomoose.org/master
>>
>>
>> To get a quick look at the status of the automated build, look at the
>> title of the page here, http://demo.geomoose.org/master/ "GeoMOOSE
>> 2.9dev (gbb075c2)".  The gbb075c2 part is from the commit log at
>> https://github.com/geomoose/geomoose/commits/master so that you can
>> confirm the automatic building is working or at least what the
>> automated build built.
>
>
> So a build fails (test fails), how is the community informed?   For example,
> commonly the failure will be reported to the -dev mailing list, so all
> developers are notified.  I'm trying find how this happens for GeoMOOSE.
>
>
> -jeff
>
>
>
>
> _______________________________________________
> geomoose-psc mailing list
> geomoose-psc at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-psc