Configure CI process performing a HafAH sync and test
- We can assume that somewhere is already synced HAF instance (Postgres database access url should be a CI spawn parameter). This source database should exist on the same Postgres instance used by CI process.
- Because HAF database is written by the app, it should be copied first using a name specific to tested branch
- Next application sync and server spawn should be perfomed (similary to Hivemind testing step)
- On spawned server set of pattern based Account history API tests should be started. CI shall fail on any difference.
- Produced database should be left for some time (i.e. 1 month). We should consider to define auto-cleaning job.
As a sidenote, I propose to prepare this process as a parametrized docker image. It should be defined to allow simple reuse in the other apps CI processes (i.e. balance_tracker).