@UITest is now @Inherited: a functional test class that doesn't declare its own @UITest gets the configuration declared on its closest superclass, so several test classes can share the same configuration through a common (abstract) base class and still be run individually (-Dit.test=SomeIT). Using the same configuration for all the test classes of a module allows reusing the XWiki instance started for one test class to run another one (-Dit.test=OtherIT -Dxwiki.test.ui.servletEngine=external).
A test class that declares its own @UITest doesn't inherit anything from its base class's annotation: the whole configuration is replaced, not merged. This differs from the nested test classes of an AllIT, whose configurations are merged with the one of the top-level test class. Both are documented in the UITest javadoc.
The configuration of the nested test classes of an AllIT is now resolved through the inherited annotation too, instead of walking the superclasses by hand.
The BlockNote functional tests are the first to use it: their configuration, previously duplicated on 9 test classes, is now declared once on AbstractBlockNoteIT.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.