You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Anand V Nath (JIRA)" <de...@myfaces.apache.org> on 2014/10/20 07:52:33 UTC

[jira] [Updated] (TRINIDAD-2516) SkinProviderTest failing because of surefire test run order

     [ https://issues.apache.org/jira/browse/TRINIDAD-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anand V Nath updated TRINIDAD-2516:
-----------------------------------
    Status: Patch Available  (was: Open)

> SkinProviderTest failing because of surefire test run order
> -----------------------------------------------------------
>
>                 Key: TRINIDAD-2516
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2516
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Skinning
>    Affects Versions: 2.1.0-core
>            Reporter: Anand V Nath
>         Attachments: jira-2516.patch
>
>
> SkinProviderTest is failing due to surefire test run order. SkinProviderTest asserts skins loaded by SkinProviders and skins available in the cache to ensure correctness of SkinProvider and StyleProvider implementations.
> When this test case runs after RenderKitTestCase, this test finds some unexpected skins to be present in the StyleProvider cache already. This happens because of the Application scope concurrent map is getting shared between RenderKitTestCase and SkinProviderTest.
> To solve this problem SkinProviderTest has to clear the Application scope concurrent map by invoking {{RequestContext.releaseApplicationState()}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)