[roll] Roll fuchsia [wlan] Housekeeping of WLAN end-to-end base test classes

The only logical change is that CoreBaseTestClass enforces invariant of
no ifaces before each test. The CoreBaseTestClass now begins every test
by destroying all of the ifaces. This provides a consistent test
environment for each test. A future version may allow for preventing the
destruction of ifaces between tests, though that should be an
exceptional case.

Otherwise, this change does bunch of housekeeping:

- Introduce the concept of a "test kit" provided by a base test
class. For example, inheriting from CoreBaseTestClass will make
a  `test_kit` available in each test that contains the one and
only phy id and a DeviceMonitorClient.
- Delete synchronous duplicate ConnectionBaseTestClassSync. This will
make applying a change to unify how honeydew handles async easier later,
and it relieves the maintenance burden of needing to change both
classes.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1454308
Original-Revision: 6631cf0f778629bdca8cfebbf2b80c881fd158a8
GitOrigin-RevId: 1e3fcc2719cc2b08711adf6c7e545f06f5119756
Change-Id: Iba3c1a15c4a0346b9a0947238f982047d963f9bf
1 file changed
tree: d41aa5994d4e338104c3e0bd14fe04bcbef5c2db
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.