COOP relies on a single Publisher gRpc service that relies on 2 backend services FactStatementStore and TxBuilder. All these service require a prelude of setting up and it would be quite reassuring to have tests implemented at the Publisher level.
Prelude FactStatementStore
Setup Sqlite db and run the gRpc service
Prelude TxBuilder
Setup the Plutip local cluster and initialize the entire COOP system followed by running a TxBulder
Run Publisher
Once the Publisher is active, we can write tests to ensure the entire stack works as intended:
Publishing a Fact Statement
Publishing a Fact Statement that has already been published
Publishing a Fact Statement that doesn't exist in the store
COOP relies on a single Publisher gRpc service that relies on 2 backend services FactStatementStore and TxBuilder. All these service require a prelude of setting up and it would be quite reassuring to have tests implemented at the Publisher level.
Once the Publisher is active, we can write tests to ensure the entire stack works as intended: