• 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: Georg Tuparev <email@hidden>
  • Date: Sun, 26 Sep 2004 15:24:22 +0200


On Sep 26, 2004, at 1:01 PM, Marco Scheurer wrote:

[I am sure this might sound like Knuth's Literate Programming - in retrospect I have to acknowledge that after Drew and I wrote the first version of our testing framework, I though that this is the closest practical way of doing literate programming for Cocoa]

I said that much when talking about a "formal specification".

In truth my point about writing tests first also has little to do with where they are implemented. You can of course start writing your class by writing the test methods. But it seems more natural to me to do so as an "outsider", the customer who specifies what the methods are supposed to do.

I hate split universes! It feels schizophrenic! If you by a book, you have the text and all illustrations together. Imagine how it will feel if they are separated in two books (three in the case of programming: sources, tests, documentation)... But when I separate all these three components, soon (after a month or so) I start feeling outsider.


Also I do not want to be an outsider to my own sources! Someone needs to be an insider after all. I also feel strong about (collective) code ownership, and I and my colleagues like to be proud about our craft. We cannot be proud for something we feel like outsiders. And emotions correlate strongly with productivity.

About your comment of "yet another do it simpler framework". You are right to suggest that every framework evolves and gets more complex with the time. The same will happen (already did) with our framework. But, it evolves in different direction. Our test analysis gets more sophisticated, and our UI nicer. But tests are just tests - very simple. They will not get more clever. There is no TestCase, or TestSuite , there is just no place where one can add bells and whistles.


Georg Tuparev Tuparev Technologies Klipper 13 1186 VR Amstelveen The Netherlands Mobile: +31-6-55798196

_______________________________________________
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: Marco Scheurer <email@hidden>)
 >Re: Unit testing framework suggestions? (From: Georg Tuparev <email@hidden>)
 >Re: Unit testing framework suggestions? (From: Marco Scheurer <email@hidden>)

  • Prev by Date: Dependency analysis warnings
  • Next by Date: Drawing a NSTextField bezel
  • Previous by thread: Re: Unit testing framework suggestions?
  • Next by thread: Re: Unit testing framework suggestions?
  • Index(es):
    • Date
    • Thread