• 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: C++ TDD in xcode
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: C++ TDD in xcode


  • Subject: Re: C++ TDD in xcode
  • From: David Jeffery <email@hidden>
  • Date: Wed, 15 Dec 2004 23:19:41 -0800

Hi, Thad.

I've recently been looking at UnitKit, which seems to fit your needs exactly, other than the fact that it's an Objective-C unit testing framework, not a C++ one. It seems to have really nice Xcode integration, though; spits out messages to the build results window plus you can make your real target dependent on your unit test target, so the build will fail if your tests fail.

If you're not averse to playing with Obj-C, why not give it a spin and see what you think? You can grab it at http://unitkit.org, along with a short tutorial showing you how to put it to work. BTW, I'm in the same boat as you; professional programmer, but only using Xcode (and in fact Mac OS X) in my personal time. My day job has kept me busy using C++ ever since I started my career, so using Objective-C rather than C++ while playing on the Mac is somehow just more fun for me (plus there's all that Cocoa goodness to leverage).

David


On Dec 10, 2004, at 01:57, Thaddaeus Frogley wrote:

Hi,

I'm interested in trying out some Test Driven Development in xcode.

So, for instance, I have a project that has a static library target
(the main product), and I have created a test framework target (static
library) and a test client target (command line tool).  The test
client is dependant on both the test-framework, and the static library
that it tests (of course) but I'd quite like to have the test client
built and run as part of the over-all build process (perhaps an
aggregate target?), with it's output fed to the build results window
and have the build fail if the test suite fails.

Is anyone doing something like this already?  Can any of you give me
some advice on how to set this up?

Basically, I'd like to be able to set u a work flow where tests are
part of the normal build, and failures are treated as build failures.

FWIW I am a professional programmer, but I do not use xcode
professionally.  This is just a hobby/learning project.

Thad

-- Thaddaeus Frogley
http://thad.notagoth.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden


This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >C++ TDD in xcode (From: Thaddaeus Frogley <email@hidden>)

  • Prev by Date: Re: xcode only gdb error
  • Next by Date: Xcode 1.5 bug
  • Previous by thread: Re: C++ TDD in xcode
  • Next by thread: Nib file Locked?
  • Index(es):
    • Date
    • Thread