Some nightmares are worse than others. For me the worst kind, the
ones that wake me up at night are problems with no (obvious)
solutions. Among this category are random crashes in places where I
cannot use my debugging tools.
I have sometimes detected random crashes in my unit tests, some of
them were due to problems in the tools, or at least that is what I
always said to myself. Clean and rebuild to test, seemed to do the
work, and all the tests passed flawlessly, as always.
Well, maybe not! Since I migrated to Xcode 6, my unit tests were
crashing far more often than usual (4 out of 5 times). Sometimes even
cleaning the build (and I mean Cleaning the build folder)
didn't solve the problem. But still in some cases the tests passed
without any problems.
Last july, I was the instructor of the Ironhack for the Core Data
and Unit Testing week. One of my goals was teaching the students how
to do testing and write proper tests. Most of these students were
experienced developers, but even in that case it isn't for clear
everybody what to test.
This is the first post of the new version of my shiny new blog. My
purpose in this blog is to share knowlege with you about the things
that I do to make my business progress. But don't be scared! I don't
plan to make this a panel for new products or projects, but the
repository of the knowledge that I have gathered while improving my
business, both technical and otherwise.
I have recently started to implement user automation
Lists, as a prove of concept test for the applications I am
currently working on. I won't try to explain UI automation in this
article, since there are are some good sources available
Vollmer article or session 306 of WWDC10. Instead, I will
focus on some of the things that I stumbled upon.
Recently, I have finished a project for a customer. The project
enables the customer to publish a set of images as an application and
can be reused for other sets (creating a different application).
Although the customer is not a programmer both him and me wanted
him to keep the project and submit his application directly to the App
Store. That meant that I had to share a project with the customer that
he could change (the image sets at least) and he would create the app
and sign it to submit it to the App Store.
As you may already
is a methodology for iterative and incremental software development
that can improve both your product development cycle and its
results. I first heard about it about one year ago,
Kahn's talk for the spring 2009 edition of the well deservedly
famous iPhone Application Programming course that Stanford publishes
in iTunesU, and since then I have applied it to all my software
projects with very satisfying results. However, I had to do several
adaptations because Scrum is really meant for a group of people and
I develop software by myself.
Please be my guest and get to know how I apply Scrum for one.
I wrote this piece a while ago in my notebook, that I keep
in TiddlyWiki, but listening
to Jose's great series on Git
(in Spanish), I decided to share it with you in this blogger site that
I had created some time ago and never really used. If you like it, I
will try to publish more.
I use git for the version control of
my projects and although it isn't
news that Xcode 4 will come with Git integration, while Xcode 3.2 is
still the required version for submitting apps to the App Store, I do
want to enjoy the benefits of automatic version number generation in
my projects. If you do to, hope this
Zarra had previous versions that helped me to write this (Thanks
guys!). Read those too.