>I haven't found an (easy) way to catch missing tests. Every once in a while >it skips an entire SWF. It appears like it launches it, but it takes too long >to launch and then >kills it, but it doesn't currently know what tests were in >that SWF so they don't go in the report. To see the differences between Mac >and Win you have to examine the >ExcludeListWin/Mac files. I suppose we could >try to report on what we find in there.
>From what I understood from reading the code, it seems that AS code is loading >the exclude file, and load the excluded lines in UnitTester.excludeList Then knows when a test is excluded: UnitTester.as 1193-1200 and and 1874-1881 So it should be possible to log something here trace(...) and have the java runner catch it from the log and report it in the results. WDYT? Maurice -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : dimanche 13 octobre 2013 07:11 À : dev@flex.apache.org Objet : Re: Failing mustella tests On 10/12/13 5:39 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >What make a good test is it being consistently repeatable. We seem to >have a different number of tests on each platform and different results >which may be environment dependant?? > >It's hard to tell from the exclusions list what is excluded, is there a >way for mustella to show how many tests it skipped and which ones they >were? I haven't found an (easy) way to catch missing tests. Every once in a while it skips an entire SWF. It appears like it launches it, but it takes too long to launch and then kills it, but it doesn't currently know what tests were in that SWF so they don't go in the report. To see the differences between Mac and Win you have to examine the ExcludeListWin/Mac files. I suppose we could try to report on what we find in there.
