Hi,
Now wouldn’t it be even more useful if we knew why the unit test failed? Apparently D doesn’t print that information automatically on assertion failure, supposedly for performance reasons.
Off-topic, but recent frontends feature a `--checkaction=context` switch, which for your example yields something like:
onlineapp.d(5): [unittest] [3: 30, 2: 20, 1: 10] != [1: 10] 1/1 unittests FAILED https://run.dlang.io/is/XZy5PN
