Comment 11 for bug 1311462

Another possible solution, of course, is to remove the "n" requirement from the "n" tests; in this case they will always run (and fail on systems that don't really support them) but at least they will run.

Yet another solution would be to wrap the resource in a shell script that also looks at output of "sudo iwlist wlan0 scanning" and checks if it sees the "n" access points. This is bad because it relies on an assumption that may not be true, but it would allow our tests to run correctly.

Marking as a blocker because without this, the N tests which are required for cert will simply not run.