mv kittyhawk tests to a upper dir

17 files changed, 2579 insertions, 0 deletions

diff --git a/jobs/kittyhawk/baseOS/applications.txt.in b/jobs/kittyhawk/baseOS/applications.txt.in
new file mode 100644
index 0000000..4aff378
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/applications.txt.in
@@ -0,0 +1,226 @@
+plugin: manual
+id: kittyhawk/baseOS/applications/ibus-general
+depends: kittyhawk/baseOS/applications/ibus-launching
+requires: package.name=="ibus"
+command: /usr/bin/ibus-setup
+_description:
+ PURPOSE:
+ 1. IBus - Editing the IBus Preference
+ STEPS:
+ 1. Launch the IBus
+ 2. Change the hotkey for launching the tool
+ 3. Use new hotkey to launch tool
+ VERIFICATION:
+ 1. Is the change functional?
+
+plugin: manual
+id: kittyhawk/baseOS/applications/ibus-input-method
+depends: kittyhawk/baseOS/applications/ibus-general
+requires: package.name=="ibus"
+command: /usr/bin/ibus-setup
+_description:
+ PURPOSE:
+ 1. Verify IBus input method switching
+ STEPS:
+ 1. Launch the IBus
+ 2. Select and add new input method
+ 3. Use hotkey to switch to the new added input method
+ VERIFICATION:
+ 1. Is the change functional?
+
+plugin: manual
+id: kittyhawk/baseOS/applications/ibus-launching
+_description:
+ PURPOSE:
+ 1. IBus - Launching the application
+ STEPS:
+ 1. Open an application which has space to input characters like GEdit
+ 2. Press [CTRL] + [SPACE]
+ VERIFICATION:
+ 1. Did the applet launch?
+
+plugin: manual
+id: kittyhawk/baseOS/applications/ibus-unity
+depends: kittyhawk/baseOS/applications/ibus-launching
+requires: package.name=="ibus"
+_description:
+ PURPOSE:
+ 1. Verify IBus input method can be functional in Unity
+ STEPS:
+ 1. Start Dash by press "Super" key, and focus on search bar of Dash.
+ 2. Launch the IBus
+ 2. Input any non-English characters
+ VERIFICATION:
+ 1. Can non-English characters be inputted in the search bar of Dash?
+
+plugin: manual
+id: kittyhawk/baseOS/applications/rhythmbox
+_description:
+ PURPOSE:
+ 1. Verify that when clicking mp3 files, rhythmbox is chosen to play
+ 2. Verify that rhythmbox can play the mp3 files
+ STEPS:
+ 1. Install and boot to desktop
+ 2. Find an mp3 file and copy over to the SUT
+ 3. Right-click the mp3 file
+ 4. Double click the mp3 file
+ VERIFICATION:
+ 1. In step 3, only rhythmbox player should be recommened for application
+ 2. In step 4, Fluendo EULA should be displayed. Click OK. Rhythmbox is launched automatically and plays the mp3.
+ NOTES:
+ 1. Watauga Bug #1000022
+ 2. Watauga Bug #1007486
+
+plugin: manual
+id: kittyhawk/baseOS/applications/ubuntu-tour
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu Tour is present and can be opened and closed successfully.
+ 2. Verify Ubuntu Tour menu does not become unreadable when interrupting a tutorial
+ STEPS:
+ 1. Log in, find Ubuntu Tour, open it and close it.
+ 2. Open it and select a tutorial and follow the first few prompts
+ 3. Click on the 'Back to menu' icon in the lower right of the screen
+ VERIFICATION:
+ 1. Ubuntu Tour should be installed and can be opened and closed successfully.
+ 2. The "Welcome to the Ubuntu tour!" window appears and all text is readable.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.9.1
+
+plugin: manual
+id: kittyhawk/baseOS/applications/user-guide
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu User Guide is present and can be opened and closed successfully.
+ STEPS:
+ 1. Log in, find Ubuntu User Guide (Enter 'Help' in Dash), open it and close it.
+ 2. Launch Ubuntu User Guide again, click through links in the guide
+ VERIFICATION:
+ 1. Ubuntu User Guide should be included and can be opened and closed successfully.
+ 2. Ubuntu User Guide should include correct Ubuntu version info, contents should not be corrupted and links should work correctly.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.9.2
+
+plugin: manual
+id: kittyhawk/baseOS/applications/sysinfo
+_description:
+ PURPOSE:
+ 1. Verify Sysinfo GUI tool for users is available
+ STEPS:
+ 1. Launch Sysinfo application by input "sysinfo" from Dash search bar
+ VERIFICATION:
+ 1. Sysinfo GUI tool window Launches
+ 2. System, CPU, Memory, Storage and Hardware info could be viewed from left panel of Sysinfo window
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.9.3
+
+plugin: manual
+id: kittyhawk/baseOS/applications/ubuntu-one-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu One should auto start on first login and can be opened and closed successfully.
+ STEPS:
+ 1. Log in after completing oem-config, connect to network
+ 2. Log out and log in.
+ VERIFICATION:
+ 1. Ubuntu One should auto start on first login.
+ 2. After close Ubuntu One and re-logging in, Ubuntu One should not autorun again.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.9.4
+
+plugin: manual
+id: kittyhawk/baseOS/applications/software-center
+_description:
+ PURPOSE:
+ 1. Verify Software Center for users is available
+ STEPS:
+ 1. Click Software Center on the Launcher
+ VERIFICATION:
+ 1. Software Center on the Launcher
+ 2. Software Center can be launched
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.9.5
+
+plugin: manual
+id: kittyhawk/baseOS/applications/camera
+_description:
+ PURPOSE:
+ 1. Verify camera application works
+ STEPS:
+ 1. Launch Dash and search for "Cheese" application
+ 2. Launch Dash and search for "Camera" application
+ 3. Take pictures with Camera app under different image resolutions
+ 4. Record videos with Camera app
+ VERIFICATION:
+ 1. Cheese app should be removed
+ 2. Camera app should already be pre-installed
+ 3. With Camera app, snapshots should be correctly taken and saved to Pictures directory under Home in .jpg format
+ 4. With Camera app, video should be correctly recorded & played back
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.9.8, #1.21.1
+ 2. Camera app tests should be tested with more than 1+ machine and also with machines with touchscreens to make sure it is stable
+
+plugin: manual
+id: kittyhawk/baseOS/applications/no-ubuntu-one
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu One should *NOT* auto start on logins
+ STEPS:
+ 1. Make sure user is connected to network and log in after completing oem-config.
+ 2. Log out and log in.
+ VERIFICATION:
+ 1. Ubuntu One should *NOT* auto start on first login because it should not be included.
+ 2. After close Ubuntu One and re-logging in, Ubuntu One still should *NOT* auto start because it should not be included.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.9.4
+
+plugin: manual
+id: kittyhawk/baseOS/applications/gallery
+_description:
+ PURPOSE:
+ 1. Verify that Gallery is included but not the default application to open pictures & does not replace shotwell
+ STEPS:
+ 1. Launch Shotwell app by entering "shotwell" in Dash
+ 2. Launch Gallery app by entering "gallery" in Dash
+ 4. In Nautilus, open any directory with picture files and double click a picture
+ 5. In Nautilus, open andy directory with picture files and right-click a picture
+ VERIFICATION:
+ 1. Shotwell app should be available and should work correctly in step 1
+ 2. Gallery app should be available and should work correctly in step 2
+ 3. Gallery app should show pictures included in ~/Pictures directory in step 2
+ 4. The picture should not be launched by gallery app in step 4
+ 5. The "open with" option list should include both Gallery & Shotwell
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.21.8
+
+plugin: manual
+id: kittyhawk/baseOS/applications/web-apps
+_description:
+ PURPOSE:
+ 1. Verify that Ubuntu enhanced web apps work correctly and has the same defaults as the distro in 14.04.
+ STEPS:
+ 1. Launch terminal and enter "dpkg -l | grep unity-webapps"
+ 2. Install any web apps via apt-get with commands such as "sudo apt-get install unity-webapps-gmail" or "sudo apt-get install unity-webapps-cnn-news"
+ 3. Launch the installed web app via Dash
+ 4. Check if installed web app works correctly
+ VERIFICATION:
+ 1. "unity-webapps-qml" & "unity-webapps-service" should be listed in Step 1
+ 2. Installation should be successful in Step 2
+ 3. The installed app should be launched with default browser and should work correctly in Step 3 & 4
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.9.6
+
+plugin: manual
+id: kittyhawk/baseOS/applications/touch-app-for-desktop
+_description:
+ PURPOSE:
+ 1. Verify that $DESKTOP_MODE=1 for touch apps to run correctly on desktops/laptops
+ STEPS:
+ 1. Launch terminal and execute "echo $DESKTOP_MODE"
+ 2. Launch touch apps such as gallery or camera
+ VERIFICATION:
+ 1. The returned value of Step 1 should be 1
+ 2. The apps should launch in windows mode instead of full screen mode in Step 2, and windows can be maximized or minimized.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.21.*
+
diff --git a/jobs/kittyhawk/baseOS/benchmark.txt.in b/jobs/kittyhawk/baseOS/benchmark.txt.in
new file mode 100644
index 0000000..5b18fe9
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/benchmark.txt.in
@@ -0,0 +1,18 @@
+plugin: manual
+id: kittyhawk/baseOS/benchmark/boot-speed
+command: boottime.py
+_description:
+ PURPOSE:
+ 1. Collect boot charts from representative systems.
+ STEPS:
+ 1. Install 'bootchart' and 'pybootchargui',
+ 2. Restart the system to create boot info
+ 2. Run python script 'boottime.py' to output boot time info & collect bootchart.png from /var/log/bootchart
+ VERIFICATION:
+ 1. N/A
+ NOTES:
+ 1. Representative systems: one of HP, Dell and Lenovo Laptop/Desktop/AIO.
+ 2. Measure boot time for image under test.
+ 3. boottime.py can be download from https://bazaar.launchpad.net/~timchen119/oem-qa-tools/oem-qa-tools-boottime-broken/files
+ 4. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.4.6
+
diff --git a/jobs/kittyhawk/baseOS/canonical-census.txt.in b/jobs/kittyhawk/baseOS/canonical-census.txt.in
new file mode 100644
index 0000000..93b8ca7
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/canonical-census.txt.in
@@ -0,0 +1,41 @@
+plugin: manual
+id: kittyhawk/baseOS/canonical-poke/send-poke
+_description:
+ PURPOSE:
+ 1. Verify system sends the following info to the census server: contents of /var/lib/ubuntu_dist_channel (image build), system marketing name (ex. ThinkPad X220), OEM vendor name (ex. Lenovo), distro release (ex. 14.04), the number of times system checks in.
+ STEPS:
+ 1. Use the testing canonistack apache server at IP_Address for testing.
+ 2. Add a line to /etc/hosts for IP_Address census.canonical.com
+ 3. Run send-census script (sudo /etc/cron.daily/send-poke), use as many different OEM systems as possible
+ 4. Login in IP_Address via SSH and use test/password for username/password. Check the /var/log/apache2/access.log
+ VERIFICATION:
+ 1. Check the server log, it should match the system info
+ 2. The format should be like https://pastebin.canonical.com/76680/
+ NOTES:
+ 1. This fake apache server will be teared down once Watauga is done. Please contact Technical Lead if you encounter any login issues.
+ 2. It's not clear how often the system will send the info to the census server, will manually run the script for now
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.18
+
+plugin: manual
+id: kittyhawk/baseOS/canonical-poke/parsing
+_description:
+ PURPOSE:
+ 1. Verify census info can be viewed on https://oem-reports.canonical.com/census
+ STEPS:
+ 1. After 'send-census' test, go to https://oem-reports.canonical.com/census
+ VERIFICATION:
+ 1. The system info and the number of times system checks in should match the info shown on the server side
+ NOTES:
+ 1. The census parsing may not be ready. We can use the test server David B set up for testing. Census script is using sqlite to build database tables. To view the parsing result, ssh to IP_Address using test/password, and do 'python census -d /tmp/test.db -l /var/log/apache2/access.log'. and 'echo '.dump' | sqlite3 /tmp/test.db'. The census script needs to be uploaded to IP_Address first.
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.18
+
+plugin: manual
+id: kittyhawk/baseOS/canonical-poke/census-script-update-initramfs-1065574
+_description:
+ PURPOSE:
+ 1. Verify census sciprt won't caused update-initramfs error
+ STEPS:
+ 1. sudo update-initramfs -u
+ VERIFICATION:
+ 1. There is no error occured during update-initramfs
+
diff --git a/jobs/kittyhawk/baseOS/chipset-support.txt.in b/jobs/kittyhawk/baseOS/chipset-support.txt.in
new file mode 100644
index 0000000..53fd1cd
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/chipset-support.txt.in
@@ -0,0 +1,63 @@
+plugin: manual
+id: kittyhawk/baseOS/chipset-support/haswell
+_description:
+ PURPOSE:
+ 1. Verify the image doesn't break anythiing else after including Intel Haswell driver packages
+ 2. Verify Haswell packages are installed by default
+ STEPS:
+ 1. Install the build on a Haswell system and non Haswell system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitches during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.11.1, #1.11.2
+
+plugin: manual
+id: kittyhawk/baseOS/chipset-support/broadwell
+_description:
+ PURPOSE:
+ 1. Verify that system can support Intel Broadwell
+ STEPS:
+ 1. Install the build on a Broadwell system and non Broadwell system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitches during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.11.3, #1.11.4
+ 2. Broadwell gfx beta driver used for GM release because formal driver will not be ready until 6/1/2014
+
+plugin: manual
+id: kittyhawk/baseOS/chipset-support/baytrail-d
+_description:
+ PURPOSE:
+ 1. Verify that system can support Intel Bay Trail-D
+ STEPS:
+ 1. Install the build on a Bay Trail-D system and non Bay Trail-D system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitches during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.11.6
+
+plugin: manual
+id: kittyhawk/baseOS/chipset-support/baytrail-m
+_description:
+ PURPOSE:
+ 1. Verify that system can support Intel Bay Trail-M
+ STEPS:
+ 1. Install the build on a Bay Trail-M system and non Bay Trail-M system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitches during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.11.6
+
+plugin: manual
+id: kittyhawk/baseOS/chipset-support/amd
+_description:
+ PURPOSE:
+ 1. Verify that system can support AMD Kaveri, Beema/Mullins, Richland, Kabini/Temash
+ STEPS:
+ 1. Install the build on a AMD system and a non AMD system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitches during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.12.1, #1.12.2, #1.12.3, #1.12.4
+ 2. Actual test matrix controlled by another file
+
diff --git a/jobs/kittyhawk/baseOS/core.txt.in b/jobs/kittyhawk/baseOS/core.txt.in
new file mode 100644
index 0000000..056e7a3
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/core.txt.in
@@ -0,0 +1,338 @@
+plugin: manual
+id: kittyhawk/baseOS/core/64bit
+command: uname -m
+_description:
+ PURPOSE:
+ 1. Verify the image supports 64 bit architecture
+ STEPS:
+ 1. Is $output (automatically captured) the same as x86_64?
+ VERIFICATION:
+ 1. It should show x86_64
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.1
+
+plugin: manual
+id: kittyhawk/baseOS/core/managed-upgrades
+_description:
+ PURPOSE:
+ 1. Verify that the default turns off automatic notification of new versions of Ubuntu (including LTS)
+ STEPS:
+ 1. Launch Update Manager by finding "Software & Updates" in Dash,
+ 2. Check default value of "Notify me of a new Ubuntu version" in the "Updates" tab
+ VERIFICATION:
+ 1. Value should be 'Never'
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.2
+
+plugin: manual
+id: kittyhawk/baseOS/core/UEFI
+_description:
+ PURPOSE:
+ 1. Verify image can be installed successfully on UEFI systems
+ STEPS:
+ 1. Set BIOS to boot in UEFI mode.
+ 2. Install the image.
+ VERIFICATION:
+ 1. Image should be installed successfully
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.5
+
+plugin: manual
+id: kittyhawk/baseOS/core/localization
+_description:
+ PURPOSE:
+ 1. Verify system can be installed in the following languages: Catalan, Czech, Danish, German, English, Spanish, Euskera (Basque), French, Galician, Italian, Hungarian, Dutch, Polish, Portuguese, Brazilian Portuguese, Slovak, Finnish, Swedish, Greek, Bulgarian, Russian, Korean, Simplified Chinese, Traditional Chinese, Japanese.
+ STEPS:
+ 1. During oem-config, select language.
+ 2. Log in to desktop, run 'sudo apt-get update'
+ 3. Do 'locale' to find out the language code, for example, en_US
+ 4. Do 'check-language-support -l <LANG>'
+ VERIFICATION:
+ 1. If check-language-support returns anything, it's a FAIL
+ 2. Should achieve full localization in launcher bar, dash, application indicators, and all application launchers and descriptions
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.8
+
+plugin: manual
+id: kittyhawk/baseOS/core/UX
+_description:
+ PURPOSE:
+ 1. Verify that user experience is unity-based and with fallback with unity-2D
+ STEPS:
+ 1. Install the system
+ 2. Login, open a terminal and do 'echo $DESKTOP_SESSION'
+ 3. Logout, click on the ubuntu circle on the login window and choose ubuntu-2d and log in. open a terminal and do 'echo $DESKTOP_SESSION'
+ VERIFICATION:
+ 1. In step 2, it should return 'ubuntu'. In step 3, it should return 'ubuntu-2d'
+
+plugin: local
+id: kittyhawk/baseOS/core/recovery
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk/baseOS/core/recovery.txt*
+_description: OS recovery verification
+
+plugin: manual
+id: kittyhawk/baseOS/core/available-updates-included
+_description:
+ PURPOSE:
+ 1. Verify when a OEM 14.04 LTS image is installed, all available updates at time of image generation.
+ STEPS:
+ 1. Install OEM 14.04 LTS image, run "/usr/lib/update-notifier/apt-check"
+ VERIFICATION:
+ 1. OS image shall include all available updates
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.15
+
+plugin: manual
+id: kittyhawk/baseOS/core/supsend
+_description:
+ PURPOSE:
+ 1. Verify that user can suspend the system from UI.
+ STEPS:
+ 1. Click on the setting icon on the system tray, choose suspend
+ 2. Press the power button, choose suspend
+ VERIFICATION:
+ 1. Suspend should appear and system should suspend successfully
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.1
+
+plugin: manual
+id: kittyhawk/baseOS/core/hybrid-sleep-basic
+_description:
+ PURPOSE:
+ 1. Verify that user can enter hybrid-sleep from UI.
+ STEPS:
+ 1. Click on the power icon on the system tray, choose hybrid sleep
+ 2. Wake system up by pressing power button
+ 3. Press the power button again and choose hybrid sleep
+ 4. Wake system up by pressing power button
+ VERIFICATION:
+ 1. Hybrid sleep option should appear and system should enter hybrid sleep successfully in step 1 & step 3
+ 2. System should wake up successfully in step 2 & step 4
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.3
+ 2. Verification on whether hybrid sleep is correctly performed will be in test case "hybrid-sleep-verification"
+
+plugin: manual
+id: kittyhawk/baseOS/core/hybrid-sleep-verification
+_description:
+ PURPOSE:
+ 1.Verify that system can suspend to both disk and RAM from the beginning.
+ STEPS:
+ 1. Open any applicaton or browser
+ 2. Press Power menu and select hybrid sleep to sleep the system
+ 3. Remove AC adapter and Battery for a while and re-install AC or Battery
+ 4. Press Power button to wake up the system
+ 5. Press Power button and select the hybrid sleep from the pop-up menu
+ 6. Repeat step 3 ~4
+ VERIFICATION:
+ 1. Check that the system resumes from the previous session.
+ 2. Check that hybrid sleep can be launched from power menu and power button menu
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.3
+
+plugin: manual
+id: kittyhawk/baseOS/core/cedar-trail-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify the image doesn't break anythiing else after including Intel Cedar Trail driver packages
+ 2. Verify cedar trail packages are installed by default
+ 3. Verify default desktop is ubuntu-2D
+ 4. Verify ocracoke (Cedar Trail) production archive is added in sources.list
+ STEPS:
+ 1. Install the build on a Cedar Trail system and non-Cedar Trail system.
+ 2. Check Adobe Flash and Java plugin
+ 3. Install VMware View 5 and Citrix Receiver 12 from Software Center and check the launch and close.
+ 4. Check if there is 'precise-ocracoke.list in /etc/apt/sources.list.d/ and do apt-get update
+ VERIFICATION:
+ 1. On the Cedar Trail system, the default desktop management should be Unity 2D. On the non Cedar Trail system, the default desktop management should be Unity 3D.
+ 2. Adobe Flash, Java plugin, VMware View 5 and Citrix Receive 12 should be launched and closed successfully.
+ 3. Check if cedarview-drm, libva-cedarview-vaapi-driver, cedarview-graphics-drivers are installed by default.
+ 4. There should be 'precise-ocracoke.list' in /etc/apt/sources.list.d/ and hwe.archive.canonical.com is on the apt-get update list
+ NOTES:
+ 1. Cedar Trail graphics is 32-bit only. It doesn't support OpenGL, so the default desktop management is unity 2D.
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.17
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery-less-build
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu Recovery is not in no-recovery builds
+ STEPS:
+ 1. Install no-recovery builds
+ VERIFICATION:
+ 1. During the install or after the install, there should not be Ubuntu Recovery.
+
+plugin: manual
+id: kittyhawk/baseOS/core/cedar-trail-production-archive-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify ocracoke production archive needs to be added to the sources.list for the i386 builds.
+ 2. Verify canonical-oem-keyring is added
+ STEPS:
+ 1. Install 32-bit builds
+ 2. Check /etc/apt/sources.list.d/
+ 3. Run apt-get update
+ VERIFICATION:
+ 1. There should be canonical partner, or hwe.archive, or ocracoke in /etc/apt/sources.list.d/
+ 2. When running apt-get update, it shouldn't complain missing keys for canonical related sources
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.17
+ 2. Watauga Bug#986362
+
+plugin: manual
+id: kittyhawk/baseOS/core/GPT-install
+_description:
+ PURPOSE:
+ 1. Verify that partitions installed on GPT are created correctly with or without recovery.
+ 2. Verify protective MBR doesn't set OS partition to active
+ STEPS:
+ 1. Install image in UEFI/GPT
+ VERIFICATION:
+ 1. Use gdisk to check protective MBR.
+ 2. Launch Disk Utility. Click the hard disk in question on the left pane. On right pane you will see "Volumes". Click each partition. If a partition is misaligned you will in a yellowish orange box: "WARNING: The partition is misaligned by X bytes. This may result in very poor performance. Repartitioning is suggested."
+ NOTES:
+ 1. Watauga Bug #1012675, #1015636, #1017563
+
+plugin: manual
+id: kittyhawk/baseOS/core/watauga-product-archive-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify Watauga production archive is added to the Watauga sources.list.
+ STEPS:
+ 1. Install OS
+ 2. Check /etc/apt/sources.list.d/
+ 3. Run apt-get update
+ VERIFICATION:
+ 1. There should be canonical partner, or precise.watauga in /etc/apt/sources.list.d/
+ 2. When running apt-get update, it shouldn't complain missing keys for canonical related sources
+ NOTES:
+ 1. Watauga 3.0, PRD # 1.12.2
+ 2. http://watauga.archive.canonical.com/dists/precise-watauga/
+
+plugin: manual
+id: kittyhawk/baseOS/core/dns-config-1030811
+_description:
+ PURPOSE:
+ 1. Validate no invalid DNS config in the image
+ STEPS:
+ 1. Install the OS, and check /etc/resolv.conf and any files in /etc/resolv.conf.d/
+ VERIFICATION:
+ 1. There should be no pre-defined DNS setting
+ NOTES:
+ 1. Watauga Bug #1030811
+
+plugin: manual
+id: kittyhawk/baseOS/core/wireless
+_description:
+ PURPOSE:
+ 1.Verify user shall have the ability through a Connection Manager to connect to both encrypted and unencrypted Wi-Fi/WLAN connections.
+ STEPS:
+ 1. Click on the Network icon in the panel.
+ 2. Select a network below the 'Wireless networks' section.
+ 3. Connect to encrypted and unencrypted Wi-Fi AP
+ 4. Lanuch web browser to verify that it's possible to establish an HTTP connection.
+ 5. Let system enter s3
+ 6. Resume system
+ 7. Repeat step 1~4
+ VERIFICATION:
+ 1. User shall have the ability through a Connection Manager to connect to both encrypted and unencrypted Wi-Fi/WLAN connections both before & after s3
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.3.1
+ 2. If there are no unencrypted AP available just skip the unencrypted testing.
+
+plugin: manual
+id: kittyhawk/baseOS/core/ethernet
+_description:
+ PURPOSE:
+ 1.Verify user shall have the ability through a Connection Manager to connect to a ethernet network.
+ STEPS:
+ 1. Connect to Ethernet cable
+ 2. Launch web browser to verify that it's possible to establish an HTTP connection.
+ 3. Check ethernet connection is listed in 'Network' icon in the panel > 'Wireless networks' section
+ 4. Let system enter s3
+ 5. Resume system
+ 6. Repeat step 2 ~ 3
+ VERIFICATION:
+ 1. Verify user shall have the ability through a Connection Manager to connect to a ethernet network before & after s3
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.3.2
+
+plugin: manual
+id: kittyhawk/baseOS/core/pxe
+_description:
+ PURPOSE:
+ 1. This provides factory installation compatibility with our certification lab. It allows for mass testion of our OS images for updates, upgrades, etc.
+ STEPS:
+ 1. Install system via PXE and finish OOBE setting
+ VERIFICATION:
+ 1. System can finish installation and boot up
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.16
+
+plugin: manual
+id: kittyhawk/baseOS/core/bay-trail-M
+_description:
+ PURPOSE:
+ 1. Verify the image doesn't break anythiing else after including Intel Bay Trail-M driver packages
+ 2. Verify Bay Trail-M packages are installed by default
+ STEPS:
+ 1. Install the build on a Bay Trail-M system and non Bay Trail-M system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitchs during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.11.6
+ 2. Need update after knowing more restrications on the system user experience and features specific to Bay Trail.
+
+plugin: manual
+id: kittyhawk/baseOS/core/bay-trail-D
+_description:
+ PURPOSE:
+ 1. Verify the image doesn't break anythiing else after including Intel Bay Trail-D driver packages
+ 2. Verify Bay Trail-M packages are installed by default
+ STEPS:
+ 1. Install the build on a Bay Trail-D system and non Bay Trail-D system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitchs during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.11.6
+ 2. Need update after knowing more restrications on the system user experience and features specific to Bay Trail.
+
+plugin: manual
+id: kittyhawk/baseOS/core/kernel-version
+_description:
+ PURPOSE:
+ 1. Verify kernel version is correct
+ STEPS:
+ 1. Is "uname -a" the same as or newer than 3.13?
+ VERIFICATION:
+ 1. Kernel version should be 3.13 or newer
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.3
+
+plugin: manual
+id: kittyhawk/baseOS/core/kittyhawk-deb-repository
+_description:
+ PURPOSE:
+ 1. Verify that changes are implemented as debian files to allow simple upgrades
+ STEPS:
+ 1. Install image
+ 2. launch a text console and execute command "cat /etc/apt/sources.list.d/trusty-oem.list"
+ 3. execute command "dpkg -l | grep kittyhawk"
+ VERIFICATION:
+ 1. if output of command in step 2 is "deb http://oem.archive.canonical.com/updates/ trusty-oem public" "deb-src http://oem.archive.canonical.com/updates/ trusty-oem public" then test case passed
+ 2. if output of command in step 3 is not empty then test case passed
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.20, #1.14.2
+
+plugin: manual
+id: kittyhawk/baseOS/core/hybrid-sleep-8GB
+_description:
+ PURPOSE:
+ 1. Verify "hybrid sleep" is not provided when system RAM is >=8GB (when swap=0)
+ STEPS:
+ 1. Install the build with Ubuntu recovery on a system with <8GB memory
+ 2. Install the build with Ubuntu recovery on a system with >=8GB memory
+ VERIFICATION:
+ 1. Hybrid-sleep should only be available on systems with <8GB memory (or when swap is available. To see if swap partition exists, execute "free -m" in terminal)
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.2
+
diff --git a/jobs/kittyhawk/baseOS/core/recovery.txt.in b/jobs/kittyhawk/baseOS/core/recovery.txt.in
new file mode 100644
index 0000000..8f640a2
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/core/recovery.txt.in
@@ -0,0 +1,232 @@
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/internal-disk-recovery
+_description:
+ PURPOSE:
+ 1. Verify "Ubuntu Recovery" works from internal disk in Legacy and UEFI BIOS
+ STEPS:
+ 1. Enter Grub and choose recovery on a Legacy machine
+ 2. Check if recovery is successful on this machine
+ 3. Enter Grub and choose recovery on an UEFI machine
+ 4. Check if recovery is successful on this machine
+ VERIFICATION:
+ 1. Recovery should be successful in step 2
+ 2. Recovery should be successful in step 4
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.9
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/swap-partition-in-UEFI
+_description:
+ PURPOSE:
+ 1. Verify that swap partition is created properly when >2TB HDD and <4GB RAM are installed
+ STEPS:
+ 1. Install the system image on a system with >2TB HDD and with <4GB RAM. Make sure the BIOS is set in UEFI mode.
+ 2. After the install, check the swap partition size
+ VERIFICATION:
+ 1. The swap partition size should be around 4GB for 2GB RAM, or 2GB for 1GB RAM.
+ NOTES:
+ 1. This requires working BIOS in UEFI mode.
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/phase1-install
+_description:
+ PURPOSE:
+ 1. Verify the default action is to automatically reboot at the end of installation phase 1
+ 2. Verify it can be changed to automatically poweroff
+ 3. Verify when preseed is empty, the default action is to display a window to tell user to restart the system
+ STEPS:
+ 1. Create a USB startup key with 32-bit recovery or 64-bit recovery image
+ 2. Check /preseed/project.cfg in the USB key. Start the install
+ 3. Change /preseed/project.cfg from 'ubiquity ubuntu-recovery/auto_power_option string reboot' to 'ubiquity ubuntu-recovery/auto_power_option string poweroff'. Start the install
+ 4. Delete 'ubiquity ubuntu-recovery/auto_power_option string poweroff' from /preseed/project.cfg. Start the install
+ VERIFICATION:
+ 1. In step 2, in /preseed/project.cfg, there should be 'ubiquity ubuntu-recovery/auto_power_option string reboot'. system should restart automatically after phase 1
+ 2. In step 2, system should poweroff automatically after phase 1
+ 3. In step 2, at the end of installation phase 1, system should display a window to tell user to restart the system
+ NOTES:
+ 1. Watauga Bug#1000528
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/home-1
+_description:
+ PURPOSE:
+ 1. Verify /home partition is created automatically
+ 2. Verify that /home partition is preserved after the recovery
+ STEPS:
+ 1. Create a Install a new application such as Chromium browser, add a few bookmarks. Download a few documents
+ 2. Check the partition setup
+ 3. Recover the system and choose not to delete user data, and create the user with the same username as before the recovery
+ 4. Install Chromium again and check bookmarks and check the /home/$USER/Downloads
+ VERIFICATION:
+ 1. There should be a partition for /home.
+ 2. Bookmarks and downloaded documents should be kept after the recovery.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.10 - Ubuntu Recovery with perservation of /home partition.
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/home-2
+_description:
+ PURPOSE:
+ 1. Verify if system partition is set as /home is in /, then the option of whether to delete or not to delete user data should not present in the recovery
+ STEPS:
+ 1. Install Kitty Hawk image, and update ubuntu recovery package
+ 2. Check the partition.
+ 3. Do a factory restore
+ VERIFICATION:
+ 1. In step 2, there should not be a partition for /home
+ 2. In the recovery UI, there should not be an option about preserving user data.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.10 - Ubuntu Recovery with perservation of /home partition.
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/power-failure-1021314-1054250
+_description:
+ PURPOSE:
+ 1. Verify system can boot when system is powered off in the middle of a user-initiated factory restore.
+ 2. Verify red grub is not shown
+ STEPS:
+ 1. Reboot system holding the Alt key to enter the grub menu
+ 2. perform factory restore
+ 3. power off system in the middle of doing the restore
+ 4. power on system
+ VERIFICATION:
+ 1. Factory restore is resumed without showing the red grub menu.
+ NOTES:
+ 1. Bug 1021314 - Watauga 2.0
+ 2. Bug 1054250 - Watauga 2.0
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/power-failure-1054243
+_description:
+ PURPOSE:
+ 1. Verify the red grub menu shows if any failure occurs during the factory install
+ STEPS:
+ 1. Install OS and power off the system during phase 1
+ 2. Power on system
+ 3. Repeat step 1 and 2, power off the system during phase 2
+ VERIFICATION:
+ 1. The red grub menu should show if any failure occurs during the factory install
+ NOTES:
+ 1. Bug #1054243
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/swap-deleted-1029990
+_description:
+ PURPOSE:
+ 1. Verify swap partition is deleted during recovery on systems with >= 4GB RAM
+ STEPS:
+ 1. Swap partition should be removed during the recovery and added back later. Install the system, check the partition setup and run the factory recovery. After the recovery is done, check the partition.
+ VERIFICATION:
+ 1. There should be just 1 swap partition.
+ NOTES:
+ 1. Bug #1029990 - Watauga 2
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/localized-1029995
+_description:
+ PURPOSE:
+ 1. Verify recovery dialog and text are translated
+ STEPS:
+ 1. Install the system and choose a non-English language
+ 2. Do a factory restore
+ VERIFICATION:
+ 1. Recovery dialog and text should be translated
+ NOTES:
+ 1. Bug #1029995 - Watauga 2
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/no-false-error-msg-1053388
+_description:
+ PURPOSE:
+ 1. Verify that there is no false error message when performing a factory restore
+ STEPS:
+ 1. After install OS, perform a factory restore
+ 2. Check both Legacy and EFI BIOS systems
+ VERIFICATION:
+ 1. There shouldn't be any false error message
+ NOTES:
+ 1. Bug #1053388 - "error: file not found" for legacy and "error: unknown command "hwmatch"" for EFI.
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/access-to-tty-1055568
+_description:
+ PURPOSE:
+ 1. Verify tty can still be accessed in phase 2 install and recovery
+ STEPS:
+ 1. Install OS on an EFI and a legacy bios system, switch between tty1 and tty7 in phase 2 install (ctrl+alt+F1 to tty1, and ctrl+alt+F7 back to tty7)
+ 2. Do factory restore and during the recovery, switch between tty1 and tty7
+ VERIFICATION:
+ 1. Access to tty should be available in phase 2 install and during recovery
+ NOTES:
+ 1. Watauga Bug #1055568
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/dvd-eject-1012940
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu Recovery doesn't hang when using DVD for OS installation with smaller RAM configuration.
+ STEPS:
+ 1. Install OS using DVD on a system with <4GB RAM
+ VERIFICATION:
+ 1. DVD eject is triggered at the end of phase 1 install, before the system goes down for a reboot.
+ 2. DVD eject is successful and Ubuntu Recovery continues.
+ NOTES:
+ 1. Watauga Bug #1012940
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/recovery-grub-localized-1032776
+_description:
+ PURPOSE:
+ 1. Verify the "Restore Ubuntu 12.04 to factory state" on the grub menu is localized when language other than English is selected
+ STEPS:
+ 1. Install the build with Ubuntu Recovery on a Legacy (BIOS) system and choose a language other than English
+ 2. Finish the install, restart the system, enter the grub menu
+ VERIFICATION:
+ 1. "Restore Ubuntu 12.04 to factory state" on the grub menu should be localized
+ NOTES:
+ 1. Watauga Bug #1032776
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/unattended-install-1011742
+_description:
+ PURPOSE:
+ 1. Verify the system can be install without any interaction
+ STEPS:
+ 1. Boot the install media, set recovery-type=factory at boot prompt
+ 2. Continue the install
+ 3. Repeat the test on a system that has recovery partition created already
+ 4. Repeat the test on a system with 64GB drive (so no swap will be created)
+ 5. Repeat the test on a system with >64GB driver (swap will be created)
+ VERIFICATION:
+ 1. Install should proceed without requiring any interactions during phase 1 and phase 2. After phase 2, OOBE should appear
+ NOTES:
+ 1. Watauga Bug #1011742 - This is useful so that we can automate the creation of an installed disk image (in a VM, ideally), so that a project's image can be run through smoke tests and automated QA without human interaction
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/bios-hotkey-REMOVED
+_description:
+ PURPOSE:
+ 1. Use a BIOS hotkey to select Ubuntu Recovery at boot
+ STEPS:
+ 1. Install image and Boot up system
+ 2. Press BIOS hotkey (should be F11) to enter Ubuntu Recovery
+ VERIFICATION:
+ 1. System can enter Ubuntu Recovery by press hotkey
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.11
+
+plugin: manual
+id: kittyhawk/baseOS/core/recovery/bootloader-hotkey
+_description:
+ PURPOSE:
+ 1. Use a bootloader hotkey to select Ubuntu Recovery at boot
+ STEPS:
+ 1. Install image and Boot up system
+ 2. Press bootloader hotkey (esc or shit+esc) to enter grub
+ 3. Press hotkey (F9) to enter Ubuntu Recovery
+ VERIFICATION:
+ 1. System can enter Ubuntu Recovery by press hotkey
+ 2. Recovery process can be completed without issues
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.12
+
diff --git a/jobs/kittyhawk/baseOS/estar.txt.in b/jobs/kittyhawk/baseOS/estar.txt.in
new file mode 100644
index 0000000..b4375b9
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/estar.txt.in
@@ -0,0 +1,211 @@
+plugin: manual
+id: kittyhawk/baseOS/estar/sleep-inactive-ac-timeout
+_description:
+ PURPOSE:
+ 1. Verify that sleep-inactive-ac-timeout setting is 1800 seconds
+ 2. Verify system enters suspend after 1800 seconds
+ STEPS:
+ 1. Install OS and log in to desktop. Check power settings
+ 2. Keep the system idle for 30 minutes
+ VERIFICATION:
+ 1. System should suspend when inactive for 30 minutes on AC power
+ 2. System should enter suspend after 30 minutes
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.4
+
+plugin: manual
+id: kittyhawk/baseOS/estar/sleep-inactive-battery-timeout
+_description:
+ PURPOSE:
+ 1. Verify that sleep-inactive-battery-timeout setting is 1800 seconds
+ 2. Verify system enters suspend after 1800 seconds
+ STEPS:
+ 1. Install OS and log in to desktop. Check power settings
+ 2. Keep the system idle for 30 minutes
+ VERIFICATION:
+ 1. System should suspend when inactive for 30 minutes on battery power
+ 2. System should enter suspend after 30 minutes
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.4
+
+plugin: manual
+id: kittyhawk/baseOS/estar/sleep-display-ac
+_description:
+ PURPOSE:
+ 1. Verify that display sleep time out is within 10 minutes
+ 2. Verify display turns off after 10 minutes
+ STEPS:
+ 1. Plug in AC, install OS and log in to desktop. Check power settings
+ 2. Keep the system idle for 10 minutes
+ VERIFICATION:
+ 1. Display sleep time out should be 10 minutes
+ 2. Display should be turned off after 10 minutes
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.4
+
+plugin: manual
+id: kittyhawk/baseOS/estar/sleep-display-battery
+_description:
+ PURPOSE:
+ 1. Verify that display sleep time out is within 10 minutes
+ 2. Verify display turns off after 10 minutes
+ STEPS:
+ 1. Unplug AC, install OS and log in to desktop. Check power settings
+ 2. Keep the system idle for 10 minutes
+ VERIFICATION:
+ 1. Display sleep time out should be 10 minutes
+ 2. Display should be turned off after 10 minutes
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.4
+
+plugin: manual
+id: kittyhawk/baseOS/estar/WoL
+requires: 
+_description:
+ PURPOSE:
+ 1. Verify the WoL feature can be enabled and disabled via ethtool
+ STEPS:
+ 1. On SUT A, go to BIOS and enable "Wake On LAN" support, proceed to desktop and connect to wired network
+ 2. Use ifconfig to get eth MAC address
+ 3. Put machine A to suspend
+ 4. Find a system B on the same network and do 'wakeonlan <A's MAC ADDRESS>'
+ 5. put machine B to suspend again
+ 6. launch gwakeonlan in Unity Dash in machine B
+ 7. click "Add machine" and finish the setup with A's mac address
+ 8. in the machines list enable A by clicking the checkbox on column 0
+ 9. click "Turn On" to wake up A
+ VERIFICATION:
+ 1. In step 4, machine A should resume from suspend.
+ 2. In step 9, machine A should resume from suspend.
+ NOTES:
+ 1. This test requires WoL support in BIOS
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.4, #1.2.7, #1.2.6
+
+plugin: manual
+id: kittyhawk/baseOS/estar/rtcwake
+_description:
+ PURPOSE:
+ 1. Verify the system can follow the scheduled wake events from Sleep mode
+ STEPS:
+ 1. On the system, use rtcwake to set the timer. Ex., sudo rtcwake -v -s 20 -m mem to suspend it for 20 seconds, or sudo rtcwake -m mem -t $(date +%s -d 'today 07:30') to put the systems to sleep and wake up at 7:30 today.
+ VERIFICATION:
+ 1. System should follow the scheduled wake events.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.4, #1.2.7, #1.2.6
+
+plugin: manual
+id: kittyhawk/baseOS/estar/power-consumption-running-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify DUT power consumption during system running
+ STEPS:
+ 1. Plugin power adapter to measure machine
+ 2. Keep the system running and watch the power consumption value
+ VERIFICATION:
+ 1. Record the power consumption to comment
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.5
+ 2. Please test 5 different model machines
+
+plugin: manual
+id: kittyhawk/baseOS/estar/poewr-consumption-suspend-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify DUT power consumption after system suspend
+ STEPS:
+ 1. Plugin power adapter to measure machine
+ 2. Suspend the machine and watch the power consumption value
+ VERIFICATION:
+ 1. Record the power consumption to comment
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.5
+ 2. Please test 5 different model machines
+
+plugin: manual
+id: kittyhawk/baseOS/estar/poewr-consumption-hibernate-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify DUT power consumption after system hibernate
+ STEPS:
+ 1. Plugin power adapter to measure machine
+ 2. Hibernate the machine and watch the power consumption value
+ VERIFICATION:
+ 1. Record the power consumption to comment
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.5
+ 2. Please test 5 different model machines
+
+plugin: manual
+id: kittyhawk/baseOS/estar/e-star-logo
+_description:
+ PURPOSE:
+ 1. Make sure E-star logo can be created in system
+ STEPS:
+ 1. Download watauga-e-star branch --> http://goo.gl/pJS1a
+ 2. Build the package and copy deb package to installed system
+ 3. Install e-star logo package to installed system
+ 4. Reboot system
+ 5. Check system settings -> details
+ VERIFICATION:
+ 1. It should show customized e-star logo in details application
+ NOTES:
+ 1. Watauga bug#1076265
+
+plugin: manual
+id: kittyhawk/baseOS/estar/suspend-option-20min
+_description:
+ PURPOSE:
+ 1. Verify that system power option in sleep settings menu has 20min setting
+ STEPS:
+ 1. Remove AC adaptor.
+ 2. In the Power setting set "On battery power" as 20 Minutes
+ 3. Idle system for 10 minutes
+ 4. Idle system for another 20 minutes
+ 5. Plug AC adaptor
+ 6. In the Power setting set "When plugged in" as 20 Minutes
+ 7. Idle system for 10 minutes
+ 8. Idle system for another 20 minutes
+ VERIFICATION:
+ 1. System will turn screen off after 10 minutes on step 3 and step 7
+ 2. System will enter suspend mode after 20 minutes on step 4 and step 8
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.8
+
+plugin: manual
+id: kittyhawk/baseOS/estar/suspend-option-2hours
+_description:
+ PURPOSE:
+ 1. Verify that system power option in sleep settings menu has 20min setting
+ STEPS:
+ 1. Remove AC adaptor.
+ 2. In the Power setting set "On battery power" as 2 hours
+ 3. Idle system for 10 minutes
+ 4. Idle system for another 2 hours
+ 5. Plug AC adaptor
+ 6. In the Power setting set "When plugged in" as 2 hours
+ 7. Idle system for 10 minutes
+ 8. Idle system for another 2 hours
+ VERIFICATION:
+ 1. System will turn screen off after 10 minutes on step 3 and step 7
+ 2. System will enter suspend mode after 2 hours on step 4 and step 8
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.9
+ 2. If system battery run out in 2 Hours, just test "On AC Power"
+
+plugin: manual
+id: kittyhawk/baseOS/estar/power-consumption
+_description:
+ PURPOSE:
+ 1. Verify DUT power consumption is Energy Star compliant
+ STEPS:
+ 1. Plugin power adapter to measure machine
+ 2. Follow E-Star power consumption calculation procedures
+ 3. Measure DUT power consumption during s0, s3, long idle, short idle
+ VERIFICATION:
+ 1. Record the power consumption and follow E-Star calculation methods to get E-Star measurement results
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.2.5
+ 2. Please test 5+ different model machines
+ 3. Power consumption matrix controlled in a separate project specific document
+ 4. E-Star 6 spec can be found here: https://www.energystar.gov/products/specs/sites/products/files/Final%20Version%206.0%20Computers%20Program%20Requirements%20%28Rev.%20Oct-2013%29.pdf
+
diff --git a/jobs/kittyhawk/baseOS/graphics.txt.in b/jobs/kittyhawk/baseOS/graphics.txt.in
new file mode 100644
index 0000000..3644aa1
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/graphics.txt.in
@@ -0,0 +1,146 @@
+plugin: manual
+id: kittyhawk/baseOS/graphics/multiple-user-account-switch
+_description:
+ PURPOSE:
+ 1. Verify that logging in and out to different user accounts work correctly
+ STEPS:
+ 1. Create 2 user accounts in the system
+ 2. Log out and log in
+ VERIFICATION:
+ 1. In step 2, lightdm should appear after log out, desktop should appear after log in.
+ NOTES:
+ 1. Should be tested on at least Intel UMA platforms. Other graphics configurations are outside of the scope.
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/multi-monitor
+_description:
+ PURPOSE:
+ 1. Verify that multi-monitor works correctly with different graphics configurations
+ STEPS:
+ 1. After install the image under test, connect the system under test to external monitor
+ VERIFICATION:
+ 1. Desktop should be displayed on external monitor
+ NOTES:
+ 1. Should be tested on at least Intel UMA platforms. Other graphics configurations are outside of the scope.
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/hybrid-graphics-hotplug
+_description:
+ PURPOSE:
+ 1. Verify that Hybrid Graphics support should support display hot plug (connecting to external monitors via all available ports should work without requiring user to log out)
+ STEPS:
+ 1. Test details controlled by another test matrix
+ VERIFICATION:
+ 1. Hybrid Graphics support should support display hot plug (connecting to external monitors via all available ports should work without requiring user to log out)
+ NOTES:
+ 1. Should be tested on at I+A, I+N & A+A platforms, test details controlled by another test matrix
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.10
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/gfx-name
+_description:
+ PURPOSE:
+ 1. Verify that gfx card name should be displayed in System Settings
+ STEPS:
+ 1. Launch sysinfo by entering sysinfo in Dash
+ 2. Go to Hardware tab > select Graphc card in drop-down list at upper-right side of sysinfo panel
+ 3. Expand the "VGA compatible controller" items
+ VERIFICATION:
+ 1. gfx card name should be displayed
+ NOTES:
+ 1. Should be tested on at I+A, I+N & A+A and UMA platforms
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.11
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/hybrid-graphics
+_description:
+ PURPOSE:
+ 1. Verify that systems which contain both integrated and discrete GPUs must be able to use either GPU
+ STEPS:
+ 1. Test details controlled by another test matrix
+ VERIFICATION:
+ 1. systems which contain both integrated and discrete GPUs must be able to use either GPU
+ NOTES:
+ 1. Should be tested on at I+A, I+N & A+A platforms, test details controlled by another test matrix
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.9, #1.2.11
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/hidpi-lowest-range
+_description:
+ PURPOSE:
+ 1. Verify that 135 DPI (1366*768@11.6") is supported
+ STEPS:
+ 1. install image and boot into OS on a machine with 11.6" screen
+ 2. Go to system settings > displays
+ 3. Make sure the resolution is set to 1366*768
+ 4. Make sure settings in UI scales "Scale menu and title bars" & "Scale all window contents to match" can be correctly applied.
+ VERIFICATION:
+ 1. the display should not be corrupt when scaled
+ 2. font sizes in the panel, Dash and menus should be adjusted for DPI. Launcher size should be adjusted too.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.15.1
+ 2. Example target device: Dell Inspiron 11 3000 (Bonsai)
+ 3. Details on HiDPI verification is listed in "hidpi-tuning-scale-menu-title" & "hidpi-tuning-scale-window" test case
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/hidpi-mid-range
+_description:
+ PURPOSE:
+ 1. Verify that 165 DPI (1920*1080@13.3") is supported
+ STEPS:
+ 1. install image and boot into OS on a machine with 13.3" screen
+ 2. Go to system settings > displays
+ 3. make sure the resolution is set to 165 DPI (1920*1080)
+ 4. Make sure settings in UI scales "Scale menu and title bars" & "Scale all window contents to match" can be correctly applied.
+ VERIFICATION:
+ 1. the display should not be corrupt when scaled
+ 2. font sizes in the panel, Dash and menus should be adjusted for DPI. Launcher size should be adjusted too.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.15.2
+ 2. Example target device: DELL XPS 13 with fHD screen (Spyder-ULT)
+ 3. Details on HiDPI verification is listed in "hidpi-tuning" test case
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/hidpi-tuning-scale-menu-title
+_description:
+ PURPOSE:
+ 1. Verify that it's obvious and easy for users to make text/windows/dash/launcher/menus bigger or smaller with "Scale menu and title bars" bar
+ STEPS:
+ 1. install image and boot into OS
+ 2. Go to system settings > displays
+ 3. Toggle the "Scale menu and title bars" bar" bar from 0.5 ~ 4
+ VERIFICATION:
+ 1. "Scale menu and title bars" toggle bar should be available in Display settings after completing step 2
+ 2. The display should not be corrupt when scaled in step 3
+ 3. Font sizes in the panel, Dash and menus should be adjusted for DPI. Launcher size should be adjusted too after step 3
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.15.4, #1.15.5
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/hidpi-tuning-scale-window
+_description:
+ PURPOSE:
+ 1. Verify that it's obvious and easy for users to make text/windows/dash/launcher/menus bigger or smaller with "Scale all window contents to match" settings
+ STEPS:
+ 1. install image and boot into OS
+ 2. Go to system settings > displays
+ 3. Connect system to an external monitor
+ 4. Try each option in "Scale all window contents to match"
+ VERIFICATION:
+ 1. "Scale all window contents to match" toggle bar should be available in Display settings after completing step 2
+ 2. TBD
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.15.4, #1.15.5
+
+plugin: manual
+id: kittyhawk/baseOS/graphics/hidpi-keyboard
+_description:
+ PURPOSE:
+ 1. (Write here test purpose)
+ STEPS:
+ 1. (Write here test execution procedure step by step)
+ VERIFICATION:
+ 1. (Write here test verification procedure step by step)
+ NOTES:
+ 1. (Add here optional notes or remove the whole section)
+
diff --git a/jobs/kittyhawk/baseOS/hardware-support.txt.in b/jobs/kittyhawk/baseOS/hardware-support.txt.in
new file mode 100644
index 0000000..5d5d876
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/hardware-support.txt.in
@@ -0,0 +1,354 @@
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/accelerometer
+_description:
+ PURPOSE:
+ 1. Verify that system can support accelerometer daemons for HDD protection
+ STEPS:
+ 1. (Write here test execution procedure step by step)
+ VERIFICATION:
+ 1. (Write here test verification procedure step by step)
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.2
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/combo-audio-jack-osd
+_description:
+ PURPOSE:
+ 1. Verify provide OSD on plug of audio jack for user to choose between microphone, headphone/speakers, or headset if it is a four ring jack.
+ STEPS:
+ 1. Need more detail information after feature implement
+ VERIFICATION:
+ 1. Does the provide OSD on plug of audio jack displayed?
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.5
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/display-osd
+_description:
+ PURPOSE:
+ 1. Verify On-screen display (OSD) notification should be shown when a user presses a hotkey to switch display settings.
+ STEPS:
+ 1. Plug external monitor cable (VGA/HDMI/DP) on system and press display hotkey
+ VERIFICATION:
+ 1. On-screen display (OSD) notification should be shown on each mode (Internal only, mirror mode, external only, extend mode)
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.4
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/wireless-osd
+_description:
+ PURPOSE:
+ 1. Verify On-screen display (OSD) notification should be shown when a user presses a hotkey to enable/disable WiFi or bluetooth.
+ STEPS:
+ 1. Press Wireless dedicated hardware key/Wireless hotkey to enable/disable WiFi or bluetooth.
+ VERIFICATION:
+ 1. WiFi and/or Bluetooth OSD notification shown
+ 2. Should test on Wireless dedicated hardware key/Wireless hotkey
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.3
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchscreen-tap
+_description:
+ PURPOSE:
+ 1. Verify touchscreen tap function works correctly
+ STEPS:
+ 1. install image onto system
+ 2. use touchscreen to perform tap
+ VERIFICATION:
+ 1. tap should work as left click
+ 2. cursor should jump to location of tap
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.1
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchscreen-drag-drop
+_description:
+ PURPOSE:
+ 1. Verify touchscreen drag & drop function works correctly
+ STEPS:
+ 1. install image onto system
+ 2. use touchscreen to perform drag & drop on browsers & files
+ VERIFICATION:
+ 1. drag & drop feature should work correctly
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.1
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchpad-click
+_description:
+ PURPOSE:
+ 1. Verify touchpad click works correctly
+ STEPS:
+ 1. install image onto system
+ 2. use touchpad to perform single & double click(s) with right/left button
+ VERIFICATION:
+ 1. touchspad click should work without any problems
+ 2. should verify on available touchpads such as PS/2, i2c
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.2
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.19
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchpad-scroll-default
+_description:
+ PURPOSE:
+ 1. Verify default touchpad scroll method is 2-finger scroll
+ STEPS:
+ 1. install image onto system
+ 2. launch any browser (Nautilus, web browser, console) that require scrolling to view complete contents
+ 3. use 2 fingers on touchpad to scroll left/right & up/down
+ 4. go to system settings > mouse & touchpad
+ 5. make sure "two finger scroll" is checked
+ VERIFICATION:
+ 1. contents in browser should correctly scroll left/right & up/down according to touchpad input
+ 2. "two finger scroll" in system settings > mouse & touchpad should be checked
+ 3. should verify on available touchpads such as PS/2, i2c
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.2
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.19
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchpad-2finger-scroll
+_description:
+ PURPOSE:
+ 1. Verify touchpad 2-finger scroll works correctly
+ STEPS:
+ 1. install image onto system
+ 2. launch any browser (Nautilus, web browser, console) that require scrolling to view complete contents
+ 3. use 2 fingers on touchpad to scroll left/right & up/down
+ VERIFICATION:
+ 1. contents in browser should correctly scroll left/right & up/down according to touchpad input
+ 2. should verify on available touchpads such as PS/2, i2c
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.2
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.19
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchpad-sidebar-scroll
+_description:
+ PURPOSE:
+ 1. Verify touchpad sidebar scroll works correctly
+ STEPS:
+ 1. install image onto system
+ 2. launch any browser (Nautilus, web browser, console) that require scrolling to view complete contents
+ 3. go to system settings > mouse & touchpad
+ 4. uncheck "two finger scroll"
+ 5. use sidebar to scroll left/right & up/down
+ VERIFICATION:
+ 1. contents in browser should correctly scroll left/right & up/down according to touchpad input
+ 2. should verify on available touchpads such as PS/2, i2c
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.2
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.19
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchpad-1finger-tap
+_description:
+ PURPOSE:
+ 1. Verify touchpad 1-finger tap works correctly
+ STEPS:
+ 1. install image onto system
+ 2. Launch Nautilus browser and do single tap on touchpad with one finger on any file or folder
+ 3. Launch Nautilus browser and do double tap on touchpad with one finger on any file or folder
+ VERIFICATION:
+ 1. tap should work as left click
+ 2. should verify on available touchpads such as PS/2, i2c
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.2
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.19
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchpad-2fingers-tap
+_description:
+ PURPOSE:
+ 1. Verify touchpad 2-finger tap works correctly
+ STEPS:
+ 1. install image onto system
+ 2. Launch Nautilus browser & tap touchpad with 2 fingers on any file or folder
+ VERIFICATION:
+ 1. 2 finger tap should work as right click
+ 2. should verify on available touchpads such as PS/2, i2c
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.2
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.19
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchpad-pinch
+_description:
+ PURPOSE:
+ 1. Verify touchpad pinch works correctly
+ STEPS:
+ 1. install image onto system
+ 2. Launch web browser and go to maps.google.com
+ 3. pinch 2 fingers together on touchpad
+ 4. pinch 2 fingers apart on touchpad
+ VERIFICATION:
+ 1. pinching 2 fingers together should zoom-out google map
+ 2. pinching 2 fingers apart should zoom-in google map
+ 3. should verify on available touchpads such as PS/2, i2c
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.2
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.19
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/blu-ray-write
+_description:
+ PURPOSE:
+ 1. Verify blu-ray write function works correctly
+ STEPS:
+ 1. install image onto system
+ 2. insert a blank blu-ray disk into ODD
+ 3. use cd/dvd burning tools such as Brasero to burn files into disk
+ VERIFICATION:
+ 1. files should be successfully burnt into disk
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.16
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/blu-ray-read
+_description:
+ PURPOSE:
+ 1. Verify blu-ray read function works correctly
+ STEPS:
+ 1. install image onto system
+ 2. insert a non blank blu-ray disk into ODD
+ VERIFICATION:
+ 1. blu-ray files are shown in Nautilus browser
+ 2. blu-ray files can be accessed by clicking the files
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.16
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/80211ac
+_description:
+ PURPOSE:
+ 1. Verify 802.11ac protocol is supported with 100Mbps sustained throughput
+ STEPS:
+ 1. Install image into any machine with 802.11ac wifi card
+ 2. Connect to any AP that supports 802.11ac protocol
+ 3. Execute command "watch iwconfig" in console
+ 4. suspend machine
+ 5. wake up machine and repeat step 2 ~ 3
+ VERIFICATION:
+ 1. Wifi connection should be successful in step 2 & step 5
+ 2. Observe iwconfig's contents for a while and make sure the "Bit Rate" value exceeds 100 Mb/s (In TPE office a successful ac connection should exceed 300 Mb/s) in step 3 & step 5
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.6
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchscreen-unity7-launcher
+_description:
+ PURPOSE:
+ 1. Verify that user can reveal/hide launcher via touchscreen
+ STEPS:
+ 1. Install image
+ 2. Go to System settings > Appearance > Behavior > set "Auto-hide the launcher" to "on"
+ 3. Use 4-finger to horizontally swipe right on screen to reveal launcher
+ 4. Use 4-finger to horizontally swipe left on screen to hide launcher
+ VERIFICATION:
+ 1. Launcher should be revealed when user horizontally swipe right with 4 fingers
+ 2. Launcher should be hidden when user horizontally swipe left with 4 fingers
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.19.1
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchscreen-unity7-dash
+_description:
+ PURPOSE:
+ 1. Verify that user can reveal/hide dash via touchscreen
+ STEPS:
+ 1. Install image
+ 2. tap screen with 4 fingers
+ 3. tap screen again with 4 fingers
+ VERIFICATION:
+ 1. User can launch dash by tapping screen with 4 fingers
+ 2. User can hide dash by tapping screen with 4 fingers again
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.19.2
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchscreen-unity7-window
+_description:
+ PURPOSE:
+ 1. Verify that user can resize windows via touchscreen
+ STEPS:
+ 1. install image
+ 2. launch any resizable window (ex. text console, nautilus browser)
+ 3. tap window with 3 fingers
+ 4. pinch window in/out with 3 fingers
+ 5. drag the horizontal/vertical/diagonal resize arrows on the sides of window
+ VERIFICATION:
+ 1. tapping window with 3 fingers enters MT Grab Handle mode
+ 2. window can be expanded/folded by pinching fingers apart/together
+ 3. window can be resized by dragging the horizontal/vertical/diagonal resize arrows on the sides of window
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.19.3
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchscreen-unity7-application
+_description:
+ PURPOSE:
+ 1. Verify app can be launched or brought forward via touchscreen
+ STEPS:
+ 1. install image
+ 2. tap any un-launched app on the launcher with 1 finger
+ 3. tap a few more un-launched apps on the launcher with 1 finger
+ 4. re-tap launched apps on the launcher with 1 finger
+ VERIFICATION:
+ 1. tapping an un-launched app on the launcher with 1 finger will launch the app
+ 2. re-tapping a launched app on the launcher with 1 finger will bring the app forward
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.19.4
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/wwan-3g
+_description:
+ PURPOSE:
+ 1. Verify that integrated WWan modems work with 3G cards
+ STEPS:
+ 1. Install image and boot into OS
+ 2. Check if system 3G connection works
+ VERIFICATION:
+ 1. System 3G connection should work
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.7
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/wwan-4g
+_description:
+ PURPOSE:
+ 1. Verify that integrated WWan modems work with 4G cards
+ STEPS:
+ 1. Install image and boot into OS
+ 2. Check if system 4G connection works
+ VERIFICATION:
+ 1. System 4G connection should work
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.7
+
+plugin: manual
+id: kittyhawk/baseOS/hardware-support/touchpad-drag-drop
+_description:
+ PURPOSE:
+ 1. Verify touchpad's drag & drop function works correctly
+ STEPS:
+ 1. install image onto system
+ 2. use touchpad to perform drag & drop on windows & files
+ VERIFICATION:
+ 1. drag & drop feature should work correctly
+ 2. should verify on available touchpads such as PS/2, i2c
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.2
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.19
+ 3. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
diff --git a/jobs/kittyhawk/baseOS/installer.txt.in b/jobs/kittyhawk/baseOS/installer.txt.in
new file mode 100644
index 0000000..61d1b41
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/installer.txt.in
@@ -0,0 +1,63 @@
+plugin: manual
+id: kittyhawk/baseOS/installer/translated
+_description:
+ PURPOSE:
+ 1. Verify that OS installer should be fully translated in all supported languages
+ STEPS:
+ 1. In language selection, select one of the following languages: Catalan, Czech, Danish, German, English, Spanish, Euskera (Basque), French, Galician, Italian, Hungarian, Dutch, Polish, Portuguese, Brazilian Portuguese, Slovak, Finnish, Swedish, Greek, Bulgarian, Russian, Korean, Simplified Chinese, Traditional Chinese, Japanese; continue the install
+ VERIFICATION:
+ 1. The rest of the installation should be displayed in selected language.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.5.1
+ 2. This test is better performed along with kittyhawk/baseOS/core/localization
+
+plugin: manual
+id: kittyhawk/baseOS/installer/default-language
+_description:
+ PURPOSE:
+ 1. Verify the default installer language is English
+ STEPS:
+ 1. Check the default language in language selection step
+ VERIFICATION:
+ 1. It should be English
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.5.2
+
+plugin: manual
+id: kittyhawk/baseOS/installer/additional-install-script-1050927
+_description:
+ PURPOSE:
+ 1. To verify additional install scripts are made available via a debian package
+ STEPS:
+ 1. Install OS and check if package watauga-install-script is installed by default
+ 2. Check the following scripts are in /usr/share/ubuntu/scripts: oem-config-no-recovery.sh, success-general.sh, success-no-recovery.sh
+ VERIFICATION:
+ 1. watauga-install-script should be installed by default and those scripts should be available after the install
+ NOTES:
+ 1. Watauga Bug #1050927
+
+plugin: manual
+id: kittyhawk/baseOS/installer/keep-kernel-parameter-EFI-1032199
+_description:
+ PURPOSE:
+ 1. Verify kernel paremeters are preserved when installing on EFI systems
+ STEPS:
+ 1. Boot the install media and at the grub menu, add a parameter after the "--" (hpet=force, or acpi_osi="!Windows 2009")
+ 2. Continue the install and check the command line parameter in between until the install is complete
+ VERIFICATION:
+ 1. The change should be preserved during install and in /etc/default/grub after the install
+ NOTES:
+ 1. Watauga Bug #1032199
+
+plugin: manual
+id: kittyhawk/baseOS/installer/Dell-specifics-removed-1012807
+_description:
+ PURPOSE:
+ 1. Verify there is no Dell specific functionality, such as OIE,, in the initial installer dialog
+ STEPS:
+ 1. Boot the install media (build with ubuntu recovery), click the canonical icon to launch the initial installer dialog
+ VERIFICATION:
+ 1. There should be no OIE paremeter in the dialog
+ NOTES:
+ 1. Watauga Bug #1012807
+
diff --git a/jobs/kittyhawk/baseOS/keyboard-shortcuts.txt.in b/jobs/kittyhawk/baseOS/keyboard-shortcuts.txt.in
new file mode 100644
index 0000000..979dcfc
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/keyboard-shortcuts.txt.in
@@ -0,0 +1,203 @@
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/app-lens
+_description:
+ PURPOSE:
+ 1. Verify clicking Super + A opens the Application lens
+ STEPS:
+ 1. Press Super + A
+ VERIFICATION:
+ 1. Dash Application lens is opened
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.6
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/ctrl-super-down
+_description:
+ PURPOSE:
+ 1. Verify clicking Ctrl + Super + Down able to minimizes the current window
+ STEPS:
+ 1. Focus on the maximizes window and press Ctrl + Super + Down
+ VERIFICATION:
+ 1. Current window size will restores or minimizes
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.14
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/ctrl-super-left-right
+_description:
+ PURPOSE:
+ 1. Verify clicking Ctrl + Super + Left or Right able to Semi-maximized the current window
+ STEPS:
+ 1. Focus on the any window and press Ctrl + Super + Left or Right
+ VERIFICATION:
+ 1. Current window size will Semi-maximized to left or right
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.15
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/ctrl-super-up
+_description:
+ PURPOSE:
+ 1. Verify clicking Ctrl + Super + Up able to maximizes the current window
+ STEPS:
+ 1. Focus on the non-maximizes window and press Ctrl + Super + Up
+ VERIFICATION:
+ 1. Current window size will maximizes
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.13
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/expo
+_description:
+ PURPOSE:
+ 1. Verify clicking Super + S shows the expo mode: zooms out on all the workspaces and lets you manage them
+ STEPS:
+ 1. Press Super + S and use arrow key to move between workspaces.
+ VERIFICATION:
+ 1. The chosen workspace should be brought to the main view.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.11
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/file-lens
+_description:
+ PURPOSE:
+ 1. Verify clicking Super + F opens the File and Folders lens
+ STEPS:
+ 1. Press Super + F
+ VERIFICATION:
+ 1. Dash File and Folders lens is opened
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.7
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/minimize
+_description:
+ PURPOSE:
+ 1. Verify clicking Ctrl + Super + D minimizes all windows, and clicking it again restores them
+ STEPS:
+ 1. Launch all application on the launcher
+ 2. Press Ctrl + Super + D
+ 3. Press Ctrl + Super + D again
+ VERIFICATION:
+ 1. All windows are minimized in step 2 and restored in step 3.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.10
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/music-len
+_description:
+ PURPOSE:
+ 1. Verify clicking Super + M opens the Music lens
+ STEPS:
+ 1. Press Super + M
+ VERIFICATION:
+ 1. Dash Music lens is opened
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.8
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/spread
+_description:
+ PURPOSE:
+ 1. Verify clicking Super + W shows the spread mode: zooms out on all windows in all workspaces
+ STEPS:
+ 1. Launch all application on the launcher
+ 2. Press Super + W
+ VERIFICATION:
+ 1. All windows are shown.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.9
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/super-hold
+_description:
+ PURPOSE:
+ 1. Verify holding the Super key invokes the sidebar Launcher
+ STEPS:
+ 1. Hold the Super key
+ VERIFICATION:
+ 1. Sidebar launcher should be invoked
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.2
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/super-number
+_description:
+ PURPOSE:
+ 1. Verify clicking Super Key + 1, 2, ..., 0 opens or draws focus to the application whose position in the launcher corresponds to the pressed number
+ STEPS:
+ 1. Click Super + 1
+ 2. Repeat Step 1 with different number
+ VERIFICATION:
+ 1. "Home Folder", "Default Web Browser", "LibreOffice Writer", "LibreOffice Calc", "LibreOffice Impress", "Software Center", "Ubuntu One", "System Settings" should appear correspondingly based on their position in the launcher.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.3
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/super-shift-number
+_description:
+ PURPOSE:
+ 1. Verify clicking Super + Shift + 1,2,...,0, opens a new instance of that application if it is already open
+ STEPS:
+ 1. Launch all application on the launcher
+ 2. Click Super + Shift + 1
+ 3. Repeat Step 2 with different number
+ VERIFICATION:
+ 1. A new instance of "Home Folder", "Default Web Browser", "LibreOffice Writer", "LibreOffice Calc", "LibreOffice Impress", "Ubuntu One" should appear correspondingly based on their position in the launcher.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.4
+ 2. Software Center and System Settings are not applicable.
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/super-tab
+_description:
+ PURPOSE:
+ 1. Verify pressing the Super key shall toggle the Unity Dash view
+ STEPS:
+ 1. Press the Super key
+ VERIFICATION:
+ 1. Unity Dash should appear
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.1
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/switch-app
+_description:
+ PURPOSE:
+ 1. Verify hold Super Key and tap Tab key able to switch applications via launcher
+ STEPS:
+ 1. Press Super Key and tap Tab key to switch applications via launcher.
+ VERIFICATION:
+ 1. The chosen applications should be switch on the launcher.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.12
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/trash
+_description:
+ PURPOSE:
+ 1. Verify clicking Super + T opens the Trash
+ STEPS:
+ 1. Press Super + T
+ VERIFICATION:
+ 1. Trash folder should be opened.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.7.5
+
+plugin: manual
+id: kittyhawk/baseOS/keyboard-shortcuts/mic-mute
+_description:
+ PURPOSE:
+ 1. Verify clicking mic mute hotkey mutes the microphone
+ STEPS:
+ 1. Launch any audio recording app to start recording audio from internal mic
+ 2. While recording, press mic mute key
+ 3. after a few seconds, press mic mute key again
+ 4. playback the recorded audio
+ VERIFICATION:
+ 1. recorded audio should include a silent section when the mic was muted
+ 2. if mic-mute LED is available, check LED status
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.13.8
+
diff --git a/jobs/kittyhawk/baseOS/launcher.txt.in b/jobs/kittyhawk/baseOS/launcher.txt.in
new file mode 100644
index 0000000..5631e2d
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/launcher.txt.in
@@ -0,0 +1,15 @@
+plugin: manual
+id: kittyhawk/baseOS/launcher/default
+_description:
+ PURPOSE:
+ 1. Verify Launcher has "Dash Home", "Home Folder", "Default Web Browser", "LibreOffice Writer", "LibreOffice Calc", "LibreOffice Impress", "Software Center", "System Settings" workspace swither, and Trash icons
+ STEPS:
+ 1. Login system and check icons on the Launcher.
+ 2. Launch all of them and close.
+ VERIFICATION:
+ 1. There should be "Dash Home", "Home Folder", "Default Web Browser", "LibreOffice Writer", "LibreOffice Calc", "LibreOffice Impress", "Software Center", "System Settings" workspace swither, and Trash icons
+ 2. All of them can be opened and closed successfully.
+ 3. No other launchers should exist as default
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.8.1
+
diff --git a/jobs/kittyhawk/baseOS/oobe.txt.in b/jobs/kittyhawk/baseOS/oobe.txt.in
new file mode 100644
index 0000000..17b16b3
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/oobe.txt.in
@@ -0,0 +1,276 @@
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-start
+_description:
+ PURPOSE:
+ 1. Verify oem-config, the first boot program, is run
+ 2. Verify fsck is not run on first boot
+ 3. Verify the startup video is played full-screen and at least 720p quality.
+ 4. Verify that video is played without any lags, and no OSD to detract the experience
+ 5. Verify that the video load time is not longer than 45 seconds.
+ 6. Verify that time required to perform final system configuration in OOBE
+ 7. Verify that the system does not spend time re-compiling dkms during first boot
+ STEPS:
+ 1. Install the system.
+ VERIFICATION:
+ 1. When system is installed, system will restart. oem-config program should run after the restart.
+ 2. At boot time, fsck should not run.
+ 3. A short animated video should be played full-screen and at least 720p quality.
+ 4. An audio track should be played with video
+ 5. No mouse pointer or network popups to detract during the video playback
+ 6. Time between power-on and OOBE video should be no more than 45 seconds.
+ 7. Record the time required to perform final system configuration in OOBE (start: user presses "continue" in media creation page / end: OS login page is shown)
+ 8. "dkms status" should return empty values
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.1, #1.6.2, #1.6.3, #1.6.4, #1.6.16, #1.6.17, #1.6.18
+
+plugin: local
+id: kittyhawk/baseOS/oobe/oem-config-settings
+command:
+ cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk/baseOS/oobe/oem-config-settings.txt*
+_description: oem-config
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-end-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify an audio track is played from the beginning and loop until oem-config is complete.
+ STEPS:
+ 1. Observe if an audio track is played and loop until oem-config is complete
+ VERIFICATION:
+ 1. An audio track should be played from the beginning and loop until oem-config is complete.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.4
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/first-login-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu One should autostart on first login but not subsequent logins (except on China desktop)
+ 2. Verify the user will be presented with three options: Enter existing account information; Create a new account; Opt-out of Ubuntu One setup.
+ STEPS:
+ 1. Log in after completing oem-config, connect to network, verify 1 and 2.
+ 2. Log out and log in.
+ VERIFICATION:
+ 1. Ubuntu One should autostart on first login.
+ 2. The user should be presented with three options: Enter existing account information; Create a new account; Opt-out of Ubuntu One setup.
+ 3. After re-logging in, Ubuntu One should not autorun again.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.9
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/apt-cache-preseed
+_description:
+ PURPOSE:
+ 1. Verify that when system is connected to network, apt-cache should be preseeded (so that user doesn't have to run apt-get update to make software-center work).
+ STEPS:
+ 1. Set up network connection during the install. Complete the install
+ 2. Log in, launch software center
+ 3. Click any app in software center and check if "install" option is available
+ 4. Install any app in software center.
+ 5. Re-install the system, and do not set up network.
+ 6. Reconnect network after installation is successful
+ 7. Repeat step 2 & 3
+ 8. Launch terminal and execute "sudo apt-get update"
+ 9. Repeat step 2 ~ 4
+ VERIFICATION:
+ 1. Install option should be available in step 3
+ 2. Installation should be successful in step 4
+ 3. Install option should not be available in step 7
+ 4. Install option should be available & installation should be successful in step 9
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.10
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/proprietary-driver-kept1
+_description:
+ PURPOSE:
+ 1. Verify that proprietary drivers won't get removed during OOBE
+ STEPS:
+ 1. Build USB startup key
+ 2. For recovery build, check if "d-i oem-config/remove_extras boolean false" is in the /preseed/project.cfg
+ 3. For non-recovery build, check if "d-i oem-config/remove_extras boolean" is present in the /install/preseed.cfg, and if it is, the value should be false
+ VERIFICATION:
+ 1. For recovery build, "d-i oem-config/remove_extras boolean false" should be in the /preseed/project.cfg
+ 2. For non-recovery build, "d-i oem-config/remove_extras boolean false" should be in the /install/preseed.cfg or not present at all
+ NOTES:
+ 1. Watauga Bug #1006481
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/proprietary-driver-kept2-1061188
+_description:
+ PURPOSE:
+ 1. Verify that proprietary drivers won't get removed during OOBE while keeping the config 'd-i oem-config/remove_extras boolean true' in the installer cfg.
+ 2. This is reverting the change made in bug #1006481
+ STEPS:
+ 1. Build USB startup key
+ 2. For recovery build, check if "d-i oem-config/remove_extras boolean true" is in the /preseed/project.cfg
+ 3. For non-recovery build, check if "d-i oem-config/remove_extras boolean" is present in the /install/preseed.cfg, and if it is, the value should be true
+ VERIFICATION:
+ 1. For recovery build, "d-i oem-config/remove_extras boolean true" should be in the /preseed/project.cfg
+ 2. For non-recovery build, "d-i oem-config/remove_extras boolean true" should be in the /install/preseed.cfg or not present at all
+ NOTES:
+ 1. Watauga Bug #1061188
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/apt-mirror-1079271
+_description:
+ PURPOSE:
+ 1. Check apt-mirror selected based on location/locale
+ STEPS:
+ 1. Install system
+ 2. Select Taipei as Timezone
+ 3. Check /etc/apt/source.d.list
+ 4. Recovery system
+ 5. Select Shaghai as Timezone
+ 6. Check /etc/apt/source.d.list
+ VERIFICATION:
+ 1. Verify step3 that apt-mirror is tw.archive.ubuntu.com
+ 2. Verify step6 that apt-mirror is cn.archive.ubuntu.com
+ NOTES:
+ 1. Watuaga bug#1079271
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/oem-config-automation-1076837
+_description:
+ PURPOSE:
+ 1. oem-config automation test
+ STEPS:
+ 1. Create an USB installer
+ 2. Modify /preseed/project.cfg file --> https://pastebin.canonical.com/82539/
+ 3. Create a disk-recipe file under /install folder --> https://pastebin.canonical.com/82539/
+ 4. Boot from USB installer and install the system
+ VERIFICATION:
+ 1. OOBE should be established automatically
+ NOTES:
+ 1. For more details, please see Watauga bug#1076837
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/after-OOBE-recovery-creator
+_description:
+ PURPOSE:
+ 1. Verify that user can create recovery media (CD/DVD/USB) after OOBE
+ STEPS:
+ 1. Install system and boot up to desktop
+ 2. In the dash search "recovery" and select "Recovery Media Creator"
+ 3. Chose DVD/USB to create recovery media, Remember Erase the Disk before create the media.
+ VERIFICATION:
+ 1. Verify the DVD/USB recovery media creator can finished without error
+ 2. Verify the DVD/USB can install and finished the installation.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.13, #1.6.15
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/reset-uuid
+_description:
+ PURPOSE:
+ 1. Verify system reset the dbus UUID (/var/lib/dbus/machine-id) after installation, so that no two machines created from the same master OS image have the same dbus ID.
+ STEPS:
+ 1. Install image
+ 2. Once installation is complete and user enters OS, run "dbus-uuidgen --get" command and record the UUID
+ 3. Reinstall the system
+ 4. Once installation is complete and user enters OS again, run "dbus-uuidgen --get" command and record the UUID
+ VERIFICATION:
+ 1. The UUID in step 2 & step 3 should be different
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.11
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/no-ubuntuOne
+_description:
+ PURPOSE:
+ 1. Verify that Ubuntu One should be completely removed from the image and installer
+ STEPS:
+ 1. Install image
+ 2. Check if Ubuntu One setup page shows up in OOBE
+ 3. Boot into OS after installation is completed
+ 4. Check if Ubuntu One window pops up
+ 5. Check if Ubuntu One cloud icon is shown in panel
+ 6. Check if Ubuntu One is pinned in launcher
+ 7. Launch Dash and check if Ubuntu One can be found in installed apps
+ VERIFICATION:
+ 1. Ubuntu One setup page should not show up in OOBE
+ 2. Ubuntu One window should not pop-up after entering OS when installation is completed
+ 3. Ubuntu One cloud icon should not be shown at desktop panel
+ 4. Ubuntu One should not exist in launcher
+ 5. Ubuntu One should not be found in installed applications
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #2.1.3, #1.6.9
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/first-boot
+_description:
+ PURPOSE:
+ 1. Verify oem-config will run on the first boot
+ STEPS:
+ 1. Install the system.
+ VERIFICATION:
+ 1. When system is installed, system will restart at the last step of installation. oem-config program should run after the restart.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.1
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/no-fsck
+_description:
+ PURPOSE:
+ 1. Ensure OS does not fsck on first boot, regardless of time/date settings in the BIOS/filesystems
+ STEPS:
+ 1. Install the system.
+ VERIFICATION:
+ 1. When system is installed, system will restart at the last step. fsck should *not* run after the reboot.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.2
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/startup-video
+_description:
+ PURPOSE:
+ 1. Verify that OEM-config should start with a short animated video.
+ STEPS:
+ 1. Install the system.
+ VERIFICATION:
+ 1. When system reboots and enters OEM-config, it should start with a short animated video.
+ 2. Video should run full-screen and should be at least 720p quality, in Ogg Vorbis format so that no additional codecs are required.
+ 3. No mouse pointer or network popups to detract during the video playback
+ 4. Audio should also be available and played correctly along with the video
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.3, #1.6.4
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/no-dkms-recomplile
+_description:
+ PURPOSE:
+ 1. Verify that system does not spend time re-compiling DKMS packages at initial system boot
+ STEPS:
+ 1. Install the system.
+ 2. After installation is complete, launch terminal and execute "dkms status"
+ VERIFICATION:
+ 1. no dkms packages should be returned in Step 2
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.16
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/poweron-to-oobe-time
+_description:
+ PURPOSE:
+ 1. Verify that time between power-on and OOBE video should be no more than 45 seconds.
+ STEPS:
+ 1. Install the system.
+ 2. After system reboots to enter OOBE, observe the time needed between poweron ~ the start of OOBE video.
+ VERIFICATION:
+ 1. Time between power-on and OOBE video should be no more than 45 seconds.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.17
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/final-installation-time
+_description:
+ PURPOSE:
+ 1. Log the time required to perform final system configuration in OOBE (lang-pack installation, oem-config removal)
+ STEPS:
+ 1. Install the system.
+ 2. After pressing "continue" in "recovery media creation" page in OOBE, start observing the time needed for system to reach OS log-in screen.
+ VERIFICATION:
+ 1. Take note of the time needed in Step 2
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.18
+
diff --git a/jobs/kittyhawk/baseOS/oobe/oem-config-settings.txt.in b/jobs/kittyhawk/baseOS/oobe/oem-config-settings.txt.in
new file mode 100644
index 0000000..01840b0
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/oobe/oem-config-settings.txt.in
@@ -0,0 +1,139 @@
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/checklist
+_description:
+ PURPOSE:
+ 1. Verify OEM-config guides the user through the following steps: Language selection, OEM EULA, Wifi/Wired Internet configuration, Set location, Keyboard layout, User account creation, Recovery media creation
+ STEPS:
+ 1. After the short video is played, observe all the settings oem-config presents
+ VERIFICATION:
+ 1. OEM-config should guide the user through the following steps: Language selection, OEM EULA, Wifi/Wired Internet configuration, Set location, Keyboard layout, User account creation, Recovery media creation
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.5
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/language
+_description:
+ PURPOSE:
+ 1. Verify product shall prompt the user for a default system language
+ STEPS:
+ 1. Continue after kittyhawk/baseOS/oobe/oem-config-start, note the first setup step in oem-config.
+ VERIFICATION:
+ 1. Product should prompt the user for a default system language
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.6
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/wireless
+_description:
+ PURPOSE:
+ 1. Verify if a wireless adapter is present and there are wireless networks available the user should be prompted to select one.
+ STEPS:
+ 1. Continue after kittyhawk/baseOS/oobe/oem-config-settings/language
+ VERIFICATION:
+ 1. Remove Ethernet cable before this test.
+ 2. Product should prompt the user for available wireless networks after Language select
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.8
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/EULA
+_description:
+ PURPOSE:
+ 1. Verify EULA is displayed and system requires the user to accept or reject the term.
+ STEPS:
+ 1. Continue after kittyhawk/baseOS/oobe/oem-config-settings/language
+ 2. Choose Reject, if available.
+ 3. Choose Accept
+ VERIFICATION:
+ 1. EULA should be displayed and there should be options to accept and/or reject the term.
+ 2. System should stop the setup.
+ 3. System should continue the setup.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.7
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/location-1
+_description:
+ PURPOSE:
+ 1. Verify user shall have the ability to choose a location.
+ 2. Verify the default one is based on location-based information from IP address if system is connected to network.
+ STEPS:
+ 1. Continue after kittyhawk/baseOS/oobe/oem-config-settings/network, note the 4th setup step in oem-config.
+ 2. Record the default location pre-selected by the system.
+ 3. Hard power off the system. Power on the system and connect the system to wired network.
+ 4. Repeat step 2.
+ VERIFICATION:
+ 1. Location selection should be displayed.
+ 2. The default location should be New York.
+ 3. In step 4, the default location should be the where the testing is performed.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.12
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/location-2
+_description:
+ PURPOSE:
+ 1. Verify the defalt location is based on the language chosen if system is not connected to network.
+ 2. Verify if system is connected to network and the location information from IP address is different from where the city will be chosen based on the language setting, the default one should be based on the location information from IP address.
+ STEPS:
+ 1. After choosing a language and not connecting to the network, Record the default location pre-selected by the system.
+ 2. Restart the installation agaion, choose a language that's different from where you are, e.g., choose Korean while you are located in a country other than Korea. Connect to the network. Record the default location pre-selected by the system.
+ VERIFICATION:
+ 1. The location pre-selected by the system should be a city in a country where the chosen language is the princple language.
+ 2. The location pre-selected by the system should be based on the location information from IP address.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.12
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/keyboard
+_description:
+ PURPOSE:
+ 1. Verify user shall have the ability to choose a keyboard layout
+ STEPS:
+ 1. Continue after kittyhawk/baseOS/oobe/oem-config-settings/location
+ VERIFICATION:
+ 1. Keyboard layout selection should be displayed.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.13
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/account
+_description:
+ PURPOSE:
+ 1. Verify user shall have the ability to set up a user account.
+ STEPS:
+ 1. Continue after kittyhawk/baseOS/oobe/oem-config-settings/keyboard
+ VERIFICATION:
+ 1. User account creation setup should appear.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.14
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/recovery
+_description:
+ PURPOSE:
+ 1. Verify recovery media creation is prompted for user to create a recovery image on a USB/DVD media.
+ STEPS:
+ 1. Continue after kittyhawk/baseOS/oobe/oem-config-settings/account
+ VERIFICATION:
+ 1. Recovery media creation setup should appear.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.15
+
+plugin: manual
+id: kittyhawk/baseOS/oobe/oem-config-settings/recovery-media-creator
+_description:
+ PURPOSE:
+ 1. Provide an optional step in the OOBE experience allowing users to create a recovery image on a USB/DVD in addition to or in place of a recovery partition. The user should be presented with the option of running a factory restore or a system recovery which would preserver user data in /home.
+ STEPS:
+ 1. Install system to the OOBE stage
+ 2. Insert USB to USB port /DVD to DVD-Writer
+ 3. Follow the OOBE to "Create Ubuntu Recovery Media" step
+ 4. Create USB/DVD recovery media, Remember Erase the Disk before create the media.
+ VERIFICATION:
+ 1. Verify system can finish the installation after create the recovery media
+ 2. Verify the DVD/USB recovery media creator can finished without error.
+ 3. Verify the DVD/USB can install and finished the installation on other platform.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.6.15
+
diff --git a/jobs/kittyhawk/baseOS/secure-boot.txt.in b/jobs/kittyhawk/baseOS/secure-boot.txt.in
new file mode 100644
index 0000000..cf718a5
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/secure-boot.txt.in
@@ -0,0 +1,76 @@
+plugin: manual
+id: kittyhawk/baseOS/secure-boot/disable
+_description:
+ PURPOSE:
+ 1. Verify secure boot can be disabled via boot manager
+ STEPS:
+ 1. Enter the boot manager menu
+ 2. Choose 'Advanced Options for Ubuntu'
+ 3. Select to disable secure boot
+ 4. Proceed to finish the boot up process
+ 5. Perform this test on Intel Bay trail, Broadwell and HSW systems
+ VERIFICATION:
+ 1. System should load Ubuntu successfully
+ 2. There should not be any text console display in the startup process
+
+plugin: manual
+id: kittyhawk/baseOS/secure-boot/install-ubuntu-key
+_description:
+ PURPOSE:
+ 1. Verify users can manually add the Ubuntu Key via boot manager to load Ubuntu on a secure-boot-enabled system
+ STEPS:
+ 1. Make sure secure boot is enabled
+ 2. Enter the boot manager menu
+ 3. Select and add Ubuntu Key
+ 4. Proceed to continue the boot
+ 5. Perform this test on Intel IVB and HSW, Intel Bay trail, Broadwell systems
+ VERIFICATION:
+ 1. System should load Ubuntu successfully
+ 2. There should not be any text console display in the startup process
+ NOTES:
+ 1. (Add here optional notes or remove the whole section)
+
+plugin: manual
+id: kittyhawk/baseOS/secure-boot/recovery
+_description:
+ PURPOSE:
+ 1. Verify on a secure-boot-enabled system, the system can boot to Ubuntu successfully after factory restore.
+ STEPS:
+ 1. On a secure-boot-enabled system, install Ubuntu OS
+ 2. Restart the system, and enter the boot menu and do a factory restore
+ 3. Perform this test on Intel IVB and HSW, Intel Bay trail, AMD, Broadwell systems
+ VERIFICATION:
+ 1. After the factory restore, the system should be able to load Ubuntu successfully.
+ 2. There should not be any text console or errors displayed in the startup or shutdown.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.6, #1.1.7, #1.1.9
+
+plugin: manual
+id: kittyhawk/baseOS/secure-boot/UEFI-secureboot
+_description:
+ PURPOSE:
+ 1. Verify image can be installed successfully on secure boot enabled UEFI systems
+ STEPS:
+ 1. Set BIOS to UEFI with secure boot.
+ 2. Boot from DVD/USB installer
+ 3. Install Kitty Hawk image.
+ VERIFICATION:
+ 1. Image can be installed successfully and user can enter OS without any problems or errors.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.6
+
+plugin: manual
+id: kittyhawk/baseOS/secure-boot/OS-secureboot
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu can be boot with secure boot enabled
+ STEPS:
+ 1. Set BIOS to UEFI without secure boot.
+ 2. Install Kitty Hawk image.
+ 3. Reboot into BIOS setup and enable secure boot
+ 4. Reboot into OS
+ VERIFICATION:
+ 1. System can reboot into OS without problems or errors after enabling secure boot.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.1.7
+
diff --git a/jobs/kittyhawk/baseOS/startup.txt.in b/jobs/kittyhawk/baseOS/startup.txt.in
new file mode 100644
index 0000000..aeda4ff
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/startup.txt.in
@@ -0,0 +1,91 @@
+plugin: manual
+id: kittyhawk/baseOS/startup/text-free-startup-shutdown
+_description:
+ PURPOSE:
+ 1. Verify no text console should ever be displayed during startup or shutdown.
+ STEPS:
+ 1. Install the system, after login, shut down the system from power menu.
+ 2. Power on the system
+ VERIFICATION:
+ 1. There shouldn't any text console display during startup or shutdown.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.4.1 and #1.4.2
+ 2. Should test with (1) UEFI secure boot enabled & (2) UEFI secure boot un-enabled (3) Legacy mode.
+
+plugin: manual
+id: kittyhawk/baseOS/startup/boot
+_description:
+ PURPOSE:
+ 1. Verify the grub is invisible to the user and the entire boot process take less then 45 seconds
+ STEPS:
+ 1. Install the system and login to Desktop
+ 2. Launch "Terminal" application by pressing Alt+Ctrl+T and type "less /etc/default/grub" in the Terminal
+ 3. Shut down the system from power menu
+ 4. Power on the system
+ VERIFICATION:
+ 1. In step 2, there is one line "GRUB_HIDDEN_TIMEOUT=0" in the file "/etc/default/grub"
+ 2. Grub should *not* be visible to the user after power-on
+ 3. The entire boot process (from post to usable desktop - autologin enabled) should take less than 45 seconds
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.4.6
+ 2. Should test with (1) UEFI secure boot enabled & (2) UEFI secure boot un-enabled (3) Legacy mode.
+
+plugin: manual
+id: kittyhawk/baseOS/startup/poweroff-1093746
+_description:
+ PURPOSE:
+ 1. Verify there is no error message appear during reboot/poweroff
+ STEPS:
+ 1. Boot into system
+ 2. Reboot or Poweroff system
+ 3. Observe the screen
+ VERIFICATION:
+ 1. Make sure there is no error message appear and system can be shutdown/reboot
+ NOTES:
+ 1. Watuaga bug#1093746
+
+plugin: manual
+id: kittyhawk/baseOS/startup/text-free-suspend
+_description:
+ PURPOSE:
+ 1. Verify no text console should ever be displayed during suspend or resume.
+ STEPS:
+ 1. Install the system, after login, suspend the system from power menu.
+ 2. Resume the system
+ VERIFICATION:
+ 1. There shouldn't any text console display during suspend or resume.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.4.3 and #1.4.4
+
+plugin: manual
+id: kittyhawk/baseOS/startup/boot-loader
+_description:
+ PURPOSE:
+ 1. System BIOS should launch the bootloader no more than 5 seconds after power-on on reference hardware. The bootloader should run in “quiet” mode with a timeout value of “0”. In this manner, the bootloader should not be visible to the user.
+ STEPS:
+ 1. Install the system and login to Desktop
+ 2. Launch "Terminal" application by pressing Alt+Ctrl+T and type "less /etc/default/grub" in the Terminal
+ 3. Shut down the system from power menu
+ 4. Power on the system
+ VERIFICATION:
+ 1. Grub should *not* be visible to the user after power-on
+ 2. In step 2, there is one line "GRUB_HIDDEN_TIMEOUT=0" in the file "/etc/default/grub"
+ 3. BIOS should launch the bootloader no more than 5 seconds after power-on
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.4.5
+ 2. Should test with (1) UEFI secure boot enabled & (2) UEFI secure boot un-enabled (3) Legacy mode.
+
+plugin: manual
+id: kittyhawk/baseOS/startup/boot-speed
+_description:
+ PURPOSE:
+ 1. The entire boot process (from post to usable desktop - autologin enabled) should take less than 45 seconds even on the slowest hard drives (5400 RPM HDD).
+ STEPS:
+ 1. Install the system and login to Desktop
+ VERIFICATION:
+ 1. The entire boot process (from post to usable desktop - autologin enabled) should take less than 45 seconds
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.4.6
+ 2. We will measure this on reference hardware that Canonical selects.
+ 3. Should test with (1) UEFI secure boot enabled & (2) UEFI secure boot un-enabled (3) Legacy mode.
+
diff --git a/jobs/kittyhawk/baseOS/third-party-add-on.txt.in b/jobs/kittyhawk/baseOS/third-party-add-on.txt.in
new file mode 100644
index 0000000..735fece
--- /dev/null
+++ b/jobs/kittyhawk/baseOS/third-party-add-on.txt.in
@@ -0,0 +1,87 @@
+plugin: manual
+id: kittyhawk/baseOS/third-party-add-on/Adobe-flash
+_description:
+ PURPOSE:
+ 1. To validate that user is not steered to a non-functional download page. Either direct them to the right place, or else do not prompt them to install Flash at all.
+ STEPS:
+ 1. After install the image, log in to the desktop and open a web browser to watch videos on youtube.com
+ 2. If a prompt pops up requesting user to install Flash, try to install Flash and check if installation is successful.
+ VERIFICATION:
+ 1. As a default, Adobe Flash should be disabled and user should *not* be able to view youtube videos.
+ 2. If no "install Flash" related prompts/links are shown and verification 1 passed, this test case can count as PASSED.
+ 3. If "install Flash" related prompts/links are shown and installation is *not* successful after clicking the prompts/links, this case should count as "FAILED"
+ 4. If "install Flash" related prompts/links are shown and installation is successful (Youtube videos can be played after installation), this case should count as "PASSED"
+ NOTES:
+ 1. Assuming Adobe Flash is required on youtube.com and HTML5 is not enabled.
+ 2. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.10.2, #1.10.3
+
+plugin: manual
+id: kittyhawk/baseOS/third-party-add-on/Java-REMOVED
+_description:
+ PURPOSE:
+ 1. To validate that Java runtime plugin is installed by default
+ STEPS:
+ 1. After install the image, log in to the desktop and open http://www.java.com/en/download/installed.jsp?detect=jre&try=1
+ VERIFICATION:
+ 1. The page should refresh and display your environment within 10-60 sec.
+ NOTES:
+ 1. Requirement #1.9.3
+
+plugin: manual
+id: kittyhawk/baseOS/third-party-add-on/fluendo-mp3
+_description:
+ PURPOSE:
+ 1. Verify that Fluendo MP3 codec is installed by default
+ STEPS:
+ 1. Install image, check if 'gstreamerX.XX-fluendo-mp3' is installed by typing "dpkg -l | grep fluendo" in terminal
+ VERIFICATION:
+ 1. gstreamerX.XX-fluendo-mp3 should be installed by default
+ 2. MP3 'notice' must be displayed.
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.10.1
+
+plugin: manual
+id: kittyhawk/baseOS/third-party-add-on/skype-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify Skype can be found in Software Center and can be installed successfully
+ STEPS:
+ 1. Install image, login, connect to network, and launch Software Center
+ 2. Search for Skype and install
+ 3. Connect to Skype server
+ VERIFICATION:
+ 1. Skype should be available and installed successfully
+ 2. Should connect toSkype server successfully
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.10.8
+
+plugin: manual
+id: kittyhawk/baseOS/third-party-add-on/steam-client-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify Valve Steam Client can be found in Software Center and can be installed successfully
+ STEPS:
+ 1. Install image, login, connect to network, and launch Software Center
+ 2. Search for Valve Steam Client and install
+ 3. Connect to Valve Steam server
+ VERIFICATION:
+ 1. Valve Steam Client should be available and installed successfully
+ 2. Should connect to Valve Steam Client server successfully
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.10.9
+
+plugin: manual
+id: kittyhawk/baseOS/third-party-add-on/chromium-browser-REMOVED
+_description:
+ PURPOSE:
+ 1. Verify Chromium web browser can be found in Software Center and can be installed successfully
+ STEPS:
+ 1. Install image, login, connect to network, and launch Software Center
+ 2. Search for Chromium web browser and install
+ 3. Connect to Internet website
+ VERIFICATION:
+ 1. Chromium web browser should be available and installed successfully
+ 2. Should connect to Internet website successfully
+ NOTES:
+ 1. Kitty Hawk 1.0 (OEM 14.04 LTS) PRD #1.10.10
+