[jira] (SUREFIRE-749) Parallel methods should run in separate classloaders

["Tibor Digana (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/SUREFIRE-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352054#comment-352054 ] 

Tibor Digana commented on SUREFIRE-749:
---------------------------------------

@Kristian Rosenvold
We are running towards to a significantly large number of bugs.
After 3 years I prefer closing this issue.
I don't think this has reached any voters till now.
I don't see any simple way to isolate for instance the Swing EDT thread in UI tests methods using separate classloaders, therefore forked processes would do this job easily.

> Parallel methods should run in separate classloaders
> ----------------------------------------------------
>
>                 Key: SUREFIRE-749
>                 URL: https://jira.codehaus.org/browse/SUREFIRE-749
>             Project: Maven Surefire
>          Issue Type: New Feature
>          Components: Junit 4.7+ (parallel) support
>    Affects Versions: 2.8.1
>            Reporter: Gili
>
> When running in parallel-method or parallel-both mode, each @Test should run in its own ClassLoader. I'm running into a lot of problems involving the use of static variables in 3rd-party libraries. Here are two examples:
> 1. slf4j: http://bugzilla.slf4j.org/show_bug.cgi?id=176
> 2. guice: http://code.google.com/p/google-guice/issues/detail?id=635
> I believe running in isolated ClassLoaders would fix both problems and it makes a lot of sense from a test isolation point of view so we should do it anyway.
> I believe Surefire's forkMode is defined in terms of isolated JVMs instead of ClassLoaders. Furthermore, it only seems to support per-Class isolation instead of per-@Test isolation.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)