Merge ubuntu-manual-tests:add_gnome_suite_test into ubuntu-manual-tests:main

Proposed by Tim Andersson
Status: Merged
Merged at revision: 775d5a01aa43f050d1d3c1ec75e34752c7293fa1
Proposed branch: ubuntu-manual-tests:add_gnome_suite_test
Merge into: ubuntu-manual-tests:main
Diff against target: 114 lines (+96/-0)
2 files modified
testcases/image/1436_Post-Installation Tests (+4/-0)
testcases/image/1783_Canary Install Test GNOME Suite (+92/-0)
Reviewer Review Type Date Requested Status
Brian Murray Approve
Review via email: mp+451347@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Brian Murray (brian-murray) wrote :

I think this should be classified as a "Run once" test as respins of the image are less likely to happen because of an application. It might make sense to add this as a part of the "Post Installation Tests" e.g. https://iso.qa.ubuntu.com/qatracker/milestones/446/builds/286684/testcases/1436/results or as a separate test similar to the "First login wizard" test.

Linking to the wiki page seems like a great idea though as that is easier to update than these!

review: Needs Fixing
Revision history for this message
Tim Andersson (andersson123) wrote :

As far as I can tell, we don't define what is mandatory, mandatory extras or run-once in the definitions, but we do that in the isotracker itself by adding a testcase to a test suite right? So this MP doesn't need amending? Or am I mistaken?

Revision history for this message
Tim Andersson (andersson123) wrote :

I don't find any instances of "mandatory" within the repo outside of stating the id field is mandatory

Revision history for this message
Brian Murray (brian-murray) wrote :

> As far as I can tell, we don't define what is mandatory, mandatory extras or
> run-once in the definitions, but we do that in the isotracker itself by adding
> a testcase to a test suite right? So this MP doesn't need amending? Or am I
> mistaken?

That's correct. What I was trying to say was that the install part of the test seems redundant and that we should move the actual test re gjs to a separate test that only covers that (or into the post-install test 1436) rather than have testers run the install again just to test gjs.

I hope that's clearer!

Revision history for this message
Tim Andersson (andersson123) wrote :

I've amended and pushed :)

Revision history for this message
Brian Murray (brian-murray) wrote :

I merged this and dropped the 1783 test id file and then updated 1436 on the server.

