This week I spent time looking at UI Testing using iOS 9 and XCode 7.
I'm not going to go through the details but I did find these two links to be good enough to get going.
The first one is a little light on the details but I found it useful in giving simple steps for adding UI testing to an existing app.
The second one, I thought, did a better job of showing how to actually assert test results once you got everything up and going.
So what was my intent with this and why should I take the time to add this to my current project(s)?
Well to be honest, it didn't take more than about 30 minutes to read the articles and get going. I did do a test project prior to adding to my existing production, or to be production, apps.
For the conversion to Swift of Pain Logger I see this as an invaluable tool to verify that once I switch a view controller over it still works as it did before.
For my "in work" app I see adding this functionality now as a way of validating and protecting from regressions in the future.
In short, setting it all up, and running the first tests was fairly simple, and I think will be a valuable tool in the tool chest.
I spent most of my time diving into ReactJS this week. There is a lot to learn here and I'm not convinced it is the right tool for the web app I am building. Time will tell. One thing I find hard is finding good training on the subject. If anyone knows of good sources for this, particularly when using with Ruby on Rails, please pass them along.
There are a few articles, and I have probably read them all, but like most things, especially in the UI world, lots of folks have their opinion on how it should be done, with each one having different tradeoffs. More investigation is needed.
Till next week.
No comments:
Post a Comment