3 Aug
2015
3 Aug
'15
2:55 p.m.
On 3 Aug 2015 at 14:53:50, Marius Dumitru Florea
(mariusdumitru.florea@xwiki.com(mailto:mariusdumitru.florea@xwiki.com)) wrote:
+1. I guess we'll have to add a
xwiki-platofrm-web-test module at some
point for testing the Velocity templates that are shared between
skins.
yes, I didn’t mention this but I agree. For now since we have only 1 skin (or will soon
since we’re removing colibri) it seems simpler to have the tests in Flamingo.
Thanks
-Vincent
Thanks,
Marius
On Mon, Aug 3, 2015 at 3:41 PM, vincent(a)massol.net wrote:
> Hi devs,
>
> I’ve brainstormed with Thomas and we’ve discussed where to put functional tests such
as test that verify that page creation from the UI works (i.e. that test the create vm and
the oldcore java action in this case).
>
> We’re proposing to put those tests (which are currently located in enterprise tests)
under xwiki-platform-flamingo-skin, i.e. to assimilate those tests as functional skin
tests.
>
> In order to do this I’ll create:
>
> xwiki-platform-flamingo
> |_ xwiki-platform-flamingo-skin
> |_ xwiki-platform-flamingo-skin-resources (—> zip)
> |_ xwiki-platform-flamingo-skin-test (functional tests)
> |_ xwiki-platform-flamingo-theme
> |_ xwiki-platform-flamingo-theme-bootswatch (XAR)
> |_ xwiki-platform-flamingo-theme-ui (XAR)
> |_ xwiki-platform-flamingo-theme-test (functional tests for Theme UI)
>
> WDYT?
>
> I’m going to start moving and splitting the current CreatePageTest into 2:
> * the tests that use Template Provider will go in platform-administration-tests
> * the tests that verify simple page/space creation will go in
xwiki-platform-flamingo-skin-test
>
> Thanks
> -Vincent