65dca4379e
Instead of using custom messages to send test reuslts from test app to test runner for tests for API events, use standard extensions::ResultCatcher to get results - it workss better with chrome.test.assert methods and produces better failure messages. Use chrome.test.listenOnce to register event listeners in tests. Note that there is no need for chrome.test.succeed for test cases using listenOnce - it will get called once listener is run (unless listener function asserts, in which case test will fail). Refactors audio/test.js - added helper methods for testing relevant properties of devices returned by chrome.audio.getInfo to make expectations a bit easier to specify/understand. The refactored test are less dependent on exact order in which audio devices are reported in device list (as the order is of no relevance). Review-Url: https://codereview.chromium.org/2462833002 Cr-Commit-Position: refs/heads/master@{#429678}
This will become a reusable extensions module. It implements the core parts of Chrome's extension system, and can be used with any host of the 'content' module.