- Nov 3, 2018
There are so many variables across test beds in the area of RD test. Most testing, although well intentioned, involves an exact state of traffic/ signal that can never be repeated. Not really fair. Wouldn't it be nice if we had a testbed that had a "set" track with a "known", challenging set of problems/ issues for an RD to address/ resolve? Static distance, signal, obstructions, noise, other environmental factors. The holy grail of test beds. A test bed from which not only different detectors could be challenged/ tested, but different versions of firmware could be tested. No one provides detailed tests across firmware versions of all the available platforms. We "assume" no changes have been made. We "know" however that variations in function effect other daemons/ functions on a fixed hardware platform with fixed resources. In the end, aren't we really just testing firmware? Doesn't it make sense to test across a fixed test bed?