-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better testing of platform releases regarding plugin compatibility #54
Comments
The plugin tests (run on CI via We have the mobilespec project, but I am not exactly sure what that is and how it works. |
I just raised apache/cordova-mobile-spec#147 to document a few known quirks & issues:
|
and not all of the automatic tests are passing for me. It seems to help to select 1 plugin at a time to run the tests on. |
So
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This and apache/cordova-mobile-spec#184 (comment) imply that there are some other ways to test platform releases and maybe some other package releases that I don't know about. Can you enlighten me and others? |
That was the conclusion of us finding and understanding
The comment you link to is about plugin testing, not platform releases. But if you have such questions, please ask them in a new issue, Slack or dev mailing list thread and don't abuse one of my issues that has a clear topic or question - which is not about enlightening you. |
Step back: What would help to "test platform releases regarding plugin compatibility"? How can we find out if a new platform release breaks anything with plugins?
Other ideas? |
Could we maybe somehow compare what a plugin installation does between two platform versions? That could catch if changes in our "copy files from a to b" logic (that caused problems in the past) will break a plugin without executing its code. |
I will need some time to evaluate these ideas. I think more comprehensive testing would be good on major releases and occasional minor releases. I would really favor a more straightforward testing procedure for hotfixes and other patch releases. |
This exists: https://github.com/alsorokin/cordova-periodic-build-android (Take a look at the Travis build history) Broken right now, but could be a blueprint on how to create a repo that can test platforms with all plugins. |
The 7.1.3 release of cordova-android had a breaking bug with multiple plugins that included
app
in their name, including our owncordova-plugin-inappbrowser
.The cordova-android tests did not catch that.
We should figure out a way to better test our platforms with plugins.
The text was updated successfully, but these errors were encountered: