This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While prepping an answer for issue #8, I took a quick look at the current
cordova-plugin-meteor-webapp
testing approach. Unless I'm missing something (which is entirely possible!) it looks like the current tests haven't been run in quite some time, as the iOS tests specifically can't be run due to Swift compilation errors.To help with this, this PR addresses the following
cordova-plugin-meteor-webapp
/cordova-plugin-meteor-webapp-tests
issues:package.json
so the test plugin can be added as a separate plugin with modern versions of Cordova.after_plugin_install
call to reference theiosAddBridgingHeader.js
helper file as if it was part of thecordova-plugin-meteor-webapp-tests
plugin. Otherwise theiosAddBridgingHeader.js
file can't be found whencordova-plugin-meteor-webapp-tests
is added viacordova plugin add
.This PR also includes a new
DEVELOPMENT.md
file that contains detailed instructions outlining an approach for running thecordova-plugin-meteor-webapp-tests
iOS tests (using local checkouts to make debugging easier).The above being said, this PR does NOT address the failing iOS tests (38 out of 69 iOS tests are failing). It just adjusts the testing infrastructure so we can at least see the failing tests. I'll look into addressing the failing tests in a separate PR.
Fixes #8.
Thanks!