Replies: 10 comments 7 replies
-
There is an Issue under OpenCPN/plugins related to this topic which will be closed at some point. It is linked to here for reference Plugin Testing There is also a Cruiser Forum Opencpn topic Volunteer Plugin Testers Needed! |
Beta Was this translation helpful? Give feedback.
-
Hello, This is my first post and I expect it to be at the right place. WeatherFax from Beta catalog test on Win11:
WeatherFax from Beta catalog test on Debian Bullseye/11 rpi:
Can't wait to test new version of WeatherRouting which is failing (also crashing OpenCPN itself) each time I try to use it (as well on Win11 as on Debian Bulseye11 rpi) Hope it helps |
Beta Was this translation helpful? Give feedback.
-
Thank you. This has been a moving target. I am sorry. The old version got rewritten by newer ones, due to background stuff happening. My apologies. Will advised. |
Beta Was this translation helpful? Give feedback.
-
Ok, we have a new vesion Weatherfax 1.9.32.1 in the Beta Catalog. If there is trouble with Image Wizard popping up instead of just automatically finding the proper coordinates and overlaying on charts., then you need to Opencpn and to remove the old coordinateSets.xml from your user directory (not the installation directory, which has the new coordinateSets.xml.) Then startup of OPenCPN and the Plugin should cause the new coordinateSets.xml file to be copied to your user directory where it is normally read. If you are having trouble with this, let me know. We have some fixes in mind to mak this better. Thank you for testing! It is a vital part of having good working plugins. |
Beta Was this translation helpful? Give feedback.
-
Alrocharari Thanks for your thorough spreadsheet report. I see that "armhf debian bullseye/11 gtk3 rpi" plugins Beta Catalog is empty except for WMM. As Dave notes: "All" should be the target, but reasonably one should prioritize on the platforms that are known to be in high demand. (Windows, MacOS, ubuntu focal/20.04, rpi armhf, rpi arm64, Android, debian buster/10, debian bullseye/11.)" For Weatherfax we need "Basic Testing" done as described briefly in the OpenCPN Plugin Testing Spreadsheet "Instructions" Tab Also the Internet Retrieval URL's have all been updated by Ozolli and should it should be confirmed that the weatherfax overlays work as expected. Report any specific problems. I have not found any yet. Confirm that you can Retrieve > Update Data. Do we need a confirmatory message on completion? Do we need a prompt "Copy installation CoordinateSets.xml over the user version? Yes No" |
Beta Was this translation helpful? Give feedback.
-
Thank you Alrocharari , we are noting your reports and have reffered them to the team. |
Beta Was this translation helpful? Give feedback.
-
Would all test volunteers please try
We are particularly interested in testing of the flatpak builds! For weatherfax_pi we suggest you uninstall weatherfax first, close opencpn. Then determine that your opencpn user writable directory does not have an opencpn/plugins/weatherfax directory. Then go ahead and install the new version. Please report the results of your tests in the Testing Spreadsheet or in the Cruiser's Forum Weatherfax thread or the Weather_routing Thread Thank you! We depend on your reports to confirm operation of these plugins! |
Beta Was this translation helpful? Give feedback.
-
We need the beta version of watchdog tested. https://www.cruisersforum.com/forums/f134/watchdog-plugin-150313.html#post3674963 Watchdog 2.4.45.2 master-chg2sean -fix divergence in branch and add Pypilot. |
Beta Was this translation helpful? Give feedback.
-
There is no PR pending for OCPN plugins. |
Beta Was this translation helpful? Give feedback.
-
Yes, that is correct. You accepted it. Very Sorry about that. |
Beta Was this translation helpful? Give feedback.
-
###The Problem:
The problem is that we will release a new version of the Testplugin Template or even ShipDriver Template, then try building all the OS metadata and tarballs for one of the plugins and simply hope that all the OS work, because we do not have the means or equipment to test them all.
Then it gets worse, we think they are working, and build all the rest of the plugins using the new template. Then the reports dribble in, first Flatpak arm64 is failing. So we fix that and rebuild all the plugins. Then we find out another OS build is failing. What are we going to do, rebuild all the plugins again? No. We are going to remove all the plugins for that OS.
The Start of a Solution
Develop a reliable testing program. Taking it one step at a time.
When Jon releases a new Testplugin Template he pushes the commit to testplugin_pi and increments the version. https://github.com/jongough/testplug...commits/master
When he pushes the commit that starts a Circleci build process which should create all the necessary metadata and tarballs for all the currently supported OS which are deployed to Cloudsmith and stored there in
https://cloudsmith.io/~opencpn/repos...prod/packages/ and sometimes in the testplugin-beta repository. He may even add the results to the Plugin Manager "beta" catalog.
When this is done, the first thing we need is for all testers to download their OS version of the testplugin tarball and use the Options > Plugins > "Import Plugin" feature (or use the beta catalog) to test the installation, enabling, preferences, menus and general operation of the plugin making sure OpenCPN does not crash, in a reasonably timely manner.
Once we are reasonably certain that the new template is working for all OS, I will, over a period of weeks, update all of Sean's plugins, plus some others, pushing them to github and deploying to Cloudsmith. Each plugin will then be added to the Plugin Manager "Beta" catalog for testing by all the OS Testers. We will want you all to test the results on your OS and report back in a timely fashion.
Then the plugins will be added to the PIM master catalog.
Thus we will avoid needless extra and repetitive work. If there are any ideas or suggestions to improve this process please write below. Thanks.
I do hope other volunteers will commit to this testing process.
Needs
Alerts: We need a good way to alert all volunteer testers that there is a new plugin test needed and what plugin which will be located on the beta catalog.
Sign off: We need a good method of registering and keeping track of volunteer testers results, all in one central location that everyone can quickly view. Ideally I would like a form listing the plugin all OS that testers could use to sign off on a plugin.
Problems: If there is a problem they can use the plugin's Issues to report.
Beta Was this translation helpful? Give feedback.
All reactions