MonkeyTalk/Jenkins CI setup
I was wondering if anybody has experience with the new MonkeyTalk http://www.gorillalogic.com/testing-tools/monkeytalk
So far I have been using it and I like it a lot for automation. I am having some issues getting it to talk with my jenkins Xcode slave machine correctly but I think those issues will be ironed out in a little time. The devs are fairly quick to respond to forum posts and have pushed out an update or two to the app since its release.
My question is kind of more theory based since I am fairly new to QA. When is it appropriate to run any sort of UI automation? Like is CI a good idea? Or regularly scheduled? Or should it depend upon the needs of the developers?
It seems like our apps are constantly evolving and weekly button labels may change or core UI functionality may change..so that is why I am asking the question. I am curious to see how other QA people do this sort of thing.
Also, does anybody have experience with GHunit? I am having some issues getting my report xml to write correctly.
My Setup so far is:
GHunit for iOS - Thru Jenkins CI
Junit for Android - Thru Jenkins CI
Monkeytalk for UI
A ton of actual device testing regularly.
Re: MonkeyTalk/Jenkins CI setup
CI is always a good idea.
I'm not very experienced in mobile, but UI tests tend to be slower and less parallelized. So a good thing to do is have it launch using a Jenkins slave to avoid tying up the build process waiting for your tests to complete. You may one to break it down into a set of smoke tests and have your regression scripts run in a separate job to get feedback as early as possible.