> *) Create a test suite that is able to store and retrieve the values
> for cwnd, RTO, RTT, bytes in flight, next tx, high tx, for different
> congestion control, different propagation delays and error rates. The
> objective is to have a base test with which we can test if an edit
> does modify something at the output level. The same simulation, right
> now, is not consistent between ns-3 versions, and often in a bad way
> (the previous versions work better, but have fewer features).

Branch tcp-test, based on tcp-warnings. I have introduced a SQLiteOutput class, different from the stats/sqlite-data-output one because it is more flexible, and have a system-wide mutual exclusion (so different processes can read/write on the same db without fearing of database corruption). I created a test that creates a lot of sub-tests, and for each execution takes the values outputted by the traces and saves them into an SQLite DB. The test is disabled by default because it takes a lot of time, and the resulting database occupies a lot of disk space. Once created, then it is possible to re-run the test and, ideally, the values should match.

[3] https://github.com/natale-p/ns-3-dev-git/tree/tcp-test