Coverage does need to include all src/main/flex classes into the test SWF in order to produce reliable test results. Otherwise it will always reports 100% of classes coverage. There is no other way to deal with that right now, but I'm open for suggestions.
Anyway, if you know that classes are broken, why don't you remove they from src/main/flex or at least name they as .txt, .old or something else?! VELO On Mon, Jul 26, 2010 at 1:21 PM, jsight <[email protected]> wrote: > I am attempting to run test classes and coverage reports on a fairly > large SWF project. The project compiles perfectly as long as there > are no tests. > > If I include test classes in src/test/flex, the build of the actual > app fails. > > All of the errors are on classes that would not normally be included > in the SWF itself. I cannot seem to control which classes from src/ > main get compiled. > > Is there a way to have it select the same classes as would normally be > compiled without tests? > > The SWF compiles perfectly if the test files are not included at all, > and it compiles ok before getting to the test phase of execution as > well. > > -- > You received this message because you are subscribed to the Google > Groups "Flex Mojos" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<flex-mojos%[email protected]> > For more options, visit this group at > http://groups.google.com/group/flex-mojos > > http://flexmojos.sonatype.org/ > -- You received this message because you are subscribed to the Google Groups "Flex Mojos" 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/flex-mojos http://flexmojos.sonatype.org/
