• 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: Some more questions on OCUnit.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some more questions on OCUnit.


  • Subject: Re: Some more questions on OCUnit.
  • From: Marco Scheurer <email@hidden>
  • Date: Sat, 14 Jun 2003 05:06:44 +0200

On Friday, June 13, 2003, at 03:35 PM, Poornima Ranganath wrote:

1] In a framework, I have 2 windows with Cocoa controls like Button,Sliders,Image View etc.
on click of these i need some functionality to be done.
these functions look like for eg:

-(IBAction)OnButtonClick:(id) sender ;
These Actions will take place only when i click on these controls.

Then what happens? What do you want to test? I think it should be possible to create a test case that will simulate a click on your button, but what should the result be?

The test case setup method could do the necessary things to bring your window up front, and then the test itself could look like:

- (void) testOnButtonClick
{
[button performClick:nil];
should (... something ...);
}


The test cases are run just on the build of the framework[choose Test build style].

So my UI and the targets cannot be tested using OCUnit is it?
so my question boils down to asking,
Can we write test cases in OCUnit to test such actions in a framework?

You need an application to run these UI tests. So if what your saying is that you can't simply test a framework with user interface widgets, you are right. You should link these frameworks in an application that can be tested.


2]In the link that u had suggested for UI testing there are no such controls used.

3] Also i am unable to use Shikenjo.Any framework opened does not get tested. if i run the Shikenjo project workspace, i get a lot of selector not recognized in the build console.

What are these errors specifically? I don't think these should happen but in any case, as I said previously, I wouldn't use Shikenjo to run tests. It was an experiment to use distributed notifications, and some of them are lost when they happen to fast, so it can happen that the main test suite does not complete. It's much better and easier to test from ProjectBuilder as described in the doc and the Stepwise tutorial.


Marco Scheurer
Sen:te, Lausanne, Switzerland http://www.sente.ch
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Some more questions on OCUnit. (From: Poornima Ranganath <email@hidden>)

  • Prev by Date: Re: array performance
  • Next by Date: Re: The more I read about MVC, the more confused I get...
  • Previous by thread: Re: Some more questions on OCUnit.
  • Next by thread: "-exec ..." in NSTask ?
  • Index(es):
    • Date
    • Thread