Wes Hardaker wrote:
Thomas> Interesting idea. However, a significant contribution to the
Thomas> slowness of the test suite currently is (also) the fact that
Thomas> we've implemented each test as being self-contained, so it
Thomas> involves a complete startup and shutdown of the daemons.
That's actually somewhat by design. Some things can be merged, but
the state that we didn't want to be in was having a previous test
break the next test... Thus the reason for the complete restart.
(the current test suite was actually designed in the beginning by an
ex-co-worker of mine and has been heavily rewritten since then
actually. He was an sh fanatic, can you tell?).
I fully understand. However, as the test suite grows (which it should)
we need to find the right balance between optimizing for speed vs.
independence. The latter (=current) approach won't scale well.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
