I think it would be a good idea to start a list of test plans to run though a plugin before releasing it.  Here is a list that i've started and going to use before releasing any new plug-ins or major changes to current ones.

 

 

• Install plug-in from a clean boot with internet conectivity
  
• Install plug-in from a clean boot without internet conectivity
  
• Upgrade plug-in (if an upgrade)
  
• Reboot after plugin is installed/configured and tested working with internet conectivity
  
• Reboot after plugin is installed/configured and tested working without internet conectivity
  
• Start/Enable plugin 2x (if function exists) and ensure/test that start/stop is actually successful each interval
  
• Test installing any files to /mnt/user/.... (I have seen some programs not work with this path, ie DropBox using symbolic links)
  
• Test installing any files to /mnt/cache/....
  
• Test installing any files to /mnt/disk1/....
  

 

 

The reason why testing without an internet connection will determine if the plugin will hang the system (usually web interface) if there was no internet connection.

 

 

SeeDrs

 

SeeDrs,

 

How does one gracefully recover from no Internet connection (more than just listing an active connection as a requirement) if e.g. the download mechanism is handled by the installplg command?  I'm asking about things like the files specified in the "file" tag.  Should we be doing e.g. wget after checking connectivity from the install/update cleanup script instead?

 

Thanks!

SeeDrs,

 

How does one gracefully recover from no Internet connection (more than just listing an active connection as a requirement) if e.g. the download mechanism is handled by the installplg command?  I'm asking about things like the files specified in the "file" tag.  Should we be doing e.g. wget after checking connectivity from the install/update cleanup script instead?

 

Thanks!

 

An example of where an no internet connection issue is with the dropbox plugin.  Say you dont have internet connection while you are enabling the service and its the first time the service is being enabled.  The plugin needs to download more components when starting for the first time.  In this case it will cause a hang because the install script never finishes because of this issue.

 

 

It also helps determine if an internet connection is required just for initial install and not required after that since it could be possible to have an unraid instance that is not connected to the internet, or the internet is not available when a reboot is required.