On 26/06/2009, at 2:04 , Ramakrishna Vavilala wrote:
I just finished converting (rewriting) a windows application to work
on Mac OSX. I made a package for my application. Now I want to test it
on a clean machine. In Windows I would normally create a clean Virtual
Machine and install the application to make sure that everything is
working properly on a clean machine.
What kind of strategy should I use to do same level of testing on a
Mac? Is buying another Mac just for testing the only other option? I
know that I don't need to worry about component dependencies/registry
settings like I do on Windows. But I don't want to use my dev machine
for testing. Are there any tricks involved in creating a test
environment?
If your application doesn't do anything funky with the system (ie, its
just a plain application, without making system level changes), then
one option is to just create a new user and use fast user switching to
test. You can create/delete new users as needed to test a clean
install - the only thing you'd need to do is remove it from the
Applications folder.
Otherwise, as suggested, a separate partition or separate harddisk or
separate Mac would be options if you need a really clean Mac. You may
need multiple partitions to test multiple OS versions (eg 10.5
and10.6). I keep around an old Mac that the kids use running the
previous OS for this purpose.
Peter.
--
Clipboard Switching and Macros with Keyboard Maestro
Keyboard Maestro <http://www.keyboardmaestro.com/> Macros for your Mac
<http://www.stairways.com/> <http://download.stairways.com/>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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 arch...@mail-archive.com
