Music Testing Checklist

in order to standardize the way we test our software I'm creating this QC checklist to be used when evaluating pull requests and while stabilising for release. This list is by no means exhaustive and I value further contributions - Nine-H

Function:

• does the app build correctly?
• does the app start without warnings?
• does the app close without warnings?
• can I import my music?
• can I delete music?
• does the app function when factory reset?

#!/usr/bin/env sh
# reset.sh
# erases the database, cache, and resets settings of music
# nine 2018.02.07

rm -rf ~/.cache/noise
rm -rf ~/.local/share/noise
gsettings reset-recursively io.elementary.music.equalizer
gsettings reset-recursively io.elementary.music.saved-state
gsettings reset-recursively io.elementary.music.settings

Playback:

• can I play a file?
• can I seek?
• can I advance to the next track?
• can I play the previous track?

Playlists:

• can I create a playlist?
• can I add a file to the playlist?
• can I add multiple files to the playlist?
• can I create a smart playlist?
• do all smart playlist rules save correctly?
• are playlists being saved when I kill and restart the application?

Views:

• is art being loaded correctly?
• is art displayed correctly?
• does sorting work as expected?