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 has been archived by the owner on Aug 2, 2021. It is now read-only.
Implement multiple automated testing scenarios for correctness and performance using temporary kubernetes namespaces. Currently there is only smoke test scenario which uses a static swarm network and does uploads, syncing and downloads as separate phases. This is the most basic, but not very realistic scenario.
Investigate if simulation package can be used for automation and consider removing it into its own repository as it does not integrate with swarm and adds significant number of dependencies.
Network testing framework requirements:
heterogeneous nodes support
fault-models throughput/churn
economic simulations
Might be most feasible to do something like this after paper is for 80% finished.
The text was updated successfully, but these errors were encountered:
Implement multiple automated testing scenarios for correctness and performance using temporary kubernetes namespaces. Currently there is only smoke test scenario which uses a static swarm network and does uploads, syncing and downloads as separate phases. This is the most basic, but not very realistic scenario.
Investigate if
simulation
package can be used for automation and consider removing it into its own repository as it does not integrate with swarm and adds significant number of dependencies.Network testing framework requirements:
The text was updated successfully, but these errors were encountered: