smocker-dev/smocker

Can we have MongoDB/Postgres to persist Mocks instead of file system

Opened this issue · 1 comments

Can we have MongoDB/Postgres to persist Mocks instead of file system

As many people are asking to use Smocker not as a testing tool but as a means of simulating missing services in a persistent environment. We plan to use an ORM to support both SQLite and Postgres to store sessions, mocks and histories.

Today we only use it as a volatile testing tool, and we want to keep this philosophy as much as possible.

This also explains a number of our choices, such as

  • Smocker must be able to start without dependencies.
  • Modifying a mock when it has already been called makes no sense, as it would make the call history inconsistent.