summaryrefslogtreecommitdiffstats
path: root/longbow
diff options
context:
space:
mode:
authorMauro Sardara <msardara+fdio@cisco.com>2017-04-07 10:25:26 +0200
committerMauro Sardara <msardara+fdio@cisco.com>2017-04-07 08:28:40 +0000
commit72462a4971319d354c00b5b3305ad2aeb558664b (patch)
tree6c1e277cc390d6f8c9802e9ad709a466cbfbdae2 /longbow
parent7290b8411c9ba7f4758be8a50d353414382d1d62 (diff)
Removed useless space
Change-Id: I4b39ddf5426d95b1d079cbe7d4852bded0223dc9 Signed-off-by: Mauro Sardara <msardara+fdio@cisco.com>
Diffstat (limited to 'longbow')
-rw-r--r--longbow/README.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/longbow/README.md b/longbow/README.md
index 01d46075..5da82a69 100644
--- a/longbow/README.md
+++ b/longbow/README.md
@@ -19,15 +19,15 @@ $ make install
## Introduction ##
-LongBow is a C language software framework that combines the fail-fast philosophy of an offensive-stance of program
-development and xUnit style unit testing. Using LongBow's to aid an offensive-development stance is largely a matter
-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
+LongBow is a C language software framework that combines the fail-fast philosophy of an offensive-stance of program
+development and xUnit style unit testing. Using LongBow's to aid an offensive-development stance is largely a matter
+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.
-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
+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
difficult to use.
## Using LongBow ##