• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Unit testing framework suggestions?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unit testing framework suggestions?


  • Subject: Re: Unit testing framework suggestions?
  • From: Marcel Weiher <email@hidden>
  • Date: Mon, 27 Sep 2004 00:40:23 +0100


On 26 Sep 2004, at 21:57, Georg Tuparev wrote:
On Sep 26, 2004, at 7:35 PM, Christian Pekeler wrote:

In my experience, for anything but trivial systems, these two class hierarchies are not an exact mirror of each other. Often times I have more than one test class per production class. These test classes test different aspects of the production class and usually have different setups. Sometimes I also have a testclass to test the interaction between certain production classes. And other timed I don't have a test class for a production class at all because I only test what could possibly fail and what requires me to do TDD.

If you read carefully my initial email, you would be surprised to discover that I am not saying that all test code should stay in the class being tested. But it is my experience, that this feels most naturally for about 70% of all cases. For these 70% of all tests, I do not want to be forced to use TestCase subclasses, because of reasons I explained in an earlier posting. For these 70% of the tests, it is also TSTTCPW to keep them close to the code they test, and this is a good thing!


If I have to chose between both extremes (xUnit - all tests re in TestCase subclasses, and Marcel's way - non of them is in a TestCase class) I would confidently choose MPWTestKit...

Too much honor heaped on me: MPWTest isn't nearly that extreme. It does allow, and I do use, completely separate test-classes. They are just rather rare, the majority of tests do not requie, and thus do not get, a separate class.


Cheers,

Marcel


-- Marcel Weiher Metaobject Software Technologies email@hidden www.metaobject.com Metaprogramming for the Graphic Arts. HOM, IDEAs, MetaAd etc. 1d480c25f397c4786386135f8e8938e4

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Unit testing framework suggestions? (From: Tim Hart <email@hidden>)
 >Re: Unit testing framework suggestions? (From: "M. Uli Kusterer" <email@hidden>)
 >Re: Unit testing framework suggestions? (From: Georg Tuparev <email@hidden>)
 >Re: Unit testing framework suggestions? (From: Marcel Weiher <email@hidden>)
 >Re: Unit testing framework suggestions? (From: Christian Pekeler <email@hidden>)
 >Re: Unit testing framework suggestions? (From: Georg Tuparev <email@hidden>)

  • Prev by Date: Re: Unit testing framework suggestions?
  • Next by Date: Re: Unit testing framework suggestions?
  • Previous by thread: Re: Unit testing framework suggestions?
  • Next by thread: Re: Unit testing framework suggestions?
  • Index(es):
    • Date
    • Thread