On 3/11/14 11:56 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>On Tue, Mar 11, 2014 at 11:15 PM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 3/11/14 10:26 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: >> >> >Doesn't Mustella need bitmap comparison? That would be almost >>impossible >> >to get to work in HTML. Selenium probably is a better option for these >> >kind of things. >> Well, lately I've been wishing we'd done display-list compares instead >>of >> bitmap compares. Just think of how much effort goes into maintaining >>the >> bitmaps, how many are wrong, etc. So it isn't "need". We're going to >> have to touch virtually every existing test. I don't think we can get >> them to run as-is. The question is how much we need to touch. >> > >I think bitmap comparisons are the most fool-proof way way to test things, >but that is just me. If we don't want to do bitmap comparison, perhaps we >can use FlexUnit? I think the display-list compares show more promise. The actual color choice can vary by player version/platform. Our code can only control the display list and not the actual pixels. Regarding FlexUnit, I think right now were talking more about functional testing. There is a whole other effort to generate unit tests via FlexUnit or something like it. Not sure when we'll get to that, but we really should at some point. > > >> > >> >Another option is that perhaps we could build a runner in AIR that >>loads >> >the html stuff in a HTML component. That we could reuse the bitmap >> >comparison part as well. That would test only Webkit rendering, but >>that >> >could be a good baseline. >> That's a cool idea. We'll call that #6. >> > >There is also the offer that Tigran from RiaTest made earlier. This >thread >has the details [1] >He even created a sample test here [2] Yeah, I never found time to try RiaTest. My sense was that it was more like QTP and we might use it to do automated testing of larger applications like some of our examples or more sophisticated samples we will hopefully build someday soon. So really, I see us using at least 3 testing engines: unit testing (hopefully FlexUnit), functional testing of the framework (Mustella/Marmotinni), and functional testing of applications/samples (RiaTest). -Alex
