Merge lp:~sakrecoer/ubuntu-manual-tests/bug-1538228 into lp:ubuntu-manual-tests

[Set Hallstrom]

[lp:~sakrecoer/ubuntu-manual-tests/bug-1538228]

329. By Set Hallstrom on 2016-02-01

Fixing the Qsynth testcase with a given ID number (1675_Qsynth), removing the one without ID

[Kev Bowring (flocculant)]

review: Approve

=== modified file 'testcases/packages/Studio/1675_Qsynth'
--- testcases/packages/Studio/1675_Qsynth	2015-12-16 20:45:48 +0000
+++ testcases/packages/Studio/1675_Qsynth	2016-02-01 17:28:09 +0000
@@ -1,22 +1,44 @@
-This is a template for a test that will check that Qsynth works.
-This text should be a short description of the test.
-<strong>Write here any prerequisites before starting the test.
-</strong>
-<dl>
-    <dt>Action 1</dt>
-        <dd>Expected result 1</dd>
-    <dt>Example Action: Click on "File" and "Open Files"</dt>
-        <dd>Example Result: A window opens, asking for a file to select</dd>
-    <dt>Keep adding actions in "dt" fields</dt>
-        <dd>Keep adding expected results in "dd" fields</dd>
-</dl>
-
-Add another test for Qsynth here.
-<strong>Add another prerequisite here.
-</strong>
-<dl>
-    <dt>More actions</dt>
-        <dd>More expected results. Note: Make sure you keep the following "strong" text at the end</dd>
+This test will check if Qsynth opens properly from the FAMILY menu
+<dl>
+    <dt>Open Qsynth from the INSTRUMENT sub-menu in the AUDIO section of the FAMILY menu.</dt>
+        <dd>Qsynth opens and starts JACK.</dd>
+    <dt>Open QjackCtl from the AUDIO section of the FAMILY menu to verify that Jack is started.</dt>
+        <dd>QjackCtl GUI opens and the audio-server is already running.</dd>
+    <dt>In the QjackCtl GUI, click on the "Connect" Button.</dt>
+        <dd>The "Connection" windows opens.</dd>
+    <dt>Click on the "Audio" tab of the window that opens.</dt>
+        <dd>The Audio-tab is displayed and Qsynth has an entry in the Readable clients section, that is connected to the entry named "system" in the writable client section.</dd>
+</dl>
+
+This test will check if Qsynth can load sound-fonts.
+<strong>Make sure you followed the steps above first.
+</strong>
+<dl>
+    <dt>In the Qsynth window, locate the "Setup" button and press it.</dt>
+        <dd>The setup window opens.</dd>
+    <dt>In the setup window, locate the "Soundfonts"-tab and click on it.</dt>
+        <dd>The "Soundfonts"-tab displays with an "open" button on the right-hand side of it.</dd>
+    <dt>Press the "Open" button.</dt>
+        <dd>A file browsing dialog opens up at the location /usr/share/sounds/sf2/ displaying a file called "FluidR3_GM.sf2".</dd>
+    <dt>Select the file "FluidR3_GM.sf2" and press "Open".</dt>
+        <dd>"FluidR3_GM.sf2" is loaded and listed in the "Soundfonts"-tab of Qsynth setup window.</dd>
+    <dt>Click the "OK" button in the Qsynth Setup window.</dt>
+        <dd>The setup window closes.</dd>
+</dl>
+
+This test will check if Qsynth can output sound with the loaded SoundFont.
+<strong>Make sure you followed the steps above first.
+</strong>
+<dl>
+    <dt>Start the program "Virtual MIDI keyboard" from the MIDI UTILITIES sub-menu of the AUDIO section in the FAMILY menu.</dt>
+        <dd>"Virtual MIDI keyboard" opens.</dd>
+    <dt>In the QjackCtl GUI, press the "Connect" button.</dt>
+    <dt>In the "connections" windows that opens up, locate the "ALSA"-tab and click on it.</dt>
+    <dt>In the "Readable Clients" section, select the entry with "Virtual Keyboard" in the name. In the "Writable Clients" section, select the entry with "FLUID Synth" in the name.</dt>
+    <dt>Still in the "ALSA"-tab of the connections window in the QjackCtl GUI, with both previously selected readable/writable entries highlighted, press the button labeled "Connect".</dt>
+        <dd>A line is drawn between the "Virtual Keyboard" entry and the "Fluid Synth" entry.</dd>
+    <dt>Focus the "Virtual Keyboard" window, and click on a note key.</dt>
+        <dd>Sound is being played back.</dd>
 </dl>
 
 <strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.