Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing is not a thing in the iOS and Mac community and that sucks. #37

Open
luisobo opened this issue Jun 11, 2013 · 5 comments
Open

Comments

@luisobo
Copy link
Owner

luisobo commented Jun 11, 2013

Nocilla is a testing tool. There is not enough testing in our community.

It's a shame, but automated testing is not a common practice in our community. On some other platforms testing is a given, but for some reason quality is not something we as a community seem to value in our apps, libraries or open source projects.

The present

The present state of our community is quite disappointing in terms of quality and best practices. Even the most popular libraries and open source projects lack of any quality or testing. Leaders in our field blog refer to unit testing as "cargo cult programming" rather than promoting it for the professional development tool that it is. It's only human nature to be scared of the unknown, but unit testing has been a widely accepted practice for years.

What can you do?

If you really want to discuss whether you should write tests or not, or what are the benefits of unit testing, please go back in time ten years. If you want to be a professional developer and write clean code that someone else can understand, use, and modify, unit testing is definitely a tool that will help you.

You can start by writing your first test. Just one. We have the tools as well as a few people in our community that actually care enough to spend their time developing those tools and sharing their knowledge for you and me.

  • Use Kiwi. There are other testing frameworks, this one is my favorite. Thanks Allen.
  • Read Jon Reid's blog qualitycoding.org with a lot of great material including screencasts. Thanks Jon.
  • There is plenty of good material out there, including some on why we should be writing tests in the first place. Go and read the literature.

Do really want to get your hands dirty? There are many open source projects out there without any tests. I dare you to submit a pull request with one single test to the open source project of your choice. The first test is always the most difficult.

The future

Apple just announced support for continuous integration in Xcode. It's definitely good to know that Apple actually cares about testing. But again, I don't think we have a problem with tools. We have a cultural problem that we need to fix, and that's something only we (you and me) can do something about. Go and spread the word. Add test coverage to your code, it will make your life easier. Add test coverage to open source projects, you will make someone else's life easier.

I dare you to close this issue.

@Abizern
Copy link

Abizern commented Jun 12, 2013

👍

@lqi
Copy link

lqi commented Jun 12, 2013

👍

@raphaeloliveira
Copy link

Thank you so much luisobo for this project. It helped me a lot in my tests. I used to test using this solution but it doesn't work anymore (at least with me).

@joshuatbrown
Copy link

Thanks for providing a solution to the problem of testing HTTP requests.

@vdaubry
Copy link

vdaubry commented Jul 12, 2013

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants