This test has a number of shortcomings.

#### 1 ####

Quoting the control files:

"This test reads (but does not verify) the reported DiconnectReason property
reported by supplicant when [...]"

Given that we've made some efforts to get various drivers to correctly report their disconnection reason, it seems prudent to have our tests verify that they are reported correctly, at least for the few error cases we check for in these tests.


#### 2 ####

The code for grabbing disconnection reasons (server/cros/network/wifi_client.py get_disconnect_reasons()) just does a blind regex on net.log, which can include multiple disconnection reasons, including from previous runs. This can cause false positives today (we're just checking that there was *some* disconnection in the past), and it will definitely mess with fixing up #1 above.

We should probably make this check smarter, to only retrieve disconnections since the start of the test.

---

I might take a stab at this sometime, but it's certainly not high on my priority plate. So please steal from me if you'd like.