"Hash arrays" work lacks a specific testbench

[thejayps]

#230 has no testbench.

We discussed (@thejayps, @rptb1 and @UNAA008) during the preparation of the pull request that the testbench would be difficult to write, and decided to defer it until some time after 1.118. The code has been in use by Configura for some time who have reported no issues so far

[thejayps]

See also #239 - @UNAA008 asked what is meant by a "specific testbench"

[rptb1]

I'm also wondering where the word "testbench" came from and whether it means anything specific. I think @thejayps introduced it.

[thejayps]

By "specific", I meant that at the time of writing, I hadn't (and still haven't) proved that there wasn't a test or tests somewhere that exercises this hash arrays feature, but that there doesn't seem to be a test that is specifically designed to verify that hash arrays meets requirements.

In my mind "Testbench" is no different in meaning to "test". It might be an engineering/computer science convention thing. In the former it's more likely to be used by people who also connect lots of unusual things up on benches as well as write software to drive it all. I'm keen to tidy up the language around tests in places where it's confusing so we can discourage future bench suffixes if desired :)

[rptb1]

The split between MMQA (see also #116 ) and other tests definitely needs tidying.