diff options
author | Luca Muscariello <lumuscar+fdio@cisco.com> | 2019-01-24 16:32:25 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@fd.io> | 2019-01-24 16:32:25 +0000 |
commit | 9fc2b9ec49c54ec2d5f0164bbedc1c78732c464c (patch) | |
tree | c7ebcf4c83b5c2f71318bc69c6f6915aaac7ae2a /longbow/README.md | |
parent | cada1143501a48effc483e3873596c22849926b5 (diff) | |
parent | 097e69e6daeefc84fd271babbdc1b47dfe4c01e5 (diff) |
Merge "Add support for ubuntu18.04 packages."
Diffstat (limited to 'longbow/README.md')
-rw-r--r-- | longbow/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/longbow/README.md b/longbow/README.md index 5da82a69..53accf64 100644 --- a/longbow/README.md +++ b/longbow/README.md @@ -24,7 +24,7 @@ development and xUnit style unit testing. Using LongBow's to aid an offensive-de of using its entry and exit assertions in your code. Similarly using LongBow's unit-test framework uses the same entry and exit assertions in the unit test cases themselves. The runtime assertions and the unit-test assertions work together in the unit test framework and do not conflict. This framework grew out of the need for a unit testing for -Test Driven Development on the CCNx Distillery software distribution. +Test Driven Development on the CCNx Distillery software distribution. Two other test frameworks were considered and used to develop unit tests: Unity and GoogleTest. Ultimately Unity was not used (although this framework is indebted to Unity for inspiration) mainly due to ease-of-use problems, and Googletest was not used mainly because it is a C++ framework, is not compatible with some features of C99, and is |