Add cross platform Bluetooth testing fixture for Windows.

Add cross platform Bluetooth testing fixture for Windows.

This CL is the first step to implement GATT service in Chrome for Windows by using cross platform testing fixture.

BUG=579202

[gogerald1, 2016-01-25 23:24:59]

Patchset #1 (id:1) has been deleted

[gogerald1, 2016-01-25 23:38:11]

Description was changed from

==========
format


format


add bluetoothtest fixture

BUG=
==========

to

==========
Add cross platform Bluetooth testing fixture for Windows.

This CL is the first step to implement GATT service in Chrome for Windows by
using cross platform testing fixture.

BUG=579202
==========

[gogerald1, 2016-01-25 23:41:29]

gogerald@chromium.org changed reviewers:
+ gogerald@chromium.org, scheib@chromium.org

[gogerald1, 2016-01-25 23:41:29]

Hey Vincent, PTAL of this CL, Thanks.

[scheib, 2016-01-26 03:38:53]

The CQ bit was checked by scheib@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-26 03:40:43]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1639593002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1639593002/20001

[commit-bot: I haz the power, 2016-01-26 05:08:04]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-26 05:08:04]

Dry run: Try jobs failed on following builders:
  win_chromium_compile_dbg_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_comp...)

[scheib, 2016-01-26 05:29:27]

Note that this patch is from your @google.com account.

Looking good. Please do speak up if the tests or test fixture need adjustment as
you bring Windows online -- we should change them to fix issues.

Also, as you go, would you use the style of callbacks always being run
asynchronously (e.g. POST_TASKed). Error callbacks are more prone to this. Some
of the later tests start enforcing this with:
  // The expected error callback is asynchronous:
  EXPECT_EQ(0, error_callback_count_);
  base::RunLoop().RunUntilIdle();
  EXPECT_EQ(1, error_callback_count_);

We should really add that to more tests (add it if you can when you spot it).
Some implementations may need fixing - which you don't have to take on
responsibility for (though OK if you do fix). But I'd like to have Windows fresh
implementation keep things async.

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
File device/bluetooth/test/bluetooth_test_win.cc (right):

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
device/bluetooth/test/bluetooth_test_win.cc:13: void BluetoothTestWin::SetUp()
{}
Remove Setup & TearDown if unneeded.

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
File device/bluetooth/test/bluetooth_test_win.h (right):

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
device/bluetooth/test/bluetooth_test_win.h:1: // Copyright 2015 The Chromium
Authors. All rights reserved.
2016

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
device/bluetooth/test/bluetooth_test_win.h:35: scoped_refptr<BluetoothAdapter>
adapter_;
BluetoothTest::adapter_ exists with this type already.

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
device/bluetooth/test/bluetooth_test_win.h:40: BluetoothAdapterWin*
adapter_Win_;
adapter_Win_ -> adapter_win_

[gogerald1, 2016-01-26 19:33:26]

Thanks for review, agree with you. At present, all OS related operations have
been done in BluetoothTaskManagerWin asynchronously. GATT service implementation
will also abide by this rule.

Please check the address of your comments in CL
https://codereview.chromium.org/1632123003/.

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
File device/bluetooth/test/bluetooth_test_win.cc (right):

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
device/bluetooth/test/bluetooth_test_win.cc:13: void BluetoothTestWin::SetUp()
{}
On 2016/01/26 05:29:26, scheib wrote:
> Remove Setup & TearDown if unneeded.

The reason I override these interfaces is to explicitly say do not use super
class SetUp and TearDown.

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
File device/bluetooth/test/bluetooth_test_win.h (right):

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
device/bluetooth/test/bluetooth_test_win.h:1: // Copyright 2015 The Chromium
Authors. All rights reserved.
On 2016/01/26 05:29:27, scheib wrote:
> 2016

Done.

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
device/bluetooth/test/bluetooth_test_win.h:35: scoped_refptr<BluetoothAdapter>
adapter_;
On 2016/01/26 05:29:27, scheib wrote:
> BluetoothTest::adapter_ exists with this type already.

Done.

https://codereview.chromium.org/1639593002/diff/20001/device/bluetooth/test/b...
device/bluetooth/test/bluetooth_test_win.h:40: BluetoothAdapterWin*
adapter_Win_;
On 2016/01/26 05:29:27, scheib wrote:
> adapter_Win_ -> adapter_win_

Done.