• 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 01:46:22 +0200


On Sep 24, 2004, at 5:27 PM, James Bucanek wrote:

A-ha! Thanks, that makes a lot of sense. I knew there had to be some
obvious reason.

The documentation for UnitKit points out another reason why test classes are kept separate. Namely, the performance of an application directly impacted by the size of the code and data structures. Leaving your test code in your production code just makes for a bloated app.

Well, we did made measurement for our last two projects - depending on the application and on the computer, the performance deteriorates between 0% and 3% (on average 1%). Not worth discussing - specially because tests helped us often to have very good performance to start with.


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: James Bucanek <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