@martinbrose I'll need your input on which strategy to use for handling megabits, as listed in the todo section.

Thanks @Nytelife26,

I'll have a look by the weekend at the latest. Hopefully earlier.

I took the initiative to evaluate each strategy for handling megabits, and figured the last one would be the simplest and least surprising (implementation wise). cfspeedtest now provides a bits_to_megabits function, and whether results are stored in bits or megabits depends on the megabits flag passed to SuiteResults. the output looks like this:

{
  "megabits": true,
  "meta": {...},
  "tests": {
    "latency": {"value": 15.61, ...},
    "jitter": {"value": 7.19, ...},
    "100kB_down": {"value": 41.33, ...},
    "100kB_up": {"value": 23.01, ...}
  },
  "90th_percentile_down": {"value": 96.43, ...},
  "90th_percentile_up": {"value": 24.67, ...}
}

this is also reported by the CLI, now with keys that reflect the dict structure:

megabits: True
...
meta.region: England
meta.city: Tamworth
tests.latency: 10.77
tests.jitter: 2.06
tests.100kB_down: 35.16
tests.100kB_up: 22.62
...
90th_percentile_down: 97.64
90th_percentile_up: 24.69

quick follow up - @martinbrose, how's your schedule looking? i'm excited to continue working on martinbrose/cloudflare-speedtest-exporter#54 after we land this.