Note that there are some explanatory texts on larger screens.

plurals
  1. POTesting cocos2d iPhone using Calabash-iOS
    primarykey
    data
    text
    <p>Some people suggested <a href="https://github.com/calabash/calabash-ios" rel="nofollow">https://github.com/calabash/calabash-ios</a> for iOS tests. I am using cocos2d-iphone, can I write tests for it using calabash?</p> <p>Still calabash turned me off because it says it will only work with the simulator which is not enough and also if devices I have to use a service which just sounds like trouble. Any clean solution?</p> <blockquote> <p>After completing this guide you will be able to run tests locally against the iOS Simulator. You can also interactively explore and interact with your application using the Calabash console.</p> <p>Finally, you will be able to test your app on real, non-jailbroken iOS devices via the LessPainful service.</p> </blockquote> <p>Edit: <a href="https://github.com/calabash/calabash-ios/wiki/07-Testing-on-physical-iDevices" rel="nofollow">https://github.com/calabash/calabash-ios/wiki/07-Testing-on-physical-iDevices</a> suggests that device testing is possible... I guess I'll just have to try it myself...</p> <p>Edit 2: I did get it all working. Even hooking up to a remote device that is not even plugged into the computer (just needs to be on same WIFI). When hooking up to the device it helps using the UDID of the device, this was not stated on calabash-ios docs, or I missed that. For anyone coming here later, this is the final command that will work:</p> <pre><code>DEVICE_ENDPOINT=http://192.168.36.180:37265 BUNDLE_ID=build/tabeyou-cal DEVICE_TARGET=thelongudidofyourdevicegoeshere OS=ios6 cucumber </code></pre> <p>Just replace the ip to the ip of your device, the udid, and BUNDLE_ID which should be the target name (I think).</p> <p>My current question is, how would I identify cocos2d stuff like CCMenu, CCSprite etc? These all seem to support accessibility identifiers and I'm sure the Ruby-iOS part could find anything under the hood - in turn that should make it possible to write tests interacting with cocos2d elements.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload