Unit Testing

[lehitoskin]

Much of Ivy's code is untested. The libraries have their own tests, so that functionality isn't going to be in the scope of this issue. What does need to be tested, however, is the consistency and functionality of the database and embedding functions. This will require creating (or reusing generated) images and a database.

I'm thinking something like the following:

ivy/test/
↳ test-embed.rkt
↳ test-db.rkt
↳ test-img # (every extension embed.rkt can handle)

[IonoclastBrigham]

This is timely. I don't know if it's a new thing, or if it's a problem that's existed for a long time and my last PR simply makes it more obvious, but I seem to have hundreds of images where the XMP and DB are out of sync.

Possibly related to issues with "Rename Tag" not actually grabbing everything.