From 1ab03bdef19a8315c86db441b456ff14dbfb0cfb Mon Sep 17 00:00:00 2001 From: shiqian Date: Thu, 3 Jul 2008 20:54:31 +0000 Subject: [PATCH] Edited wiki page through web user interface. --- wiki/GoogleTestPrimer.wiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/wiki/GoogleTestPrimer.wiki b/wiki/GoogleTestPrimer.wiki index f53bfafe..b6e29cee 100644 --- a/wiki/GoogleTestPrimer.wiki +++ b/wiki/GoogleTestPrimer.wiki @@ -19,7 +19,7 @@ So what makes a good test, and how does Google C++ Testing Framework fit in? We # Tests should be _fast_. With Google C++ Testing Framework, you can reuse shared resources across tests and pay for the set-up/tear-down only once, without making tests depend on each other. Since Google C++ Testing Framework is based on the popular xUnit -architecture, you'll feel right at home if you've used JUnit or PyUnit before. +architecture, you'll feel right at home if you've used JUnit or !PyUnit before. If not, it will take you about 10 minutes to learn the basics and get started. So let's go!