Phase 1 of Firmware Test (FAFT) improvements completed

[Yusuf Mohsinally]

Hi All,

We have completed phase 1 of FAFT infrastructure improvements.

What this means for you:

- if you run FAFT tests, the changes are transparent.

- if you debug/write/maintain tests, things are now much simpler. See below.

FAFT used to consist of:

1. A set of helper functions and objects used in autotests.

2. A framework, which required test steps be specified in a special data structure.

With the new changes:

Tests do not require a custom data structure. Steps are now function calls like in any autotest. And no tasks are hidden behind the step processing code.

Example test conversion: https://chromium-review.googlesource.com/#/c/199465/

All firmware tests have been gradually migrated over the last few months, and been run over multiple platforms, both internally and externally. As of now, all tests have been converted and old code has been deleted.

As we continue improving the infrastructure and tests, please let us know what changes you would like to see in the future.

Thank you,

The ChromeOS Firmware Test Team