end-to-end extension API tests

An initial pass at structure to do end-to-end extension API tests.  I'll work on actually fleshing out some tests in the next CL.

(this landed as r23577, the scripts failed to update this entry)

[Aaron Boodman, 2009-08-16 23:22:10]

lgtm, cool!

http://codereview.chromium.org/171032/diff/23/24
File chrome/browser/extensions/extension_api_browsertest.cc (right):

http://codereview.chromium.org/171032/diff/23/24#newcode20
Line 20: static const int kTimeoutMs = 60 * 1000;  // 1 minute
1 minute seems good to me. Remove comment?

http://codereview.chromium.org/171032/diff/23/24#newcode59
Line 59: const NotificationSource& source,
Indent

http://codereview.chromium.org/171032/diff/23/24#newcode92
Line 92: IN_PROC_BROWSER_TEST_F(ExtensionApiTest, Bookmarks) {
Nit: Move this out to a separate file just to start with a good precedent? (We
want there to be lots of these tests).

[Erik does not do reviews, 2009-08-17 17:03:18]

I did the refactoring you suggested, but also decided to do a bit more while I
was in there, splitting the test notification into two separate functions. 
Since the tree is closed now anyway, please take another look at it before I
submit.

[Aaron Boodman, 2009-08-17 17:31:02]

LGTM

http://codereview.chromium.org/171032/diff/1027/47
File chrome/chrome.gyp (right):

http://codereview.chromium.org/171032/diff/1027/47#newcode50
Line 50: 'browser/extensions/extension_apitest.cc',
Yes, the name was too long before.

http://codereview.chromium.org/171032/diff/1027/53
File chrome/test/data/extensions/api_test/bookmarks/test.js (right):

http://codereview.chromium.org/171032/diff/1027/53#newcode3
Line 3: function complete() {
It would be nice if this light infrastructure were shared with all tests. I am
not sure how to do it, though.