Thanks!

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/testcases/image/1436_Post-Installation Tests b/testcases/image/1436_Post-Installation Tests
2index 98bcdb2..6f6c2b1 100644
3--- a/testcases/image/1436_Post-Installation Tests
4+++ b/testcases/image/1436_Post-Installation Tests
5@@ -18,6 +18,10 @@
6 <dd>The timezone, date and time should match the settings you selected during installation</dd>
7 <dt>If you installed a non-english version of FAMILY, note the language used on the desktop</dt>
8 <dd>The desktop should be localized into your language, or it should have prompted you upon initial login to install the missing components for your language</dd>
9+ <dt>After installing a system, follow the two test cases here to test the GNOME suite of applications:</dt>
10+ <dd>https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs</dd>
11+ <dt>This test case is primarily useful when there have been updates to gjs, but is still worthy of testing on every release.</dt>
12+
13 </dl>
14 <strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
15 If an action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong>
16diff --git a/testcases/image/1783_Canary Install Test GNOME Suite b/testcases/image/1783_Canary Install Test GNOME Suite
17new file mode 100644
18index 0000000..4e3ccac
19--- /dev/null
20+++ b/testcases/image/1783_Canary Install Test GNOME Suite
21@@ -0,0 +1,92 @@
22+<!-- Please do not edit this file directly; it was generated with the
23+ tools/test_case_gen script using the following configuration as input:
24+ definitions/canary_desktop_cases.xml
25+-->
26+
27+ <p><em>Proceed in your native language if you wish. Instructions will remain in English.</em></p>
28+ <dl>
29+
30+
31+ <dt>Boot up the image</dt>
32+ <dd>If you see the GRUB boot menu you should see the following:</dd>
33+ <dd>
34+ <li>'Try or Install FAMILY'</li>
35+ <li>'FAMILY (safe graphics)'</li>
36+ <li>'OEM install (for manufacturers)'</li>
37+ <li>'Test memory' (only on BIOS systems)</li>
38+ </dd>
39+
40+
41+ <dt>Select the 'Try or Install FAMILY' option and press Enter</dt>
42+ <dd>The system boots properly and loads the installer displaying the Welcome dialog with language selection and the mascot logo on the right.'</dd>
43+
44+
45+ <dt>Click on 'Continue'</dt>
46+ <dd>The 'Try or Install' screen is displayed with 'try FAMILY' and 'Install FAMILY' buttons</dd>
47+ <dt>Click on the release notes hyperlink to confirm that a browser launches and you are taken to the release notes discourse page.</dt>
48+ <dt>Click on the 'Install FAMILY' icon to select the option and click on the Continue button</dt>
49+ <dd>The 'Keyboard layout' screen appears</dd>
50+ <dd>The proposed keyboard corresponds with your keyboard</dd>
51+ <dt>Select your keyboard layout and click on Continue</dt>
52+ <dd>The 'Connect to internet' screen is displayed</dd>
53+ <dd>The screen should reflect the current status and display those elements</dd>
54+ <dd>
55+ <li>Wired connection</li>
56+ <li>Connect to a Wi-Fi network followed by a scrollable list of available APs, displaying an active one colored with a leading checkmark</li>
57+ <li>Connect to a hidden Wi-Fi network</li>
58+ <li>I don't want to connect to internet for now</li>
59+ </dd>
60+ <dt>Click on 'Continue'</dt>
61+ <dd>The 'Updates and other software' screen is displayed, listing normal and minimal installation.</dd>
62+
63+
64+ <dt>Click on 'Continue'</dt>
65+ <dd>The 'Installation type' screen is displayed</dd>
66+
67+
68+ <dt>Note the state of the 'Erase disk and install FAMILY' radio button</dt>
69+ <dd>The 'Erase disk and install FAMILY' radio button is selected and the 'Advanced features' button is active</dd>
70+ <dt>Click on 'Continue'</dt>
71+ <dd>The 'Write changes to disk' screen is displayed, including the details of incoming partitions changes.</dd>
72+ <dt>Verify that the partitioning details make sense</dt>
73+ <dd>The available disk should be used for the installation</dd>
74+ <dt>Click 'Start Installing'</dt>
75+
76+
77+ <dd>The 'Where are you?' screen is displayed</dd>
78+ <dt>If your system is connected to the network, note the preselected timezone corresponds with your timezone and the city indicated in the text box</dt>
79+ <dd>The timezone and city displayed match your timezone and a major city from your area</dd>
80+ <dt>Select your timezone, and click on the Continue button</dt>
81+ <dd>The 'Who are you?' screen appears</dd>
82+ <dt>Input your initial user details and password <em>admin can not be used - it is a dedicated Linux User</em></dt>
83+
84+ <dd>Name, username and password are accepted.</dd>
85+ <dd>Continue button becomes available</dd>
86+ <dt>Click on 'Continue'</dt>
87+ <dd>The 'Choose your look' screen is displayed showing light and dark options</dd>
88+ <dt>Click on 'Continue'</dt>
89+ <dd>The 'Welcome to FAMILY' slide is displayed</dd>
90+ <dd>The slideshow is entirely in your language</dd>
91+ <dt>Wait for the installer to finish</dt>
92+ <dd>An 'Installation Complete' dialog appears</dd>
93+ <dt>Click the 'Restart into FAMILY XX.XX' button</dt>
94+ <dd>GUI is shut down, a prompt to remove media and press Enter appears</dd>
95+ <dt>Remove the disc and press enter</dt>
96+ <dd>The machine is rebooted</dd>
97+
98+
99+ <dt>Allow the machine to reboot</dt>
100+ <dd>The system boots properly and loads into FAMILY showing username selected</dd>
101+
102+ <dt>After rebooting, follow the two test cases here to test the GNOME suite of applications:</dt>
103+ <dd>https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs</dd>
104+ <dt>This test case is primarily useful when there have been updates to gjs, but is still worthy of testing on every release.</dt>
105+
106+ </dl>
107+ <p>If <strong>all</strong> actions produce the expected results described,
108+ please <a href="results#add_result">submit</a> a 'passed' result.</p>
109+ <p>If <strong>any</strong> action fails, or produces an unexpected result,
110+ please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include
111+ the bug number when you <a href="results#add_result">submit</a> your
112+ result.</p>
113+
114\ No newline at end of file

Subscribers

People subscribed via source and target branches

to all changes: