Add GPS hardware test to the factory suite.

Add GPS hardware test to the factory suite.

Make sure basic GPS hardware test is included in the factory
test flow.

Change-Id: I2ac6bd11317cf7cf6f7fd5e53176772febc84b7b

BUG=chromium-os:647
TEST=manual

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=0d8c655

[Nick Sanders, 2011-03-24 06:53:36]

Also FYI Tammo, Hungte: vbendeb has added a GPS factory test, which validates
chip <-> SW interface.

http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
File client/site_tests/suite_Factory/test_list (right):

http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
client/site_tests/suite_Factory/test_list:109: 
It should probably go in runin (fully automated test sequence) or as an
individual test right before keyboard.

http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
client/site_tests/suite_Factory/test_list:252: AutomatedSubTest(
This is the firmware modification sequence, Can you move this to the earlier
test sequence?

[Hung-Te, 2011-03-24 07:27:22]

Just like nick's comment - unless you need the final HWID and firmware BMP/HASH
etc, otherwise please put the GPS test before the HWID tests, maybe in same
place as x-display, keyboard, or other devices.

[vb, 2011-03-25 17:11:51]

PLA

http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
File client/site_tests/suite_Factory/test_list (right):

http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
client/site_tests/suite_Factory/test_list:109: 
On 2011/03/24 06:53:36, Nick Sanders wrote:
> It should probably go in runin (fully automated test sequence) or as an
> individual test right before keyboard.

Done.

http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
client/site_tests/suite_Factory/test_list:252: AutomatedSubTest(
On 2011/03/24 06:53:36, Nick Sanders wrote:
> This is the firmware modification sequence, Can you move this to the earlier
> test sequence?

Done.

[vb, 2011-03-26 00:27:10]

On 2011/03/25 17:11:51, vb wrote:
> PLA
> 
>
http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
> File client/site_tests/suite_Factory/test_list (right):
> 
>
http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
> client/site_tests/suite_Factory/test_list:109: 
> On 2011/03/24 06:53:36, Nick Sanders wrote:
> > It should probably go in runin (fully automated test sequence) or as an
> > individual test right before keyboard.
> 
> Done.
> 
>
http://codereview.chromium.org/6410034/diff/2001/client/site_tests/suite_Fact...
> client/site_tests/suite_Factory/test_list:252: AutomatedSubTest(
> On 2011/03/24 06:53:36, Nick Sanders wrote:
> > This is the firmware modification sequence, Can you move this to the earlier
> > test sequence?
> 
> Done.

submitting after showing this to nsanders and getting a verbal
approval.

[Nick Sanders, 2011-03-26 01:02:11]

lgtm