Actually when the error says the compilation unit is not found, it means that the test runner isn't finding your compiled class. If you look at the "Source" tab of your "Java Build Path", I'll bet that you have the "Allow output folders for source folders" checkbox checked. Unchecking this will cause all compilation units to be put into targets/classes (your test classes are currently in target/test- classes and the test runner can't find them). There are other ways to solve this problems but this is the simplest. It has the undesired (I assume) side affect of including the test classes in your output jar or war, so you have to exclude them during packaging. The second alternative is to make sure the target/test-classes folder is on your classpath during testing.
On Jan 30, 10:43 am, salk31 <[email protected]> wrote: > Sorry, I'm afraid I don't use maven > > On Jan 30, 7:31 am, tanteanni <[email protected]> wrote: > > > > > > > > > thx, the problem is how to fix it. i have a maven project generated by > > webappcreator from google. i thought unit tests with gwttestcase should > > work out of the box? > > with sources not in classpath do you mean the eclipse way of sources > > (knowing were to look in debugging session, debugging "normal" tests is > > working fine)? Or do you mean the "gwt-sources" (declared in gwt.xml)? (i > > put all tests in same packages as the OUTs - that should be enough for gwt > > to find the sources?!) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
