| 8e9f21c005c170c5868576d86870bc175af8c610 |
|
17-Apr-2014 |
Chris Sosa <sosa@chromium.org> |
Remove complex autotest common code.
So the autotest imports make it really hard to install fake_device_server
as a standalone server. This CL removes that and just requires that the
Python code be installed in a directory called fake_device_server since
we have no Autotest dependencies.
BUG=chromium:361204
TEST=Started server + ran all unittests.
Change-Id: Iefcb5105cb96f07a99c919a1d3d41bf5ff3cb46f
Reviewed-on: https://chromium-review.googlesource.com/195454
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Alex Vakulenko <avakulenko@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/fake_device_server/common_util_unittest.py
|
| c927d5825c831e0372a75b500a57cb545f06bcf7 |
|
31-Mar-2014 |
Chris Sosa <sosa@chromium.org> |
GCD: Refactor device resource code so it can be reused by other methods.
Started working on implementing the devices / commands methods and realized
that many of the components were identical. Specifically every method
has a json-based representation that can be identified given some id
/ api_key.
So with this CL, there are 2 changes:
1) Data manipulation has been moved to a resource delegate class rather than
a dedicated tickets dict.
2) Common arg parsing has been moved to common_util.
BUG=chromium:358277
TEST=All existing unittests + local integration testing.
Change-Id: I126fd88146741cfb981475a9f8fde9f6a0a57b8b
Reviewed-on: https://chromium-review.googlesource.com/192360
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Alex Vakulenko <avakulenko@chromium.org>
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/fake_device_server/common_util_unittest.py
|
| 67d4de0fd871c5c14bdb2e18034991bc6b9c7400 |
|
18-Mar-2014 |
Chris Sosa <sosa@chromium.org> |
Buffet: Initial commit of device test service.
This initial commit supports all aspects of the registration process.
Specifically it implements registrationTicket's:
insert,post,patch,update, and get operations.
Internally I represent tickets in a dictionary which I update with
patch/update requests. I don't bother currently with anything
complex in claim (technically this could be a full oauth2 method),
and claim the device directly to a hard-coded email address.
Finally, finalize doesn't do anything besides add some dummy robot
info.
BUG=None
TEST=Tested with a combo of curl -X POST operations and web requests
through the browser. Also ran unittests which covers all functionality.
Change-Id: I50d675df6fd954db51209ad30bd8f4329b32ffa4
Reviewed-on: https://chromium-review.googlesource.com/190421
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
/external/autotest/client/common_lib/cros/fake_device_server/common_util_unittest.py
|