Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

ability to run standalone / custom reporter support #5

petejkim opened this Issue Jan 16, 2012 · 3 comments


None yet
2 participants

petejkim commented Jan 16, 2012

No description provided.

@petejkim petejkim was assigned Jan 16, 2012


nerdyc commented Aug 7, 2013

The custom reporter stuff is addressed now -- what is the relationship to 'standalone' specs?

I actually had need for running tests outside of OCUnit this afternoon. I couldn't find any way to profile tests to look for memory leaks under OCUnit. Does 'standalone' mean outside of OCUnit?


petejkim commented Aug 7, 2013

yeah that's what i meant, but i guess it's not very important... running it standalone also has other problems like needing its own app delgate etc..


nerdyc commented Aug 7, 2013

I actually think standalone tests would be worthwhile. I've used them in the past to create API integration tests for each version of an app. That way I knew if API changes would break older versions of the app.

Standalone tests can also be run within Instruments, which I've found really useful to find memory or performance issues from time to time.

@petejkim petejkim closed this Nov 10, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment