Firebug uses a home-built test solution http://code.google.com/p/fbug/source/browse/#svn/fbtest/branches/fbtest1.7
The two hard parts of testing are 1) recognizing the visual elements of the dynamic user interface from test code in a timely manner, 2) firing events into the user interface in a reliable manner. That is why you will find a lot of unit-test tools out there that all look similar but do not support testing of the user interface and a lot fewer test tools that all look completely different but to support UI testing. If you need to test the UI, then you will have to invest a lot of time in one toolkit or another, basically hacking it to recognize your UI. The "mozmill" is one of the UI solutions developed for mozilla addons. jjb On Aug 6, 4:43 am, Eric Lemoine <[email protected]> wrote: > Hi > > I'm interested in developing unit tests for FireFox add-ons. At this > point I'm not looking at testing XPCOM components so xpcshell doesn't > look appropriate. Does anyone know frameworks/tools for testing > FireFox add-ons?Reading John Resig's blog post about FireUnit I > thought that FireUnit could be that tool, but I haven't found > documentatiom or anything about using FireUnit for add-ons. > > Any advise? > > Thanks, > > -- > Eric -- You received this message because you are subscribed to the Google Groups "Firebug" 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/firebug?hl=en.
