[Feedhenry-raincatcher] Suggestion for more confidence in automated raincatcher tests

[Niall Donnelly]

Sure, this is an initial spike around auto deployment of the demo solution:
https://issues.jboss.org/browse/RAINCATCH-719

Any comments here would be great.

Thanks

On Fri, Apr 28, 2017 at 10:40 AM, David Martin <davmarti at redhat.com> wrote:

> That's great that its in coming sprints.
>
> Is there a Jira Epic or issues with some more info?
>
> I can leave some comments if that would be helpful.
>
> On 28 April 2017 at 10:35, Niall Donnelly <ndonnell at redhat.com> wrote:
>
>> Hi David
>>
>> Yes, definitely. it is something we are looking into in the coming
>> sprints to have a more comprehensive set of tests for our modules and demo
>> apps.
>>
>> It would be useful to take a look at how fh-mbaas-api does it. Thanks for
>> the info.
>>
>> Thanks
>> Niall
>>
>>
>>
>> On Fri, Apr 28, 2017 at 10:22 AM, David Martin <davmarti at redhat.com>
>> wrote:
>>
>>> Hey Raincatcher folks,
>>>
>>> I'm a little out of the Raincatcher loop, but know enough to be
>>> dangerous :)
>>> I'm wondering if there would be benefit in having automated acceptance
>>> tests for any changes across the Raincatcher Demo Solution parts.
>>> For example, if any of the
>>> * raincatcher-demo-mobile
>>> * raincatcher-demo-cloud
>>> * raincatcher-demo-auth
>>> * or raincatcher-demo-portal repos have a PR, they run their automated
>>> unit tests (as they currently do), and follow that up with a run of
>>> automated acceptance tests.
>>>
>>> The acceptance tests would use the PR branch of the repo that has
>>> changed, and take the version on master of the other 3 repos.
>>>
>>> Here's an example scenario.
>>> * I make a PR for raincatcher-demo-auth
>>> * Travis runs unit tests
>>> * Travis then uses all 4 repos to bring up a working Raincatcher demo
>>> solution
>>> * Acceptance tests are executed
>>>
>>> The acceptance tests could execute/interact with the Portal and Mobile
>>> App to ensure no regressions.
>>>
>>>
>>> This is simlar to what happens in fh-mbaas-api for sync [1], where
>>> fh-mbaas-api unit tests are executed at PR time, followed by a run of sync
>>> acceptance tests [2] which use the latest fh-js-sdk.
>>>
>>> [1] https://github.com/feedhenry/fh-mbaas-api/blob/master/.t
>>> ravis.yml#L24-L29
>>> [2] https://github.com/feedhenry/sync-acceptance-testing
>>>
>>> Interested in any thoughts.
>>>
>>> --
>>> David Martin
>>> Red Hat Mobile
>>> Twitter: @irldavem
>>> IRC: @irldavem (feedhenry, mobile-internal)
>>>
>>> _______________________________________________
>>> Feedhenry-raincatcher mailing list
>>> Feedhenry-raincatcher at redhat.com
>>> https://www.redhat.com/mailman/listinfo/feedhenry-raincatcher
>>>
>>>
>>
>>
>> --
>>
>> NIALL DONNELLY
>>
>> SOFTWARE ENGINEER
>>
>> Red Hat
>>
>> <https://www.redhat.com/>
>>
>> Communications House, Cork Road
>>
>> Waterford City, Ireland X91NY33
>>
>> ndonnell at redhat.com    IM: ndonnelly
>> <https://red.ht/sig>
>>
>
>
>
> --
> David Martin
> Red Hat Mobile
> Twitter: @irldavem
> IRC: @irldavem (feedhenry, mobile-internal)
>



-- 

NIALL DONNELLY

SOFTWARE ENGINEER

Red Hat

<https://www.redhat.com/>

Communications House, Cork Road

Waterford City, Ireland X91NY33

ndonnell at redhat.com    IM: ndonnelly
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-raincatcher/attachments/20170428/e98b9f0c/attachment.htm>