You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by Paul Merlin <pa...@apache.org> on 2017/05/21 15:31:08 UTC
Re: polygene-java git commit: :tools:generator Add empty test to
generated rest-api application
FYI Niclas
Le 2017-05-21 17:29, paulmerlin@apache.org a écrit :
> Repository: polygene-java
> Updated Branches:
> refs/heads/develop 779cffbc6 -> 84a794d29
>
>
> :tools:generator Add empty test to generated rest-api application
>
> See
> tools/generator-polygene/app/templates/RestAPIApplication/bootstrap-test.tmpl
>
> The generator tests now run ./gradlew check instead of ./gradlew
> classes on generated projects
Re: polygene-java git commit: :tools:generator Add empty test to
generated rest-api application
Posted by Paul Merlin <pa...@apache.org>.
Niclas Hedhman a écrit :
> To support this, we really need the internal Docker support to become
> official. So, I am removing the "internals" as it only contains the
> DockerRule stuff, and that I am moving to core/testsupport.
>
> With that in testsupport, I am adding testcases to Yeoman generator that
> will do a full integration test (i.e. slow) and the combinatorial problem
> gets blown out of the water, 1 day to a week, with every other feature
> added to double that time. Nevertheless, I think it is worthwhile doing.
For our docker testing infrastructure to work in other projects they
will need some build machinery to actually build the required docker
images (they are not published to any public docker registry). We could
at some point either publish testing images or build machinery (e.g.
Polygene Gradle Plugin) but that won't happen in 3.0.
I think we should not promote docker based testing from internals in a rush.
Plus, since I implemented this testing facility,
https://www.testcontainers.org/ appeared and I think we should move to
using this instead of our ad-hoc solution at some point.
For testing the generated projects, maybe only
assembly/activation/passivation would be enough for now ?
Or, @Ignore the generated integration tests for the assemblies that
require external services.
Re: polygene-java git commit: :tools:generator Add empty test to
generated rest-api application
Posted by Niclas Hedhman <ni...@hedhman.org>.
To support this, we really need the internal Docker support to become
official. So, I am removing the "internals" as it only contains the
DockerRule stuff, and that I am moving to core/testsupport.
With that in testsupport, I am adding testcases to Yeoman generator that
will do a full integration test (i.e. slow) and the combinatorial problem
gets blown out of the water, 1 day to a week, with every other feature
added to double that time. Nevertheless, I think it is worthwhile doing.
On Sun, May 21, 2017 at 11:31 PM, Paul Merlin <pa...@apache.org> wrote:
> FYI Niclas
>
>
> Le 2017-05-21 17:29, paulmerlin@apache.org a écrit :
>
>> Repository: polygene-java
>> Updated Branches:
>> refs/heads/develop 779cffbc6 -> 84a794d29
>>
>>
>> :tools:generator Add empty test to generated rest-api application
>>
>> See
>> tools/generator-polygene/app/templates/RestAPIApplication/bo
>> otstrap-test.tmpl
>>
>> The generator tests now run ./gradlew check instead of ./gradlew
>> classes on generated projects
>>
>
>
--
Niclas Hedhman, Software Developer
http://polygene.apache.org - New Energy for Java