Wednesday, October 30, 2013

iOS Mavericks and XCode 5.0.1 was Apple showing arrogance and dominance in the mobile app market

I am still amazed at how Apple has showed complete arrogance and disregard for it's developer base by releasing XCode 5.0.1 and Mavericks just a few weeks after iOS7/XCode 5.0 initial release with several major changes in the OS and testing/development tools that are not close to working the same way as with the previous release.

Apple should have just waited (and not released 3 weeks ago) and called last week's OS upgrade Mavericks 7.0 and XCode 5.0, because iOS 7.0.2 and XCode 5.0.1 are a lot different (especially the way Instruments and Authorization internally works) than would be expected in a "dot" or "point" release, which is usually slated for unseen bugs or security fixes which do not require disruption to the previous upgrade.

Apple must have calculated the disruption that happened earlier this week and basically said: we don't care, because we are Apple, and you have to react to whatever we decide is going to happen.

It is clear that this was a message from Apple to it's development community: mobile is where most of the new product development is happening and we own this space, and you will do what we say and we will let you know information when we want to, and you will just have to scramble and deal with the consequences.

It was either disorganization or total arrogance, but I doubt it was the former. Apple is too smart for that.

I offer my never-ending Thanks and Appreciation to all of the 3rd party testing and development products that have to deal with Apple's arrogance in order to assist their respective communities in supporting the development of excellent and innovative products that help to sell iPhones and iPads because user want/need that app.

Ironic.

Tuesday, October 29, 2013

iOS Mavericks is a disaster for test automation developers

iOS 7 first update was disaster for us test automation developers.

Thanks Apple for, yet again, showing us test automation developers and software QA people how little you care about quality and testing of 3rd party apps depending on mobile technology stability.

Appium - broken
Instruments - broken (why ask permissions EVERY SINGLE TIME?)

It's amazing how a single "dot" release disrupted (and not in a positive way) every single test automation framework other than whatever weak, inferior test automation software was attempted in XCode 5.0.1 and Mavericks.

Saturday, October 19, 2013

Appium - the game changer that mobile application automated testers have been waiting for.

A few months ago,  I was introduced to Appium - an amazing mobile application testing tool for software testing professionals that have the incredible burden of being responsible for testing mostly Android and iOS mobile applications.

And I love it.

I think "love" is not an adequate word - It is what all software testing professionals have been waiting for for years: An easy-to-use, robust, powerful, silver bullet that allows me to rapidly create tests for mobile applications on any platform that I used to have to write (for iOS) Objective-C (which is really stupid) and Java activity proxy (which is slow and cumbersome) in the programming language that you choose.

In my case, I love Java. So...... I created an entire automated tests suite for iOS and Android mobile applications using, for the most part, the same codebase - in Java!

Follow this amazing project on twitter at @AppiumDevs. Thanks guys! Finally, someone got it right.

Buh-bye Objective-C. Buh-bye Calabash. We dont need you anymore, but thanks for playing :)