In looking at logs for some DUTs in the test lab wificells, we suspect there might be (unreported) disconnects/reconnects on some tests. For something like wifi_perf, this is probably pretty important -- we shouldn't be reporting rates when the DUT disconnected in the middle. Also, this could be a sign of device issues.

We're landing fixes for wifi_perf here:

https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/693044

Let's consider if we should expand this to other tests. For example, we could have the base Wifi test class handle an enum, such that each test can declare something like NO_DISCONNECTS, DISCONNECTS, or DONT_CARE, and the base class can do the verification for us.

This would require reworking some of our tests that perform some kinds of manual cleanup (e.g., router.deconfig()) in their test body, as well as auditing relevant tests to see whether to opt in/out of this feature.