summaryrefslogtreecommitdiff
path: root/whatsnew-2.0.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2009-04-17 06:58:04 +0000
committerNick Mathewson <nickm@torproject.org>2009-04-17 06:58:04 +0000
commit2c4c294ed8168c3d9bea99d02896235cd8d7385f (patch)
tree606723d3a7a67316ef1c053ff9568db19f484b34 /whatsnew-2.0.txt
parent812800629b15c20c7d5fc15c6999c0df47136005 (diff)
downloadlibevent-2c4c294ed8168c3d9bea99d02896235cd8d7385f.tar.gz
note new unit test framework.
svn:r1191
Diffstat (limited to 'whatsnew-2.0.txt')
-rw-r--r--whatsnew-2.0.txt18
1 files changed, 18 insertions, 0 deletions
diff --git a/whatsnew-2.0.txt b/whatsnew-2.0.txt
index 91960ae7..28e3d78f 100644
--- a/whatsnew-2.0.txt
+++ b/whatsnew-2.0.txt
@@ -421,5 +421,23 @@ What's New In Libevent 2.0 so far:
TODO(nickm) writeme
+7. Infrastructure improvements
+7.1. Better unit test framework
+ We now use a unit test framework that Nick wrote called "tinytest".
+ The main benefit from Libevent's point of view is that tests which
+ might mess with global state can all run each in their own
+ subprocess. This way, when there's a bug that makes one unit test
+ crash or mess up global state, it doesn't affect any others.
+
+7.2. Better unit tests
+
+ Despite all the code we've added, our unit tests are much better
+ than before. Right now, iterating over the different backends on
+ my MacBook, I'm getting around 75% test coverage, compared with
+ less than 45% test coverage in Libevent 1.4.
+
+ (Right now, evdns.c has the worst test coverage of any significant
+ module, at 57%. If we exclude it from consideration, we're at 80%
+ test coverage, which is fairly good for a networking library.)