From ae46acf1c9a12138f9718211a9bbd9ba6a5ecdc4 Mon Sep 17 00:00:00 2001 From: philsquared Date: Tue, 21 Dec 2010 04:04:19 -0800 Subject: [PATCH] Updated What's the CATCH? (markdown) --- Catch-for-Objective-C.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Catch-for-Objective-C.md b/Catch-for-Objective-C.md index 9aad7d8..14e9963 100644 --- a/Catch-for-Objective-C.md +++ b/Catch-for-Objective-C.md @@ -3,9 +3,9 @@ CATCH stands for C++ Adaptive Test Cases in Headers and is a multi-paradigm unit test framework for C, C++ and Objective-C - coded entirely in headers. This page is presented from an Objective-C perspective. [[For the C++ oriented page see here|https://github.com/philsquared/Catch/wiki]]. -## Why do we need yet another Objective C Unit Test System? +## Why do we need yet another Objective-C Unit Test System? -Good question. In fact the working title for CATCH was YACUTS (Yet Another C++ Unit Test System) - followed, briefly, by NINJA CUTS ( NINJA CUTS Is Not Just Another C++ Unit Test System). +Good question. In fact the working title for CATCH was YACUTS (Yet Another C++ Unit Test System) - followed, briefly, by NINJA CUTS ( NINJA CUTS Is Not Just Another C++ Unit Test System). (CATCH is implemented in C++, hence the C++ bias in those names. The Objective-C bindings, however, give you a blend of the best that C++ and Objective-C have to offer). Although there are others, Objective-C unit testing is dominated by OCUnit - especially since Apple started bundling it. While OCUnit is a perfectly fine unit test framework, it has some limitations - and doesn't seem to be actively been developed. So what does CATCH bring to the party that differentiates it? Apart from a Catchy name, of course.