Files
memgraph/tests/e2e
andrejtonev 8b9e1fa08b Replication refactor part 6 (#1484)
Single (instance level) connection to a replica (messages from all databases get multiplexed through it)
ReplicationClient split in two: ReplicationClient and ReplicationStorageClient
New ReplicationClient, moved under replication, handles the raw connection, owned by MainRoleData
ReplicationStorageClient handles the storage <-> replica state machine and holds to a stream
Removed epoch and storage from *Clients
rpc::Stream proactively aborts on error and sets itself to a defunct state
Removed HandleRpcFailure, instead we simply log the error and let the FrequentCheck handle re-connection
replica_state is now a synced variable
ReplicaStorageClient state machine bugfixes
Single FrequentCheck that goes through DBMS
Moved ReplicationState under DbmsHandler
Moved some replication startup logic under the DbmsHandler's constructor
Removed InMemoryReplicationClient
CreateReplicationClient has been removed from Storage
Simplified GetRecoverySteps and made safer

---------

Co-authored-by: Gareth Lloyd <gareth.lloyd@memgraph.io>
2023-11-23 11:02:35 +01:00
..
2023-10-16 09:11:07 +02:00
2023-11-21 09:19:50 +01:00
2022-07-07 13:30:28 +02:00
2022-09-15 07:25:36 +02:00

tests/e2e

Framework to run end-to-end tests against Memgraph.

Notes

  • If you change something under this directory and below (even a Python script), make has to be run again because all tests are copied to the build directory and executed from there.
  • Use/extend run.sh if you run any e2e tests:
    • if all tests have to executed, use run.sh
    • if a suite of tests have to be execute, take a look under run.sh how to do so
    • if only a single test have to be execute, take a look at each individual binary/script, it's possible to manually pick the test