We'd like to make our manufacturing software portable on different platforms, so that it can act as following roles:
1. Loaded on Chromebook during it's manufacturing to do tasks like hw tests, finalization, logging, provisioning, calibration, etc.
2. Extend chromium:557573, which allows us to test DUT with a Chromebook station, to test DUT with a general Linux or Windows machine.
3. Loaded on non-Chrome OS device, or headless Chrome OS device, to perform run-in tests.
To achieve our goal, Following refactoring steps are required in goofy:
1. Modularize goofy: Move all platform dependent code into separated "plugins" that can be loaded in different scenarios.
2. Support running goofy pytest without enable Goofy UI.
3. Make all platform dependent paths configurable.
We'd like to make our manufacturing software portable on different platforms, so that it can act as following roles:
1. Loaded on Chromebook during it's manufacturing to do tasks like hw tests, finalization, logging, provisioning, calibration, etc.
2. Extend chromium:557573, which allows us to test DUT with a Chromebook station, to test DUT with a general Linux or Windows station.
3. Loaded on non-Chrome OS device, or headless Chrome OS device, to perform task like run-in tests.
To achieve our goal, Following refactoring steps are required in goofy:
1. Modularize goofy: Move all platform dependent code into separated "plugins" that can be loaded in different scenarios.
2. Support running goofy pytest without enable Goofy UI.
3. Make all platform dependent paths configurable.
We'd like to make our manufacturing software portable on different platforms, so that it can act as following roles:
1. Loaded on Chromebook during it's manufacturing to do tasks like hw tests, finalization, logging, provisioning, calibration, etc.
2. Extend chromium:557573, which allows us to test DUT with a Chromebook station, to test DUT with a general Linux or Windows station.
3. Loaded on non-Chrome OS device, or headless Chrome OS device, to perform task like run-in tests.
To achieve our goal, following refactoring steps are required in goofy:
1. Modularize goofy - move all platform dependent code into separated "plugins" that can be loaded in different scenarios.
2. Support running goofy pytest without enable Goofy UI.
3. Make all platform dependent paths configurable.
I'd like to set an additional goal on this. To support "using goofy to do station-base testing", we do want a setup that
- runs on top of any Linux box, not ChromeOS
- runs goofy properly
It seems to me that an ideal solution is to make Goofy runs on top of one Docker image, for example ubuntu or debien, with all dependencies we need, so we can tell partner to just setup a Linux box, get Docker, deploy with our scripts to get device toolkit installed & updated.
Comment 1 Deleted