status-im
/
cs-codex-dist-tests
mirror of
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
540 Commits 46 Branches 0 Tags 5.2 MiB
C# 99.1%
Shell 0.5%
Dockerfile 0.4%
Go to file
benbierens e0a734591f
Sets geth http and ws port to same number. 		2023-09-22 09:17:56 +02:00
.github/workflows updates ci command 2023-09-21 14:42:45 +02:00
Framework Merge branch 'master' into plugin-refactor 2023-09-21 11:07:27 +02:00
ProjectPlugins Sets geth http and ws port to same number. 2023-09-22 09:17:56 +02:00
Tests Cleanup 2023-09-22 07:43:46 +02:00
Tools/CodexNetDeployer Adds name to geth container 2023-09-21 14:48:41 +02:00
docker Pass a command during automated tests run (#65) 2023-09-19 17:53:15 +03:00
docs Updates the docs 2023-09-21 14:39:41 +02:00
.gitignore ADD Parallel download Tests 2023-04-19 12:34:46 +02:00
CONTRIBUTINGPLUGINS.MD Updates the docs 2023-09-21 14:39:41 +02:00
CONTRIBUTINGTESTS.MD Updates the docs 2023-09-21 14:39:41 +02:00
README.md Updates the docs 2023-09-21 14:39:41 +02:00
codexnode-manifest.yml Use codexstorage/nim-codex Docker images 2023-05-30 22:45:41 +03:00
cs-codex-dist-testing.sln Restores continuous test runner 2023-09-20 13:33:58 +02:00

README.md

Distributed System Tests for Nim-Codex

Using a common dotnet unit-test framework and a few other libraries, this project allows you to write tests that use multiple Codex node instances in various configurations to test the distributed system in a controlled, reproducible environment.

Nim-Codex: https://github.com/codex-storage/nim-codex
Dotnet: v7.0
Kubernetes: v1.25.4
Dotnet-kubernetes SDK: v10.1.4 https://github.com/kubernetes-client/csharp
Nethereum: v4.14.0

Tests/CodexTests and Tests/CodexLongTests

These are test assemblies that use NUnit3 to perform tests against transient Codex nodes.

Tests/ContinousTests

A console application that runs tests in an endless loop against a persistent deployment of Codex nodes.

Tools/CodexNetDeployer

A console application that can deploy Codex nodes.

Test logs

Because tests potentially take a long time to run, logging is in place to help you investigate failures afterwards. Should a test fail, all Codex terminal output (as well as metrics if they have been enabled) will be downloaded and stored along with a detailed, step-by-step log of the test. If something's gone wrong and you're here to discover the details, head for the logs.

How to contribute a plugin

If you want to add support for your project to the testing framework, follow the steps HERE

How to contribute tests

If you want to contribute tests, please follow the steps HERE.

Run the tests on your machine

Creating tests is much easier when you can debug them on your local system. This is possible, but requires some set-up. If you want to be able to run the tests on your local system, follow the steps HERE. Please note that tests which require explicit node locations cannot be executed locally. (Well, you could comment out the location statements and then it would probably work. But that might impact the validity/usefulness of the test.)

Missing functionality

Surely the test-infra doesn't do everything we'll need it to do. If you're running into a limitation and would like to request a new feature for the test-infra, please create an issue.