You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 12, 2018. It is now read-only.
The Clojure implementation has an extensive correctness test suite. Most of the tests look like:
install test schema;
transact a few assertions;
assert that datoms, transactions, or fulltext values table has following contents/new rows.
Since our SQL schema is identical to the Clojure implementation, it should be easy to move the input and output data into .edn files and write a generic test harness to do those steps.
It might be finicky to get the transaction IDs, timestamps, and other ephemeral data correct. I wonder if we can rewrite :db/tx and :db/txInstant in controlled locations to get what we want? (This could require reader syntax like #value [:db/tx] or similar.)
The Clojure implementation has an extensive correctness test suite. Most of the tests look like:
Since our SQL schema is identical to the Clojure implementation, it should be easy to move the input and output data into
.ednfiles and write a generic test harness to do those steps.It might be finicky to get the transaction IDs, timestamps, and other ephemeral data correct. I wonder if we can rewrite
:db/txand:db/txInstantin controlled locations to get what we want? (This could require reader syntax like#value [:db/tx]or similar.)