featurebase/internal/clustertests
Souhaila Noor 7983a7506f - Need to get code coverage on the server and client side
- For server side, used an instrumented binary with a test that wraps around the main entrypoint for featurebase
- Every time, the binary is called, a new coverage file is generated.
- For the client side, used the standard -coverprofile flag for go test to generate code coverage
- For backup test that's expected to fail, needed to call Run call in backup.go directly. The code coverage is not written to disk for an instrumented binary if there is an error.
2022-02-11 11:26:00 -06:00
..
fakeidp fb1172: enable refresh tokens 2022-02-07 13:42:11 -06:00
testdata fb1172: enable refresh tokens 2022-02-07 13:42:11 -06:00
cluster_test.go - Need to get code coverage on the server and client side 2022-02-11 11:26:00 -06:00
docker-compose-replication2.yml remove unnecessary port bindings 2022-01-24 16:29:12 -06:00
docker-compose.yml - Need to get code coverage on the server and client side 2022-02-11 11:26:00 -06:00
Dockerfile-fakeIDP fb1172: enable refresh tokens 2022-02-07 13:42:11 -06:00
pause_node_test.go remove http subpackage and bring implementations into core 2022-02-03 21:04:04 -06:00