New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 767395 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Create firmware packer/signer/updater test coverage

Project Member Reported by shapiroc@chromium.org, Sep 21 2017

Issue description

Currently, the firmware packer has pack_firmware_func/unittest.py, the updater has some primitive shell tests, and the signer has some primitive shell tests.

There is no easy mechanism to bring together all 3 components and test the complete lifecycle (since the components are so interdependent).

Currently, FAFT testing sort of does this, but it's highly coupled to a heavy test setup and doesn't fully invoke the signer features (it's all dev keys).

Goal is to do the following:
- Use config to generate a real keyset at runtime (with dev keys, but matching the actual signer keyset config structure)
- Pack the firmware
- Invoke the signer with the generated keyset config
- Invoke the updater and make various assertions about the state of the signed package
 
Owner: jclinton@chromium.org
Labels: -Type-Bug -Pri-3 Pri-2 Type-Feature
Owner: chingcodes@chromium.org
Being implemented by Chris during the rewrite.
Components: Infra>Client>ChromeOS>Build

Sign in to add a comment