Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Test Scenarios #6

Open
hgn opened this issue Sep 5, 2017 · 1 comment
Open

Define Test Scenarios #6

hgn opened this issue Sep 5, 2017 · 1 comment

Comments

@hgn
Copy link
Member

hgn commented Sep 5, 2017

We should define test scenarios with the focus on limiting to a bare minimum and simultanously have all possible use cases covered.

I can imagine this:

static large network dense
static large network full

Where dense means a router has in average two, three direct neighbors. Full means 5, 10, 20 neighbors. Probably this is a parameter and the distance and the area is modifyable.

The number of routers within should be a parameter.

This topology is suited to analyse the routing message size for different topologies.

Based on this we can then analyse how the partial update performs. Right, for this static Scenarios the partial mode should perform superior.

Sidenote: we should design in the protocol a automatic that after n partial messages a full message SHOULD be send.

Based on this scenario we should add somehow dynamic characteristics

  • nodes disappear and appear. The number and random interval of disappearing and appearing nodes should be configurable
  • nodes should move somehow
@reisub-de
Copy link
Contributor

  • Randomized
  • meshed Square
  • circle with 2 neighbours each

See #5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants