Makes sense. And would it be too cumbersome to test our extensions using Chrome's testing system? (i.e. using real extension APIs, not mocks).
-matias On Sep 28, 2:29 pm, Aaron Boodman <[email protected]> wrote: > It hasn't been done. Our tests are more about testing the extension > system, not the extensions, so mocking out the system would be > counter-productive :) > > - a > > On Mon, Sep 28, 2009 at 11:18 AM, Matias Pelenur > > > > <[email protected]> wrote: > > > Hi, > > I'm working on a somewhat complex extension, and I've started writing > > JSUnit tests for the different components (background page, toolstrip, > > content scripts, interactions between them). > > > Has anyone written mock versions of the chrome APIs in Javascript? > > (chrome.extension.connect, chrome.tabs.getSelected, etc). Or are there > > some available from the Chrome team? > > > I noticed that there are extension tests under > >http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/data/exte..., > > but as far as I can tell, you need the Chrome test runners to test > > them. I'd like something a bit more lightweight, that can be run using > > standard JSUnit. Unless of course I am mistaken, and using the > > existing Chrome test runner is fairly easy to do outside of the Chrome > > codebase. > > > If this seems useful and has not been done yet, perhaps I'll start a > > little side project on code.google.com and people can contribute to > > it... > > > -matias --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" 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/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
