>
> Thanks for your detailed reply, and it help me a lot. I'm sorry to reply
>> so later , I was very busy yesterday.
>
>
>> After read the document of Cordova testing, I know that you have done a
>> really great work about test.
>
>
>> in Weex, we have also build some native Unit Tests in both iOS and
>> Android to check if individual pieces of code produce the expected
>> results.But as you know,in Weex,our users build their app by writing
>> javascript code, so Unit Tests is not enough.We need e2e/Integration
>> testing.
>
>
>> for example, I want to test if the animation works as expected.the
>> animation is (x+300,y+300,during=0.3s),
>
>
>> if we use js test-framework,we can easy to simulate user input. but we
>> can't get the animation result.(because we should compare the view's
>> properties with it's expected)
>
> if we use Native,we should firstly Create UIViewController/Activity and
>> then Simulate user input.
>
>
>> Correct me if I'm wrong.I have read the e2e test of cordova-ios and
>> cordova-android, the e2e-test only test if project is created successful
>> and project is builded successful. I'm curious how you designed a test
>> case like this.
>
>
>> After I read Sauce Lab document, I think maybe Sauce Lab is better
>> solution than Travis CI to run android emulator-based test case. It also
>> provide free resource for open source project and the sauce lab can
>> integrated into Travis CI.
>
>
>> can you tell me something about ARM android emulator in Sauce Lab, For
>> example, the stability and the speed at which test cases are executed. It's
>> very important to me.
>
>
>>
>
>> 1. Free to Apple For SauceLab: https://saucelabs.com/open-source
>
> 2. Travis CI with Sauce Lab:
>> https://docs.travis-ci.com/user/sauce-connect/
>
> 3. supported Android emulators:
>> https://wiki.saucelabs.com/display/DOCS/Supported+Android+Emulators
>
>
