tree 74bfb62403a513e833e8b3b1b04984158cbdd6f7
parent 1bdb7a928e92339e4b97d6f951d4c0488fd183c2
author Chris Sosa <sosa@chromium.org> 1397100367 -0700
committer chrome-internal-fetch <chrome-internal-fetch@google.com> 1397246490 +0000

Add extra requirements when testing update payloads.

In order to verify that real Chrome OS devices with test
images are actually sending valid Omaha Requests that will get served
an update in the field, we need to check for additional items
(hardware_class and track being set). Since there are non-Chrome OS
devices that can use the devserver, we only enforce this for devices
that interact with the devserver through a devserver proxy i.e. started
with --remote. This is only used in our automated tests.

BUG=chromium:344939
TEST=Unittests which cover this functionality.

Change-Id: I201df9ac5bf5d571b5368137e50fcc397a82befd
Reviewed-on: https://chromium-review.googlesource.com/193979
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>