Difference between revisions of "Complete Test Procedure"

From MOD Wiki
Jump to navigation Jump to search
Line 14: Line 14:
 
* 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 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
 
* There are plugins in the store area
 +
 +
== 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

Revision as of 13:02, 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.

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

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