Yes, to some degree. Since some special class, such as the primitive types, long.class can not be substituted.
On 11/27/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote:
When you changed the test case to avoid side-effect have you made the test weaker? If not I'd prefer to run them in a fork mode "once" because in this case they run faster. Thanks, Mikhail 2006/11/27, Leo Li <[EMAIL PROTECTED]>: > Hi, all: > During fixing the bug of Harmony-2249, I found that the testcase in one > junit test file might lead to other fail in a different junit file. After > digging into it, I am aware that testcase can influence the global state of > a VM, for example, the resolution of class (both RI and Harmony have similar > behavior). Although I changed the testcase as a workaround, it is not > tested so thoroughly as I expected in order not to lead other tests to fail. > > So I recommend if we can specify some testcase that should run in junit > with fork = "true". Maybe to add some annotation is one resolution or to add > them to a property file as we done with excluded ones. > Any suggestion? > > -- > Leo Li > China Software Development Lab, IBM > >
-- Leo Li China Software Development Lab, IBM
