On 2008 Dec, 31, at 23:19, Kyle Sluder wrote:
You mean you have written an application and haven't been testing it
throughout?
Probable answer: Yes, life happens. People have also been known to
write applications without a detailed Test Plan in a detailed Software
Specification. :))
On Wed, Dec 31, 2008 at 5:01 AM, Matteo Manferdini
<[email protected]> wrote:
I came across the Cocoa scripting guide, and it seems the way to go,
but I wonder if it would not be better to write some code that fills
automatically the app instead of going through the guide to learn how
to make my app scriptable.
If you have plans to make your app scriptable someday, and your
release schedule allows it, then, sure, consider making it scriptable
now and use it to test -- I've dreamed of doing this.
Or use Kyle's idea of writing some kind of importer.
Although Unit Testing is not geared toward initial testing a new
application, since you had enough time to ask the question, reading
through this would probably help your decision-making process:
http://developer.apple.com/tools/unittest.html
Like Kyle said, there is no "correct" answer. It depends on your
situation. Just don't throw it over the cubicle wall to the Test
Department.
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
