assertion

For now, the theme is harcoded in the code. Ideally we want the user to be able to load its custom theme from a simple json file. This will allow for example to address accessibility issues (for visually impaired users)

ex:

I have a zora.theme.json in my project root

{
    "version":1,
     "bgError":"bgRed"    
}

Where the values can be anything in [colorette](htt

Add the following extensions methods for dictionaries:

var dictionary = new Dictionary<string, string>
{
    ["key1"] = "value1",
    ["key2"] = "value2",
};

dictionary.Throw().IfContainsKey("key1");
dictionary.Throw().IfNotContainsKey("key3");

And the corresponding dictionary properties extension methods:

var dictionary = new Dictionary<string, string

The report shows the timings of each test without any units, and these should be shown. The same units should be used for every test in the report (or at least in the same suite). Test times are currently measured in milliseconds (using System.currentTimeMillis though, it would make sense to display them in either ms or s. However, it may also be worthwhile recording System.nanoTime *as we

Instead of writing tg.throwIf(tg.isNot(tg.isString)), it would be nicer to write tg.throwUnless(tg.isString).

• It would make sense (and greatly improve the 'testing flow') if .exists, .is, and .each could be chained to the .expr function:

await freddo('https://api.example.com')
      .status(200)
      .expr('.total_count').exists()
      .expr('.incomplete_results').is('boolean')
      .expr('.items.node_id').each(validator.isBase64)
      .ensure()