incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CB-831) issue in mobile-spec in automated geolocation on iOS
Date Sat, 26 May 2012 01:16:23 GMT
Shazron Abdullah created CB-831:
-----------------------------------

             Summary: issue in mobile-spec in automated geolocation on iOS
                 Key: CB-831
                 URL: https://issues.apache.org/jira/browse/CB-831
             Project: Apache Cordova
          Issue Type: Bug
          Components: mobile-spec
    Affects Versions: 1.7.0, 1.8.0
            Reporter: Shazron Abdullah
            Assignee: Filip Maj


Thread originated by Becky: http://apache.markmail.org/thread/hgc7cpwoca6wl7rx

I don't know all of the nuances of jasmine yet,  but there is an issue in
the automated geolocation tests for iOS.  Specifically this section:

describe('watchPosition method', function() {

        var watch = null;

        afterEach(function() {

            navigator.geolocation.clearWatch(watch);

        });

There are two tests, one to test the error callback and one to test the
success callback for watchPosition.  What I see happening is that the first
tests runs and fails as expected.  The next test runs and calls
watchPosition.  Then, the clearWatch gets called (I assume for the end of
the first, fail case) with the CURRENT watch value.  Since we use the same
watch variable for each test, it seems that clearWatch is getting called
right after the second watchPosition and is passing in the id for that.
The clearWatch call does what it is supposed and clears the watchId out of
our internal list.  Since there is no longer a watchId, and the test times
out because there is no watchId to call back out to when location data
arrives from the sensor.   Make some semblance of sense?

I think the fix is to separate out the tests into two separate tests but
I'll let the Jasmine gurus take a look, please.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message