Difference between revisions of "Complete Test Procedure"
Jump to navigation
Jump to search
Line 29: | Line 29: | ||
NOTE: Do not uncheck the stable filter. | NOTE: Do not uncheck the stable filter. | ||
We don't care if unstable plugins are not installable. | We don't care if unstable plugins are not installable. | ||
+ | |||
+ | === Update all plugins === | ||
+ | |||
+ | Preparations needed: | ||
+ | * Install all plugins (see previous step) | ||
+ | * Make all plugins releaseVersion 0, by running: | ||
+ | <code> | ||
+ | TODO | ||
+ | <code> | ||
+ | |||
+ | Test can now begin: | ||
+ | * Open the mod web interface | ||
+ | * Make sure there are all plugins installed (compare local number to store number) | ||
+ | * Go to the store and click to update all plugins | ||
== mod-os == | == mod-os == |
Revision as of 14:05, 22 July 2016
This page describes a complete test procedure for the MOD Duo. This includes testing both hardware and software, as much as possible.
Contents
mod-ui
Loading initial contents
- http://192.168.51.1 web page loads
- Page redirects to have '/?v={{version}}' suffix
- "Loading pedalboard..." animation appears and stops
- There are plugins showing up in the plugin bar
- There are pedalboards in the pedalboards section
- The pedalboards section includes a 'Default' pedalboard, which cannot be deleted
- There are banks in the banks area (if there's none please create one and add the default pedalboard, then re-open the banks section)
- There are plugins in the store area
Install all plugins
Preparations needed (delete all plugins):
- Delete ~/.lv2/ folder
- Reboot or restart mod-host and mod-ui services
Test can now begin:
- Open the mod web interface
- Make sure there are 0 plugins installed
- Enable Dev mode
- Go to the store and click to install all plugins
NOTE: Do not uncheck the stable filter. We don't care if unstable plugins are not installable.
Update all plugins
Preparations needed:
- Install all plugins (see previous step)
- Make all plugins releaseVersion 0, by running:
TODO
Test can now begin:
- Open the mod web interface
- Make sure there are all plugins installed (compare local number to store number)
- Go to the store and click to update all plugins
mod-os
automatic upgrade
Preparations needed to force an update:
- Edit /etc/mod-release/release and replace its contents with "v1.0.0" (without quotes)
- Delete /etc/mod-release/system file
- Reboot or restart mod-ui service
Test can now begin:
- Open the mod web interface
- A small popup on the bottom-right appears saying a required update is available
- A small notification on the top-right appears saying there's an update available
- Click download and wait
- A browser confirmation window appears asking if you want to update now
Test branch #1
- Click yes, update starts immediately
Test branch #2
- Click no, update does not start
- Load a random pedalboard, still works
- Open the update popup and click to upgrade now. it starts immediately