| commit | 1f115ae9ee3c043e9577e7ce9872dc99323fdcb3 | [log] [tgz] |
|---|---|---|
| author | Yusuf Mohsinally <[email protected]> | Wed Nov 06 17:31:16 2013 -0800 |
| committer | chrome-internal-fetch <[email protected]> | Thu Nov 07 20:09:01 2013 +0000 |
| tree | 8cca35d933dfae42de264eb3f540cf8e55e2e83e | |
| parent | 5d2551b23350ce3a96e1345a6f6eb6de552bce4c [diff] [blame] |
Correctly using initialize() rather than setup() for FAFT tests. FAFT tests have been using setup() (which is run once at autotest init), when it should have instead used initialize() for running code before each test case is run. BUG=chromium:267175 TEST=Ran tests manually against Pit device to ensure that these changes did not introduce problems. Change-Id: If0e76e12b9f40249154d7b95a1375b2787a56304 Reviewed-on: https://chromium-review.googlesource.com/176024 Reviewed-by: Wai-Hong Tam <[email protected]> Commit-Queue: Yusuf Mohsinally <[email protected]> Tested-by: Yusuf Mohsinally <[email protected]>
diff --git a/server/site_tests/firmware_DevScreenTimeout/firmware_DevScreenTimeout.py b/server/site_tests/firmware_DevScreenTimeout/firmware_DevScreenTimeout.py index 01422bc..bfa5feb 100644 --- a/server/site_tests/firmware_DevScreenTimeout/firmware_DevScreenTimeout.py +++ b/server/site_tests/firmware_DevScreenTimeout/firmware_DevScreenTimeout.py
@@ -82,8 +82,8 @@ got_timeout)) - def setup(self): - super(firmware_DevScreenTimeout, self).setup() + def initialize(self, host, cmdline_args): + super(firmware_DevScreenTimeout, self).initialize(host, cmdline_args) # This test is run on developer mode only. self.setup_dev_mode(dev_mode=True) self.setup_usbkey(usbkey=False)