I started adding tests along with v0.5 and reached a good coverage in v0.6. Of course, I'll have to extend them to check if everything works in different scenarios.

## What's tested

So far, I've tested pgMemento mostly with workflows from one of my other projects, the [3D City Database](https://github.com/3dcitydb/). There, I'm importing 3d city models into a PostGIS-enabled database. The schema contains a lot of relationships between tables, even self-references. Thus, import and delete operations, for example, can cover multiple tables. Being able to revert such processes has been one of my major goals.

## What's open to test

I haven't worked with table inheritence or table partitioning, yet, so I can't tell if they impose some problems to the logging behaviour of pgMemento.