Anay
2c547e60f4
Inet framework
|
7 years ago | |
|---|---|---|
| .. | ||
| README | 7 years ago | |
| diffingerprints.py | 7 years ago | |
| diffingerprints.sh | 7 years ago | |
| ethernet-bus-reconnect.csv | 7 years ago | |
| ethernet-bus-reconnect.ini | 7 years ago | |
| ethernet-bus-reconnect.xml | 7 years ago | |
| ethernet-hub-reconnect.csv | 7 years ago | |
| ethernet-hub-reconnect.ini | 7 years ago | |
| ethernet-hub-reconnect.xml | 7 years ago | |
| ethernet-hub.csv | 7 years ago | |
| ethernet-hub.ini | 7 years ago | |
| ethernet-switch.csv | 7 years ago | |
| ethernet-switch.ini | 7 years ago | |
| ethernet-twohosts.csv | 7 years ago | |
| ethernet-twohosts.ini | 7 years ago | |
| examples-TODO.csv_off | 7 years ago | |
| examples.csv | 7 years ago | |
| external-tcpip.csv | 7 years ago | |
| fingerprints | 7 years ago | |
| gen_runallexamples.pl | 7 years ago | |
| manet.csv.unstable | 7 years ago | |
| multi.csv | 7 years ago | |
| multi.csv.unstable | 7 years ago | |
| runDefaultTests.sh | 7 years ago | |
| runWirelessTests.sh | 7 years ago | |
| showcases.csv | 7 years ago | |
| test-branch | 7 years ago | |
| tutorials.csv | 7 years ago | |
| voipstream.csv | 7 years ago | |
README
This folder contains fingerprint-based tests for various models.
When a fingerprint test passes, that indicates that with very high
probability, the simulation has followed the same trajectory as when
the fingerprint was recorded, i.e. the times and modules of the events
were the same. That is, a passing fingerprint tests means that the
simulation model logic works the same as before.
However, a passing test does not guarantee that e.g. result recording
has not changed.
Fingerprints are fragile to NED changes and parameter value changes.
When a fingerprint test fails, the simulation's correctness has to be
verified by some other means, and the fingerprints in the tests
updated.
When a fingerprint test passes, that indicates that with very high
probability, the simulation has followed the same trajectory as when
the fingerprint was recorded, i.e. the times and modules of the events
were the same. That is, a passing fingerprint tests means that the
simulation model logic works the same as before.
However, a passing test does not guarantee that e.g. result recording
has not changed.
Fingerprints are fragile to NED changes and parameter value changes.
When a fingerprint test fails, the simulation's correctness has to be
verified by some other means, and the fingerprints in the tests
updated.