search

jkorell / iperf

Automatically exported from code.google.com/p/iperf
Other
1 stars 0 forks source link

Better testing procedures / test harness #127

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
It would be good to have some scripts, or at least a wiki page with a list of 
things to test, for each release.

Original issue reported on code.google.com by bltier...@es.net on 18 Dec 2013 at 10:42

GoogleCodeExporter commented 9 years ago 
Agreed.  Early on I did some unit tests but there wasn't much  added to them 
over time.  They're the t_*.c files.

However, I think it is hard to write a lot of unit tests for this kind of code, 
so some kind of harness to look for regressions would be good.

I haven't done any looking but it seems likely that we can find a tool to help 
with this.

Original comment by jdu...@es.net on 19 Dec 2013 at 4:46

GoogleCodeExporter commented 9 years ago 
Probably wouldn't be too hard to make a shell script that does a few localhost 
test runs. Use JSON output and do some minimal parsing to see if it's sane.

Original comment by jef.posk...@gmail.com on 19 Dec 2013 at 4:52

GoogleCodeExporter commented 9 years ago 
I added a script test_commands.sh as a starting point, but this really need a 
companion script to look at the JSON output and make sure it all looks right.

Original comment by bltier...@es.net on 20 Dec 2013 at 11:19