Re: Unit Testing in XCode 3.2.3
Re: Unit Testing in XCode 3.2.3
- Subject: Re: Unit Testing in XCode 3.2.3
- From: Eeyore <email@hidden>
- Date: Mon, 29 Nov 2010 22:35:16 -0800
Haven't tried Hudson myself, although it has come up a few other times when I've been part of the conversation. I suspect Ricky (the author of the quoted email below) could give you some pointers on the installation and configuration.
Aaron
On Nov 24, 2010, at 5:20 PM, David Jackman wrote:
> Aaron and Eeyore,
>
> Thanks for the reply, I think that the best method of attack for me then with the final goal being automated testing of the application and continuous integration is to get that GH-Unit installed and working for me. that way i can start pushing tests into my code and integrate test driven coding practices into my new projects.
>
> This Hudson sounds interesting.
>
> http://wiki.hudson-ci.org/display/HUDSON/Installing+Hudson
>
> Im not sure where Mac OSX falls in their documentation, Was it difficult intalling and configuring Hudson? I use git right now but i am not against switching to svn. I think i recall something about the Xcode4 having integrated repos too; It would be nice they match.
>
> David
>
> On Nov 21, 2010, at 4:28 AM, Ricky Sharp wrote:
>
>>
>> On Nov 21, 2010, at 4:40 AM, David Jackman wrote:
>>
>>> Aaron,
>>>
>>> Thank you,
>>>
>>> I would like to do automated testing in the iphone simulator using iOS SDK 4 and Xcode 3.2.3.
>>> I would like to do both inspection of the views (application testing i think) and unit testing.
>>
>>
>> At my day job, we currently have the following setup:
>>
>> (1) Xcode 3.2.4 with iOS SDK 4.1
>>
>> (2) Hudson installed on our build machine and integrated with our SVN setup. This gives us continuous integration builds.
>>
>> (3) We struggled with the built-in testing (OCUnit aka SenTestKit) as well. So many things bad about that IMO. So, we use GH-Unit instead [1]. It allows you to do things like debug unit tests in the simulator as well as on devices and it has a slick UI to show passes/failures as well. You can even re-run specific tests using the UI to aid in debugging.
>>
>> It can also be run from the command-line and generates JUnit style XML output (which is then posted to hudson).
>>
>> (4) For ATs, we've been exploring iCuke [2]. There's some downsides to that though. For example, just as with Apple's automated testing implementation, your scripts are now bound to a particular language of your UI. For now, our app is US-English only so we'll run with it.
>>
>> At my home business though, I wrote my own AT infrastructure that is language-agnostic. So I can thus do runs against all five localized languages. This was key for me since each language has their own nib files. Simply testing the English UI would not cut it. I've been using this AT setup for the past nine years for both Mac OS 9/X and now iOS apps.
>>
>>
>>
>> [1] https://github.com/gabriel/gh-unit
>>
>> [2] https://github.com/unboxed/icuke
>>
>> ___________________________________________________________
>> Ricky A. Sharp mailto:email@hidden
>> Instant Interactive(tm) http://www.instantinteractive.com
>>
>>
>>
>
>
_______________________________________________
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