+1 by the way On Thu, Jan 28, 2016 at 5:59 PM, Thomas Mortagne <[email protected]> wrote:
On Thu, Jan 28, 2016 at 5:49 PM, Guillaume Delhumeau <[email protected]> wrote:
Hello.
In XWiki, we take care of retro-compatibility. Each class that is not internal is considered as API, and we have clirr to detect when an API breakage is done.
However, we don't apply this strategy regarding the page objects of our functional tests. I noticed this when I've tried to use some pages objects defined on an application based on platform 6.4.1 on an other application based on platform 7.4. Due to incompatibility issues, I had to rewrite some page objects in my new application.
It will be a major issue when we will move some current core extensions to contrib.
So I propose considered Page Objects as API, and to add CLIRR checks on the build.
Not only Page Object themself since the issue you have here is with TestUtils but the whole Page Object related framework.
WDYT?
Thanks, -- Guillaume Delhumeau ([email protected]) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne