GitHub user jbondc opened a pull request:
https://github.com/apache/cordova-windows/pull/19
cordova run test + add common.js lib
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gdesolutions/cordova-windows CB-6204
Alternatively
Hi,
Right now, the work live in the cordova-labs repo under the CDVTest branch (
https://github.com/apache/cordova-labs/tree/cdvtest). Specifically, there
is a test plugin and test harness app. Its still a work in progress, and
while several of the API tests from mobile-spec were moved
Mocnymmo...@chromium.org;
Date: Thu, Oct 31, 2013 11:35 PM
To: devdev@cordova.apache.org;
Subject: Re: mobile-spec and releases: How do we test?
This is awesome progress, guys, thanks for the help.
I'm going to put all the bits together and compile a list of tasks left and
write-up
The recent e2e tests have serious issues on windows, too much for me to
consider jumping into right now, so instead of fixing them, I just added a
new test fixture.
If you want to run tests on windows, you can use :
$ npm run win-test
I have also added a runtime platform check
@cordova.apache.org
Objet : Test changes for windows cordova-cli
The recent e2e tests have serious issues on windows, too much for me to
consider jumping into right now, so instead of fixing them, I just added a
new test fixture.
If you want to run tests on windows, you can use :
$ npm run win-test
I have also
How about we remove the reliance on Device from these tests?
On Tue, Nov 12, 2013 at 5:36 PM, Joe Bowser bows...@gmail.com wrote:
Hey
I saw a recent commit on the Android repository removing what I left
in the test directory. While I agree that this probably shouldn't
have certain
Yes, manually invoking plugman locally to install the device plugin into the
test app is a cleaner way of doing that, IMHO. But does that also mean that
there should be a number of .gitignore entries in cordova-android/test so that
the after-effects of running plugman don't encourage folks
The removal should be just in JS. I'm OK with that.
On Wed, Nov 13, 2013 at 10:53 AM, Marcel Kinard cmarc...@gmail.com wrote:
Yes, manually invoking plugman locally to install the device plugin into the
test app is a cleaner way of doing that, IMHO. But does that also mean that
there should
Joe, how does this look?
https://github.com/cmarcelk/cordova-android/commit/88cb3e8d2ea0bc38a8dfa1eb124e943cc225e335
On Nov 13, 2013, at 1:57 PM, Joe Bowser bows...@gmail.com wrote:
The removal should be just in JS. I'm OK with that.
Done. Thanks for the feedback!
On Nov 13, 2013, at 2:59 PM, Joe Bowser bows...@gmail.com wrote:
Looks fine! Ship it!
Hey
I saw a recent commit on the Android repository removing what I left
in the test directory. While I agree that this probably shouldn't
have certain attributes because they're stale, I think that we should
use plugman to install the plugins, because in this case I don't have
my plugins
30, 2013 at 1:54 PM, Naik, Archana na...@lab126.com wrote:
Thanks Michal. You answered my questions.
More to elaborate on my question: I am testing amazon-fireos
port(platform) with all plug-ins using mobile-spec. I am seeing some
failures in 3.1.0 version because of test cases timing out
, Oct 30, 2013 at 1:54 PM, Naik, Archana na...@lab126.com wrote:
Thanks Michal. You answered my questions.
More to elaborate on my question: I am testing amazon-fireos
port(platform) with all plug-ins using mobile-spec. I am seeing some
failures in 3.1.0 version because of test cases
-ins using mobile-spec. I am seeing some
failures in 3.1.0 version because of test cases timing out. I am
pretty
new
to cordova and still in learning phase. :) I am trying to understand
these
failures. Interestingly they pass on 3.0.x version.
Archana
From: Michal Mocny
May you clarify?
Right now, there is no formal way to test plugins, we are trying to invent
that way now. Check out cordova-labs repo's cdvtest branch for a sample
app plugin to track progress.
Jasmine is hosted in that sample app, but plugins will not directly
know/care. Any testing
It's checked into master (not in 3.2.x branch yet until this issue below is
resolved).
Should I add it in the dependency plugin?
The problem is I have to add it as a url, not from a local repo (thus
install requires an internet connection).
This is because we can't switch to a branch _and_ a
if we had the cordova-plugins repo created, this won't be a problem. The
issue is not resolved yet: https://issues.apache.org/jira/browse/INFRA-6902
On Wed, Oct 30, 2013 at 1:38 PM, Shazron shaz...@gmail.com wrote:
It's checked into master (not in 3.2.x branch yet until this issue below
is
I'm not a very big fan of this sub directory business anyhow. Too many ways
to fail. It would be better, in my mind, if we aimed to always have one
repo equals one package.
On Wed, Oct 30, 2013 at 10:40 AM, Shazron shaz...@gmail.com wrote:
if we had the cordova-plugins repo created, this won't
On Wed, Oct 30, 2013 at 1:54 PM, Naik, Archana na...@lab126.com wrote:
Thanks Michal. You answered my questions.
More to elaborate on my question: I am testing amazon-fireos
port(platform) with all plug-ins using mobile-spec. I am seeing some
failures in 3.1.0 version because of test
The way we define dependencies is the problem. The plugin author is
currently responsible for defining explicitly the location of the plugin to
fetch, instead of just the idversion and letting the system do its job.
Andrew had a proposal in the past for a simple form of local plugin
repository
After discussing with shaz, seems there is no good solution which does not
involve action on the users' part, except to just be explicit about remote
url.
Instead, I think we are going to just remove the hard dependency, and have
those mobile-spec tests fail unless you manually install the
I'll add the check whenever someone goes to the Keyboard manual test page.
Will re-visit once the cordova-plugins repo is up.
On Wed, Oct 30, 2013 at 4:14 PM, Michal Mocny mmo...@chromium.org wrote:
After discussing with shaz, seems there is no good solution which does not
involve action
I just converted geolocation to the new test style [1]
I'm happy with the process overall, and I find the jasmine 2 tests are more
succinct.
There are a few things worth noting:
- I kept the eval code in. At google today, it was discussed that this may
not be the best approach.
- Jasmine 2: You
We are adding CLI and Plugman master to our continuous builds. That means I
will start getting nag emails whenever they break, and I will be sending
frowny emails to the authors of those commits.
Run the tests! It's easy, just run npm test, in either repo. They only take
a couple of seconds
Are the repeated
cp: no such file or directory: /some/path/www/config.xml
lines an expected part of the output? I saw them when I committed my last
changes, and so I checked out a couple of commits behind master and saw
that they still appeared. I committed my changes, figuring that at least I
They might be related to an error, they might not. Either way, they're a
bug that needs fixing because they're not supposed to be in the output.
Similarly for the handful of JSON blurbs inside the dots at the top.
Braden
On Thu, Oct 17, 2013 at 12:44 PM, Ian Clelland
I actually created an issue about cleaning up the tests yesterday evening.
https://issues.apache.org/jira/browse/CB-5106
I am planning on spending some time today and trying to get those failures
fixed. I also need to add some new tests.
On Thu, Oct 17, 2013 at 10:17 AM, Braden Shepherdson
I believe the failures are the result of promise additions. Some 'expects' will
have to wait.
The error I kept seeing is an attempt to shell.rm
Sent from my iPhone
On Oct 17, 2013, at 10:21 AM, Steven Gill stevengil...@gmail.com wrote:
I actually created an issue about cleaning up the
I fixed all the tests vigorously when I was making that refactoring. If
people have been adding lazy[1] tests similar to the ones I was fixing,
then they're not going to work.
[1] By lazy tests, I mean tests that are really testing async functions,
but only mocking things that are called
Yeah the windows8 tests were in a branch without promises, and did not exist
for you to vigorously patch.
Sent from my iPhone
On Oct 17, 2013, at 10:48 AM, Braden Shepherdson bra...@chromium.org wrote:
I fixed all the tests vigorously when I was making that refactoring. If
people have
function function(require, module, exports) { ... }. So there is
still runtime memory and CPU impact.
I support js-test-module tags or js-module ... test or whatever.
Similarly, prepare for tests. I realize we want to avoid tooling support,
but I think tooling support is a lesser evil than
=, asset mode=, etc etc
- More visually apparent when reading a plugin.xml file, akin to
platforms tag
The drawbacks seem to be:
- Not all descendant tags are easy to support for a given mode (ie,
dependency)
Summarizing the options currently discussed in this thread:
- new js-test-module tag
in this thread:
- new js-test-module tag. Not general enough solution to support tests
bundling assets, so -1 from me for this reason.
- mode=... attribute for a set of whitelisted tags (js-module, asset,
...)
- mode name=... tag for a set of whitelisted descendant
tags (js-module, asset
I might be able to create something new here.
What sizes and formats are needed? Would something short in duration work best,
or does it need to be longer than ~15 seconds?
On Oct 10, 2013, at 9:06 PM, Shazron shaz...@gmail.com wrote:
Added https://issues.apache.org/jira/browse/CB-5053
plugin tests in any which way, but
we
ship a
mobile-spec app which is one opinionated way to do so.
- It attempts to require the test module for each installed
plugin,
runs
them, and aggregates results.
- It could report results to some shared server, allow toggling
a
mobile-spec app which is one opinionated way to do so.
- It attempts to require the test module for each installed
plugin,
runs
them, and aggregates results.
- It could report results to some shared server, allow toggling
of
tests,
etc, but no plugin should know
TLDR; I've implemented a plugin testing strategy that requires 0 new
tooling features, can support non-core plugins, and hopefully even support
a variety of methods for running/reporting the test results. Super alpha
preview, but take a look if you like the direction!
NEW: CDVTest Plugin: https
The eval of the jasmine interface deserves mention. Is the motivation there
that tests can choose to use another testing framework? That's why you
don't just make jasmine functions globals?
One nit pick just from reading your email is that this will cause the test
js-modules to be injected
would need to depend on anything but CDVTest, and
not expect any globals. I guess, though, that CDVTest still expects the
app to provide to a test framework and some other stuff, so in the end its
no different. I was hedging on being able to update CDVTest in the future
for whatever we need, and all
the example didn't play properly on any browser that
I had access to at the time. (No sound, video didn't actually load,
etc).
It'd be good if we actually had a working video for this test and
other tests around the video tag. This might be a tall order, but
does someone want to try taking this on?
Joe
I guess we could use the old PhoneGap video. I think we should use this video:
http://www.youtube.com/watch?v=XI-fLgWOA4U
On Thu, Oct 10, 2013 at 10:17 AM, Shazron shaz...@gmail.com wrote:
What format would do for all the platforms - and size? h.264? Jesse donated
a test mp3 and its
:17 AM, Shazron shaz...@gmail.com wrote:
What format would do for all the platforms - and size? h.264? Jesse donated
a test mp3 and its on Apache's servers, don't think it will be a problem to
put a short video on there.
I suppose we could use http://www.youtube.com/watch?v=wOH4aGows40
wrote:
What format would do for all the platforms - and size? h.264? Jesse
donated
a test mp3 and its on Apache's servers, don't think it will be a
problem to
put a short video on there.
I suppose we could use http://www.youtube.com/watch?v=wOH4aGows40 if
it is
allowed (not sure the license
use
this
video:
Pigeons at Work http://www.youtube.com/watch?v=XI-fLgWOA4U
On Thu, Oct 10, 2013 at 10:17 AM, Shazron
shaz...@gmail.comjavascript:;
wrote:
What format would do for all the platforms - and size? h.264? Jesse
donated
a test mp3 and its on Apache's
, Oct 10, 2013 at 10:17 AM, Shazron shaz...@gmail.com
wrote:
What format would do for all the platforms - and size? h.264? Jesse
donated
a test mp3 and its on Apache's servers, don't think it will be a
problem to
put a short video on there.
I suppose we could use Introduction
think we should use
this
video:
Pigeons at Work http://www.youtube.com/watch?v=XI-fLgWOA4U
On Thu, Oct 10, 2013 at 10:17 AM, Shazron shaz...@gmail.com
javascript:;
wrote:
What format would do for all the platforms - and size? h.264?
Jesse
donated
a test mp3
:;
wrote:
What format would do for all the platforms - and size? h.264?
Jesse
donated
a test mp3 and its on Apache's servers, don't think it will be a
problem to
put a short video on there.
I suppose we could use Introduction to PhoneGap - An Open Source
:17 AM, Shazron
shaz...@gmail.comjavascript:;
javascript:;
javascript:;
wrote:
What format would do for all the platforms - and size? h.264?
Jesse
donated
a test mp3 and its on Apache's servers, don't think it will
be a
problem to
put a short video
, Shazron shaz...@gmail.com
javascript:;
javascript:;
wrote:
What format would do for all the platforms - and size?
h.264?
Jesse
donated
a test mp3 and its on Apache's servers, don't think it will
be a
problem to
put a short video on there.
I
FYI: https://github.com/w3c/web-platform-tests/tree/master/battery-status
Lisa Seacat DeLuca
ldel...@apache.org
to require the test module for each installed plugin,
runs
them, and aggregates results.
- It could report results to some shared server, allow toggling of
tests,
etc, but no plugin should know or care about those features.
Using that as a generic base:
- We ship a CDVTests
Hum I think keeping tests with the plugin is a better approach, keeps code
and test together on a single repo for a plugin.
Maybe plugman should not install the test folder located on the root of the
plugin by default unless an optional flag --test is pass
plugman install --test ...
cordova
(...) ).
- Will need a common way to describe/report results (others have
mentioned TAP).
- Any app is free to run those plugin tests in any which way, but we
ship a
mobile-spec app which is one opinionated way to do so.
- It attempts to require the test module for each installed plugin,
runs
which is one opinionated way to do so.
- It attempts to require the test module for each installed plugin,
runs
them, and aggregates results.
- It could report results to some shared server, allow toggling of
tests,
etc, but no plugin should know or care about those
Currently, the automated test system that we have running (derived from
Medic) uses only the mobilespec tests. It does not yet use tests collected
from the plugins. Its been talked about, but not gone anywhere.
David Kemp
On Wed, Sep 25, 2013 at 7:58 PM, Jesse purplecabb...@gmail.com wrote
What's the challenge of having us use the tests that come with the
individual plugins ?
On Thu, Sep 26, 2013 at 8:13 AM, David Kemp drk...@google.com wrote:
Currently, the automated test system that we have running (derived from
Medic) uses only the mobilespec tests. It does not yet use tests
I like the idea can we call mobilespec now cordova-voltron and be DRY and
use the tests form the plugins.
Voltron by itself creates an App that tests only core, but as you
use plugman to add plugins to voltron it has more test cases.
It would not be a bad idea to enhance plugin.xml in the future
Here's an off-the-top-of-my-head sketch of how we might do Voltron tests:
- Add a tag to plugin.xml that names each test file:
test type=automatic src=spec/foo.js name=Foo Automated /
test type=manual src=spec/bar.js name=Foo Manual /
- Add a new command, cordova test (maybe prepare-test
(...) ).
- Will need a common way to describe/report results (others have
mentioned TAP).
- Any app is free to run those plugin tests in any which way, but we ship a
mobile-spec app which is one opinionated way to do so.
- It attempts to require the test module for each installed plugin, runs
them
style?
This came up earlier, but I haven't found any fix that needed a
mobile-spec test. (Many that need native testing, like recursive file
copy, etc). Any thoughts?
Joe
, will there be scripts to assemble
mobile-spec all Voltron style?
This came up earlier, but I haven't found any fix that needed a
mobile-spec test. (Many that need native testing, like recursive file
copy, etc). Any thoughts?
Joe
Yeah, I have pushed some changes to mobile-spec, and when I did I also
copied the tests into the plugin involved.
Until we get the magic test runner happening, I think we just keep
duplicating.
@purplecabbage
risingj.com
On Wed, Sep 25, 2013 at 4:38 PM, Steven Gill stevengil...@gmail.com wrote
Confirmed. I get 715 fails
On Fri, Aug 30, 2013 at 4:45 AM, Shazron shaz...@gmail.com wrote:
Can someone verify my results? I noticed there were changes in the code for
CDVWhitelist.m, and I was trying to fix static analyzer errors and re-ran
the tests before and after I made the changes.
test *is* all native code.
On Fri, Aug 30, 2013 at 9:39 AM, Andrew Grieve agri...@chromium.org wrote:
My guess is that Ian broke these tests when he changed the whitelist to
behave the same way as Android's. He added whitelist unit tests to
mobile-spec, so likely these can just be deleted
My guess is that Ian broke these tests when he changed the whitelist to
behave the same way as Android's. He added whitelist unit tests to
mobile-spec, so likely these can just be deleted? Will let him confirm when
he gets in.
On Fri, Aug 30, 2013 at 9:16 AM, David Kemp drk...@google.com wrote:
afterwards.
I'll see what I can do to clean them up. I think I would like to keep some
of those tests in place, as the code under test *is* all native code.
On Fri, Aug 30, 2013 at 9:39 AM, Andrew Grieve agri...@chromium.orgwrote:
My guess is that Ian broke these tests when he changed
Anyone get this to work? I'm not seeing any test executions
On Fri, Jul 12, 2013 at 5:07 PM, Filip Maj f...@adobe.com wrote:
Anyone get this to work? I'm not seeing any test executions
No, it doesn't look like they're running right now.
They were running (though failing) for me earlier today, but I was on
commit 0c80083.
Bisecting between
It's probably something simple, but I've created CB-4194 to track it in
case its more involved.
On Fri, Jul 12, 2013 at 10:26 PM, Ian Clelland iclell...@chromium.orgwrote:
On Fri, Jul 12, 2013 at 5:07 PM, Filip Maj f...@adobe.com wrote:
Anyone get this to work? I'm not seeing any test
Hi devs,
I would like to understand better about the actual intent of the various
cordova test suites for v2.x.
(This question was already asked to PhoneGap Forum last week but got not
replies)
From what I can work out, the testing of cordova (for Android) is shared
between a number
On Thu, Jul 4, 2013 at 9:20 AM, Andrew Grieve agri...@chromium.org wrote:
Comments inline.
As are mine.
On Thu, Jul 4, 2013 at 3:27 AM, Smith, Peter
pet...@fast.au.fujitsu.comwrote:
Hi devs,
I would like to understand better about the actual intent of the various
cordova test suites
mean?
I just meant that none of the JUnit-style test cases have any direct
reference to the Java plugin implementations.
Anyway, I understand now that this seems deliberate:
* Andrew wrote: Omitted deliberately I think.
* Joe wrote: We test the API through mobile-spec, so we don't consider
I'm trying to understand the cordova-mobile-spec test case
contacts.spec.21 update a contact.
This test case clearly expects that saving over a contact email with an
empty string will remove that email.
But I didn't see any mention of this kind of functionality in the
cordova
Great question, I have no idea myself! My guess is the test is incorrect..
Looking into git blame, looks like that test code has existed for almost a
year and a half :s
I imagine instead of setting the email to the empty string, the second
email would be entirely removed.
On 7/1/13 11:17 PM
.
If that is not working then you should raise a bug:
https://issues.apache.org/jira/browse/CB
Simon Mac Donald
http://hi.im/simonmacdonald
On Tue, Jul 2, 2013 at 2:17 AM, Smith, Peter pet...@fast.au.fujitsu.comwrote:
I'm trying to understand the cordova-mobile-spec test case
contacts.spec.21
-js\pkg\cordova.test.js: SyntaxError: Unexpected
token .
SyntaxError: Unexpected token .
at module.exports.node [as action] (D:\work\cordova-js\test\runner.js:72:18)
at TaskBase.run
(C:\Users\blahblah\AppData\Roaming\npm\node_modules\jake\lib\task\task.js:220:21
.
**
error eval()ing D:\work\cordova-js\pkg\cordova.test.js: SyntaxError:
Unexpected token .
SyntaxError: Unexpected token .
at module.exports.node [as action]
(D:\work\cordova-js\test\runner.js:72:18)
at TaskBase.run
(C:\Users\blahblah\AppData\Roaming\npm\node_modules\jake\lib\task
Sorry to bother everybody with this test...
Giorgio
on our morning scrum call, Jesse made the excellent suggestion of unique
test id's for each unit test in Mobile Spec. This would allow us to
reference specific test cases when filing issues, and track these tests
between issues.
Would be implemented as a script which would insert unique
Presumably these would just be helper ids so we can easily jump to a
particular test, or verify if the same test is failing on multiple devices.
As tests get added, modified, there is a possibility that a particular test
changes context/meaning, which I don't think is a big deal.
Trying
Ok great - in the ballpark helper ids are better than nothing, definitely
On Thu, Apr 4, 2013 at 11:54 AM, Jesse purplecabb...@gmail.com wrote:
Presumably these would just be helper ids so we can easily jump to a
particular test, or verify if the same test is failing on multiple devices
Hello
It's the first time I'm building cordova-js and I'm running into a
problem related to symlinks.
jake test results in
generated platform: test in 286ms
error eval()ing C:\folder\cordova-js\pkg\cordova.test.js:
SyntaxError: Unexpected token .
SyntaxError: Unexpected token
test results in
generated platform: test in 286ms
error eval()ing C:\folder\cordova-js\pkg\cordova.test.js:
SyntaxError: Unexpected token .
SyntaxError: Unexpected token .
at module.exports.node [as action]
(C:\folder\cordova-js\test\runner.js:72:18)
The problem is caused by my windows
I spent all day on Windows today and I had the issue as well.
On Tue, Feb 26, 2013 at 2:05 PM, Jesse purplecabb...@gmail.com wrote:
Personally I ignore the jake test command, and simply use 'jake build'
Occasionally, I will run the 'btest'
Mobile spec is where I test, since it is running
since mobile-spec is now tagged 2.4.0.
Create Mobile Spec Test to benchmark ArrayBuffer exec bridge
Key: CB-2216
URL: https://issues.apache.org/jira/browse/CB-2216
Project
on BlackBerry 10 around test #200
-
Key: CB-2287
URL: https://issues.apache.org/jira/browse/CB-2287
Project: Apache Cordova
Issue Type: Bug
Components: BlackBerry
Affects Versions
Filip Maj created CB-2331:
-
Summary: Add tests for FileTransferError to test response body
Key: CB-2331
URL: https://issues.apache.org/jira/browse/CB-2331
Project: Apache Cordova
Issue Type: Sub
[
https://issues.apache.org/jira/browse/CB-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-2049:
--
Fix Version/s: (was: 2.4.0)
2.5.0
Moving to 2.5.0.
Remove test
of the errors - if
you comment out the last three tests in media, it should run okay.
https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;a=commit;h=d1b4a2002c48cd40aee55fc2ea6335fa5255b905
Mobile-spec freezes on BlackBerry 10 around test #200
.
Mobile-spec freezes on BlackBerry 10 around test #200
-
Key: CB-2287
URL: https://issues.apache.org/jira/browse/CB-2287
Project: Apache Cordova
Issue Type: Bug
Components
=cordova-blackberry.git;a=commit;h=5c3226f32fc8806d058bd05117f3f6b685032186
Mobile-spec freezes on BlackBerry 10 around test #200
-
Key: CB-2287
URL: https://issues.apache.org/jira/browse/CB
[
https://issues.apache.org/jira/browse/CB-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13569175#comment-13569175
]
Filip Maj commented on CB-2287:
---
Thanks.
Too bad it still freezes around test #190 :(
Where
://github.com/blackberry/BB10-WebWorks-Framework/issues/606
I guess we'll just have to wait till someone gets around to it. I'll be merging
in my fixes soon.
Mobile-spec freezes on BlackBerry 10 around test #200
-
Key
this is resolved and
we can run mobile-spec start-to-finish I will integrate BB10 + PlayBook into
ci.cordova.io.
Mobile-spec freezes on BlackBerry 10 around test #200
-
Key: CB-2287
URL: https
- in order to get the tests
passing and actually not crashing, we may have to take out the media api for
bb10 for now. Not the greatest solution, but I can't see how we can mobile spec
to even run with this bug.
Mobile-spec freezes on BlackBerry 10 around test #200
a redirect loop.
Have you pinged Gord about this? We should get someone at RIM take a look at
this ASAP.
Let's leave this issue open for now, and merge in your fix into master.
Mobile-spec freezes on BlackBerry 10 around test #200
[
https://issues.apache.org/jira/browse/CB-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj reassigned CB-2049:
-
Assignee: Filip Maj (was: Shazron Abdullah)
Remove test dependency on audio file on external site
object
is defined and see where that gets me.
Mobile-spec freezes on BlackBerry 10 around test #200
-
Key: CB-2287
URL: https://issues.apache.org/jira/browse/CB-2287
Project
-ios/pull/9]. Please
take a look. :)
FileTransfer spec test failing on iOS5
--
Key: CB-2235
URL: https://issues.apache.org/jira/browse/CB-2235
Project: Apache Cordova
Issue Type: Bug
.
FileTransfer spec test failing on iOS5
--
Key: CB-2235
URL: https://issues.apache.org/jira/browse/CB-2235
Project: Apache Cordova
Issue Type: Bug
Components: iOS
Reporter
601 - 700 of 742 matches
Mail list logo
