I would also like a tip on how to run that testcase alone.

Right now I am doing this:

(cd user && ant test -Dtest.emma.selenium.disable=true 
-Dtest.draft.htmlunit.disable=true -Dtest.coverage.htmlunit.disable=true 
-Dtest.nometa.htmlunit.disable=true -Dtest.nongwt.disable=true 
-Dtest.dev.htmlunit.disable=true -Dtest.web.htmlunit.disable=true 
-Dgwt.junit.testcase.includes=**/SerializableTypeOracleBuilderTest.class)

Can I narrow it further down

Best regards
Rene

Den mandag den 16. november 2015 kl. 22.28.31 UTC+1 skrev Rene Hangstrup 
Møller:
>
> Hi
>
> I am trying to write a test case for 
> https://github.com/gwtproject/gwt/issues/7247
>
> There was an old test in 
> https://github.com/gwtproject/gwt/issues/7247#issue-87058425 that 
> reproduces the problem.
>
> I am trying to narrow it down and implement it as part of the existing 
> SerializableTypeOracleBuilderTest instead, but so far I cannot make it fail 
> (after removing the change to SerializableTypeOracleBuilder)
>
> By adding tracing to the original test case that reproduced the problem I 
> can see that computeTypeInstantiability() visits the classes in this order: 
>
> Level1, Root, Parameter, Level2, AnInterface
>
> But in my new test case they are visited in this order:
>
> Root, Level1, Level2, Parameter, AnInterface
>
> My theory is that the test will fail if they are visited in the same order 
> as in the original setup.
>
> Any suggestions for either
> - how I can force the classes to be visited in the desired order?
> - how I can make the test closer to the original setup?
>
> Best regards
> Rene
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/9ddfa60b-61f6-4b04-9fbe-7b677eb223c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to