initial for Kittyhawk 2.0 project

24 files changed, 2698 insertions, 0 deletions

diff --git a/jobs/kittyhawk2/baseOS.txt.in b/jobs/kittyhawk2/baseOS.txt.in
new file mode 100644
index 0000000..9ddcb8d
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS.txt.in
@@ -0,0 +1,107 @@
+plugin: local
+id: kittyhawk2/baseOS/core
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/core.txt*
+_description: Core verification
+
+plugin: local
+id: kittyhawk2/baseOS/startup
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/startup.txt*
+_description: System Startup verification
+
+plugin: local
+id: kittyhawk2/baseOS/installer
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/installer.txt*
+_description: OS Installer verification
+
+plugin: local
+id: kittyhawk2/baseOS/oobe
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/oobe.txt*
+_description: Out of box experience verification
+
+plugin: local
+id: kittyhawk2/baseOS/keyboard-shortcuts
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/keyboard-shortcuts.txt*
+_description: Unity UI keyboard shortcuts verification
+
+plugin: local
+id: kittyhawk2/baseOS/launcher
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/launcher.txt*
+_description: Launcher Bar verification
+
+plugin: local
+id: kittyhawk2/baseOS/applications
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/applications.txt*
+_description: Applications verification
+
+plugin: local
+id: kittyhawk2/baseOS/third-party-add-on
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/third-party-add-on.txt*
+_description: Third-party add-ons verification
+
+plugin: local
+id: kittyhawk2/baseOS/graphics
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/graphics.txt*
+_description: Generic tests on graphics cards
+
+plugin: local
+id: kittyhawk2/baseOS/benchmark
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/benchmark.txt*
+_description: Benchmarks
+
+plugin: local
+id: kittyhawk2/baseOS/estar
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/estar.txt*
+_description: To check power management settings are e-star compliant
+
+plugin: local
+id: kittyhawk2/baseOS/canonical-poke
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/canonical-census.txt*
+_description: Canonical Poke Test
+
+plugin: local
+id: kittyhawk2/baseOS/secure-boot
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/secure-boot.txt*
+_description: Secure Boot
+
+plugin: local
+id: kittyhawk2/baseOS/hardware-support
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/hardware-support.txt*
+_description: Verify that system can support new feature
+
+plugin: local
+id: kittyhawk2/baseOS/chipset-support
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/chipset-support.txt*
+_description: Verify that system can support new chipsets
+
+plugin: local
+id: kittyhawk2/baseOS/chipset-support
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/osp1-sw-features.txt*
+_description: Verify that system can support new software features
+
+plugin: manual
+id: kittyhawk2/baseOS/canonical-oem-keyring
+_description:
+ PURPOSE:
+ 1. Verify that trusted updates are allowed from the overlay archive specific to the OEM project.
+ STEPS:
+ 1. Launch a terminal and execute command "sudo dpkg -l | grep canonical-oem-keyring"
+ 2. Check if the file "/usr/share/keyrings/canonical-oem-archive-keyring.gpg" generated by canonical-oem-keyring exists
+ VERIFICATION:
+ 1. Step 1 should return Info on canonical-oem-keyring
+ 2. the file "/usr/share/keyrings/canonical-oem-archive-keyring.gpg" should exist
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.1.17
+
+plugin: manual
+id: kittyhawk2/baseOS/unity-7-custom-scope
+_description:
+ PURPOSE:
+ 1. Verify that Unity 7 custom scopes can be created
+ STEPS:
+ 1. Launch terminal and execute "dpkg -l | grep unity-scope"
+ 2. Check if there are existing installed scopes
+ VERIFICATION:
+ 1. If a list of installed scopes is returned, it means that the scope API works and custom scopes can be created. Count case as passed in this case.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.19.10
+
diff --git a/jobs/kittyhawk2/baseOS/Core/recovery.txt.in b/jobs/kittyhawk2/baseOS/Core/recovery.txt.in
new file mode 100644
index 0000000..ac8deed
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/Core/recovery.txt.in
@@ -0,0 +1,76 @@
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.1.9
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.1.10 - Ubuntu Recovery with perservation of /home partition.
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.1.10 - Ubuntu Recovery with perservation of /home partition.
+
+plugin: manual
+id: kittyhawk2/baseOS/core/recovery/bios-hotkey
+_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 2.0 (OEM 14.04 OSP1) PRD #1.1.11
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.1.12
+
diff --git a/jobs/kittyhawk2/baseOS/applications.txt.in b/jobs/kittyhawk2/baseOS/applications.txt.in
new file mode 100644
index 0000000..77b8d04
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/applications.txt.in
@@ -0,0 +1,108 @@
+plugin: manual
+id: kittyhawk2/baseOS/applications/ubuntu-tour
+_description:
+ PURPOSE:
+ 1. Make sure that Ubuntu Tour is present and can be opened and closed successfully.
+ 2. Make sure that Ubuntu Tour menu does not become unreadable when interrupting a tutorial
+ STEPS:
+ 1. Log in to OS, find Ubuntu Tour, open it and close it.
+ 3. Open it and select a tutorial and follow the first few prompts
+ 4. Click on the 'Back to menu' icon in the lower right of the screen
+ 5. Re-install system and set language to zh_CN during installation process
+ 6. Login to OS and check if Ubuntu tour is automatically run
+ VERIFICATION:
+ 1. Ubuntu Tour should be installed and can be opened with default browser and closed successfully.
+ 2. The "Welcome to the Ubuntu tour!" window appears and all text is readable.
+ 3. In zh_CN locale, the Ubuntu tour is installed and should run locally as a first-run tutorial.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.9.1
+
+plugin: manual
+id: kittyhawk2/baseOS/applications/user-guide
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.9.2
+
+plugin: manual
+id: kittyhawk2/baseOS/applications/sysinfo-removed
+_description:
+ PURPOSE:
+ 1. Make sure that Sysinfo GUI tool for users is removed
+ STEPS:
+ 1. Check if Sysinfo application is removed by input "sysinfo" from Dash search bar
+ VERIFICATION:
+ 1. No "sysinfo" application should bee found
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.9.3
+
+plugin: manual
+id: kittyhawk2/baseOS/applications/no-ubuntu-one
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.9.4
+
+plugin: manual
+id: kittyhawk2/baseOS/applications/software-center
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.9.5
+
+plugin: manual
+id: kittyhawk2/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 webbrowser-app and should work correctly in Step 3 & 4
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.9.6
+
+plugin: manual
+id: kittyhawk2/baseOS/applications/camera
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) 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
+
diff --git a/jobs/kittyhawk2/baseOS/benchmark.txt.in b/jobs/kittyhawk2/baseOS/benchmark.txt.in
new file mode 100644
index 0000000..e996242
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/benchmark.txt.in
@@ -0,0 +1,17 @@
+plugin: user-interact-verify
+id: kittyhawk2/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. collect bootchart.png from /var/log/bootchart
+ NOTES:
+ 1. Measure boot time for image under test.
+ 2. boottime.py can be download from https://bazaar.launchpad.net/~timchen119/oem-qa-tools/oem-qa-tools-boottime-broken/files
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.4.6
+
diff --git a/jobs/kittyhawk2/baseOS/canonical-census.txt.in b/jobs/kittyhawk2/baseOS/canonical-census.txt.in
new file mode 100644
index 0000000..c3ffd5b
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/canonical-census.txt.in
@@ -0,0 +1,39 @@
+plugin: manual
+id: kittyhawk2/baseOS/canonical-poke/send-poke
+_description:
+ PURPOSE:
+ 1. Verify that a counter is included in the OEM images that report fields back to Canonical for 'OEM', 'Model', and 'Region'.
+ STEPS:
+ 1. make sure internect connection is established ("ping poke.canonical.com" to make sure the following steps will work correctly; Or access website 'poke.canonical.com', the site works correctly if browser shows 'OK'. )
+ 2. launch terminal and execute the following commands one by one
+ 3. "sudo rm -rf /var/lib/send-install-count/" to reset poke logs
+ 4. "ls /etc/cron.daily/send-poke", "ls /etc/cron.weekly/send-poke", "ls /etc/cron.monthly/send-poke" "ls /etc/cron.hourly/send-poke" to check available send-poke cron jobs
+ 5. "sudo /etc/cron.daily/send-poke" to manually send daily poke
+ 6. "sudo /etc/cron.weekly/send-poke" to manually send weekly poke
+ 7. "sudo /etc/cron.monthtly/send-poke" to manually send montly poke
+ 6. check contents of files in /var/lib/send-install-count/
+ VERIFICATION:
+ 1. /etc/cron.[daily, weekly, monthly]/send-poke should exist, /etc/cron.hourly/send-poke should *NOT* in step 4
+ 2. /var/lib/send-install-count/firstrun should be created after 1st manual poke (step 5), content should be the date the first poke is performed, file should "NOT" be updated starting from the 2nd poke (steps 6~ 7 or repeated steps of 5~7)
+ 3. /var/lib/send-install-count/counter should be created with content "1" after step 5, and number will +1 after each repeat of step 5
+ 4. /var/lib/send-install-count/counter-weekly should be created with content "1" after step 6, and number will +1 after each repeat of step 6
+ 5. /var/lib/send-install-count/counter-monthly should be created with content "1" after step 7, and number will +1 after each repeat of step 7
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.1.18
+
+plugin: manual
+id: kittyhawk2/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
+ 2. Verify census sciprt won't caused update-initramfs error
+ VERIFICATION:
+ 1. The system info and the number of times system checks in should match the info shown on the server side
+ 2. run "sudo update-initramfs -u"
+ 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. There is no error occured during update-initramfs
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.1.18
+
diff --git a/jobs/kittyhawk2/baseOS/chipset-support.txt.in b/jobs/kittyhawk2/baseOS/chipset-support.txt.in
new file mode 100644
index 0000000..a8213fb
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/chipset-support.txt.in
@@ -0,0 +1,87 @@
+plugin: manual
+id: kittyhawk2/baseOS/chipset-support/haswell
+_description:
+ PURPOSE:
+ 1. Make sure that the image doesn't break anythiing else after including Intel Haswell driver packages
+ 2. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.11.1, #1.11.2
+
+plugin: manual
+id: kittyhawk2/baseOS/chipset-support/broadwell
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) 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: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.11.6
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.11.6
+
+plugin: manual
+id: kittyhawk2/baseOS/chipset-support/braswell 
+_description:
+ PURPOSE:
+ 1. Verify that system can support Intel Braswell
+ STEPS:
+ 1. Install the build on a Braswell system and non Braswell system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitches during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.11.8
+
+plugin: manual
+id: kittyhawk2/baseOS/chipset-support/skylake 
+_description:
+ PURPOSE:
+ 1. Verify that system can support Intel skylake
+ STEPS:
+ 1. Install the build on a Skylake system and non Skylake system.
+ VERIFICATION:
+ 1. System should be operatable and no graphics glitches during the install and after log in to desktop.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.11.9
+
+plugin: manual
+id: kittyhawk2/baseOS/chipset-support/amd
+_description:
+ PURPOSE:
+ 1. Verify that system can support AMD Kaveri, Beema/Mullins, Richland, Kabini/Temash, Carrizo/Carrizo-L
+ 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 2.0 (OEM 14.04 OSP1) PRD #1.12.1, #1.12.2, #1.12.3, #1.12.4, #1.12.5
+ 2. Actual test matrix controlled by another file
+
diff --git a/jobs/kittyhawk2/baseOS/core.txt.in b/jobs/kittyhawk2/baseOS/core.txt.in
new file mode 100644
index 0000000..1c65704
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/core.txt.in
@@ -0,0 +1,237 @@
+plugin: user-interact-verify
+id: kittyhawk2/baseOS/core/64bit
+command: uname -m|zenity --text-info
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.1
+
+plugin: manual
+id: kittyhawk2/baseOS/core/managed-upgrades
+_description:
+ PURPOSE:
+ 1. Verify that the default turns off automatic notification of new versions of Ubuntu (including LTS)
+ 2. Verify that the HWE stack "update available" notification is disabled
+ 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
+ 3. check if file /var/lib/update-notifier/disable-eol-messages exist
+ VERIFICATION:
+ 1. Value should be 'Never'
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.1.2
+ 2. https://wiki.ubuntu.com/Hwestackeolnotifications
+
+plugin: manual
+id: kittyhawk2/baseOS/core/kernel-version
+_description:
+ PURPOSE:
+ 1. Verify kernel version is correct
+ STEPS:
+ 1. Is "uname -a" the same as or newer than 3.18?
+ VERIFICATION:
+ 1. Kernel version should be 3.18 or newer
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) should use 15.04 HWE Stack
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.1.3
+
+plugin: manual
+id: kittyhawk2/baseOS/core/UEFI
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.5
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.1.8
+
+plugin: local
+id: kittyhawk2/baseOS/core/recovery
+command: cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk2/baseOS/core/recovery.txt*
+_description: OS recovery verification
+
+plugin: manual
+id: kittyhawk2/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", or run "sudo apt-get update && sudo apt-get upgrade"
+ VERIFICATION:
+ 1. OS image shall include all available updates, no updates should be installed when running update commands
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.1.15
+ 2. NOTE: Since there are upstream updates almost everyday, there will always be some updates installed after running the update/upgrade command. There is no way to verify this bug
+
+plugin: manual
+id: kittyhawk2/baseOS/core/pxe
+_description:
+ PURPOSE:
+ 1. Verify installation via a PXE server to provide 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 2.0 (OEM 14.04 OSP1) PRD #1.1.16
+
+plugin: manual
+id: kittyhawk2/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"
+ 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
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.1.20, #1.14.2
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.1
+
+plugin: manual
+id: kittyhawk2/baseOS/core/hybrid-sleep-RAM-32GB
+_description:
+ PURPOSE:
+ 1. Verify "hybrid sleep" is not provided when system RAM is >32GB (when swap=0)
+ STEPS:
+ 1. Install the build with Ubuntu recovery on a system with <32GB memory
+ 2. Install the build with Ubuntu recovery on a system with >=32GB memory
+ VERIFICATION:
+ 1. Hybrid-sleep should only be available on systems with <32GB memory (or when swap is available. To see if swap partition exists, execute "free -m" in terminal)
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.2.2
+
+plugin: manual
+id: kittyhawk2/baseOS/core/hybrid-sleep-DISK-128GB
+_description:
+ PURPOSE:
+ 1. Verify "hybrid sleep" is not provided when system DISK is <128GB (when swap=0)
+ STEPS:
+ 1. Install the build with Ubuntu recovery on a system with <128GB memory
+ 2. Install the build with Ubuntu recovery on a system with >=128GB memory
+ VERIFICATION:
+ 1. Hybrid-sleep should only be available on systems with >=128 memory (or when swap is available. To see if swap partition exists, execute "free -m" in terminal)
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.2.2
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.3
+ 2. Verification on whether hybrid sleep is correctly performed will be in test case "hybrid-sleep-verification"
+
+plugin: manual
+id: kittyhawk2/baseOS/core/hybrid-sleep-verification
+_description:
+ PURPOSE:
+ 1.Verify that system can suspend to both disk and RAM.
+ STEPS:
+ 1. Open any applicaton or browser
+ 2. Press Power menu and select hybrid sleep to sleep the system
+ 3. Wake system up by pressing power button
+ 4. Let system hybrid sleep again
+ 5. Remove AC adapter and Battery for a while and re-install AC or Battery
+ 6. Press Power button to wake up the system
+ 7. Press Power button and select the hybrid sleep from the pop-up menu
+ 8. Repeat step 3~6
+ VERIFICATION:
+ 1. Check that the system resumes from the previous session from s3 (from RAM) in step 3
+ 2. Check that the system resumes from the previous session from s4 (from disk) in step 6
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.2.3
+
+plugin: manual
+id: kittyhawk2/baseOS/core/non-recovery-installation
+_description:
+ PURPOSE:
+ 1. Verify Ubuntu Recovery is not in non-recovery builds
+ STEPS:
+ 1. Install non-recovery builds
+ VERIFICATION:
+ 1. During the install or after the install, there should not be Ubuntu Recovery.
+
+plugin: manual
+id: kittyhawk2/baseOS/core/wireless
+_description:
+ PURPOSE:
+ 1.Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.3.1
+ 2. If there are no unencrypted AP available just skip the unencrypted testing.
+
+plugin: manual
+id: kittyhawk2/baseOS/core/ethernet
+_description:
+ PURPOSE:
+ 1.Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.3.2
+
+
+
diff --git a/jobs/kittyhawk2/baseOS/estar.txt.in b/jobs/kittyhawk2/baseOS/estar.txt.in
new file mode 100644
index 0000000..d791a12
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/estar.txt.in
@@ -0,0 +1,157 @@
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.4
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.4
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.4
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.4
+
+plugin: manual
+id: kittyhawk2/baseOS/estar/WoL
+requires: 
+_description:
+ PURPOSE:
+ 1. Verify the WoL feature capability via both BIOS and ethtool
+ STEPS:
+ 1. On SUT A, go to BIOS and enable "Wake On LAN" support, proceed to desktop and connect to wired network
+ 2. If no WoL option within BIOS setup menu, please go to step 11.
+ 3. Use ifconfig to get eth MAC address
+ 4. Put machine A to suspend
+ 5. Find a system B on the same network and do 'wakeonlan <A's MAC ADDRESS>'
+ 6. put machine B to suspend again
+ 7. launch gwakeonlan in Unity Dash in machine B
+ 8. click "Add machine" and finish the setup with A's mac address
+ 9. in the machines list enable A by clicking the checkbox on column 0
+ 10. click "Turn On" to wake up A
+ 11. Use ethtool to enable / disable WoL feature (Enable by "$sudo ethtool -s eth0 wol g" / Disable by "$Disable by sudo ethtool -s eth0 wol d"
+ 12. If it's enabled by ethtool, please go through step 3-10
+ VERIFICATION:
+ 1. In step 5, machine A should resume from suspend.
+ 2. In step 10, machine A should resume from suspend.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.2.4, #1.2.7, #1.2.6
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.4, #1.2.7, #1.2.6
+
+plugin: manual
+id: kittyhawk2/baseOS/estar/power-consumption
+_description:
+PURPOSE:
+ 1. Verify SUT power consumption is Energy Star compliant (on UMA and Hybrid Graphics Configs)
+ STEPS:
+ 1. Plugin power adapter to measure machine
+ 2. Follow E-Star power consumption calculation procedures
+ 3. Measure SUT power consumption during s0, s3, long idle, short idle, s5
+ 4. For Discrete configs, please measure in both Power-saving mode and Performance mode. (you can adjust the graphic mode via the Graphics driver)
+ VERIFICATION:
+ 1. Record the power consumption and follow E-Star calculation methods to get E-Star measurement results
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.2.5, #1.2.11, #1.13.9
+ 2. Please test 5+ different model machines (including Hybrid grphics configs: I+A, I+N & A+A platforms should be included, test details controlled by another test matrix)
+ 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
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.8
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.2.9
+ 2. If system battery run out in 2 Hours, just test "On AC Power"
+
+
diff --git a/jobs/kittyhawk2/baseOS/graphics.txt.in b/jobs/kittyhawk2/baseOS/graphics.txt.in
new file mode 100644
index 0000000..27f7919
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/graphics.txt.in
@@ -0,0 +1,174 @@
+plugin: manual
+id: kittyhawk2/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: kittyhawk2/baseOS/graphics/video-out
+_description:
+ PURPOSE:
+ 1. Verify that video-out 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: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.13.10
+
+plugin: manual
+id: kittyhawk2/baseOS/graphics/gfx-name
+_description:
+ PURPOSE:
+ 1. Verify that gfx card name should be displayed in System Settings
+ STEPS:
+ 1. Go to System Settings > Details
+ 2. Check if correct graphic card name is listed in "Graphics" column
+ VERIFICATION:
+ 1. Correct 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 2.0 (OEM 14.04 OSP1) PRD #1.13.11
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.13.9, #1.2.11
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) 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: kittyhawk2/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 2.0 (OEM 14.04 OSP1) 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: kittyhawk2/baseOS/graphics/auto-dpi
+_description:
+ PURPOSE:
+ 1. Verify that machine automatically configure the UI to the best render depending on screen's DPI
+ STEPS:
+ 1. Install image on a machine with resolutions 1920*xxxx or above and observe OOBE process
+ 2. Log into OS after installation is completed
+ 3. Go to System Settings > Displays and check value of "Scale menu & windows" bar
+ 4. launch a terminal and execute "cat .config/oem-unity-auto-scale.log" and check output
+ 5. Execute "rm ~/.config/oem-unity-auto-scale.log" in terminal
+ 6. Modify value in Settings > Displays "Scale menu & windows" bar, panel, Dash, menus & Launcher size should change
+ 7. Logout and login again
+ VERIFICATION:
+ 1. OOBE UI should be readable
+ 2. Value of ""Scale menu & windows" bar should be larger than 1 in step 3
+ 3. Output should be larger than 8 in step 4
+ 4. After step 7, "Scale menu & windows" bar value should scale back to the same value seen in step 3
+ 5. After step 7, panel, Dash, menus & Launcher size should return to default seen during step 3
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.15.4
+ 2. Details please see https://bugs.launchpad.net/kittyhawk/+bug/1287039 comment #22
+
+plugin: manual
+id: kittyhawk2/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 ~ max value
+ 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 2.0 (OEM 14.04 OSP1) PRD #1.15.5
+
+plugin: manual
+id: kittyhawk2/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. The results should match Trusty's behavior, details please refer to http://goo.gl/LO5DeT
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.15.5
+
+plugin: manual
+id: kittyhawk2/baseOS/graphics/hidpi-keyboard
+_description:
+ PURPOSE:
+ 1. Verify that DPI tuning is available via keyboard keys
+ 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 ~ max value with keyboard up & down keys
+ 4. Connect system to an external monitor
+ 5. Try each option in "Scale all window contents to match"
+ VERIFICATION:
+ 1. Screen DPI should be toggled according to the the value toggled with keyboard
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.15.5
+ 2. Has upstream bug https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1296966
+
+
diff --git a/jobs/kittyhawk2/baseOS/hardware-support.txt.in b/jobs/kittyhawk2/baseOS/hardware-support.txt.in
new file mode 100644
index 0000000..8f1facc
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/hardware-support.txt.in
@@ -0,0 +1,383 @@
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/accelerometer
+_description:
+ PURPOSE:
+ 1. Verify that system can support accelerometer daemons for HDD protection
+ STEPS:
+ 1. Launch terminal on a system with accelerometer
+ 2. Execute command "/usr/sbin/hdapsd -p /var/run/hdapsd.pid -d sda -s 15"
+ 3. Tilt machine and check output in terminal
+ VERIFICATION:
+ 1. Terminal should output the following info according to machine tilt movement: 
+ Mon May 5 04:45:12 2014: Starting hdapsd 
+ Mon May 5 04:45:12 2014: Selected interface: HDAPS 
+ Mon May 5 04:45:12 2014: Selected HDAPS input device: /dev/input/event14 
+ Mon May 5 04:45:15 2014: parking 
+ Mon May 5 04:45:17 2014: un-parking
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.13.2
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/wireless-osd
+_description:
+ PURPOSE:
+ 1. Make sure that On-screen display (OSD) notification is 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 2.0 (OEM 14.04 OSP1) PRD #1.13.3
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/display-osd
+_description:
+ PURPOSE:
+ 1. Make sure that On-screen display (OSD) notification is shown when a user presses a hotkey to switch display settings.
+ STEPS:
+ 1. Plug external monitor cable (VGA/HDMI/DP) on system
+ 2. Launch System settings > Display
+ 3. Press display hotkey to cycle display modes
+ 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 2.0 (OEM 14.04 OSP1) PRD #1.13.4
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/combo-audio-jack-osd
+_description:
+ PURPOSE:
+ 1. Make sure that OSD is displayed on plug of audio jack for user to choose between microphone, headphone/speakers, or headset if it is a four ring jack.
+ STEPS:
+ 1. Plug in a headset
+ VERIFICATION:
+ 1. Does OSD show up after plugging in audio jack?
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.13.5
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/80211ac
+_description:
+ PURPOSE:
+ 1. Make sure that 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 terminal (or install latest iw .deb package and execute command "watch iw dev wlan0 link" for more detailed info)
+ 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. Make sure connection is indeed via 802.11ac protocol (if "watch iw dev wlan0 link" output contains "80MHz" in "tx bitrate" line then connection is 802.11ac)
+ 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 2.0 (OEM 14.04 OSP1) PRD #1.13.6
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.13.7
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.13.7
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/blu-ray-write
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.13.16
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/blu-ray-read
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.13.16
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchscreen-tap
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.17.1
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476 
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchscreen-drag-drop
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.17.1
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476 
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-click
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.19
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.2
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-scroll-default
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.19
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.2
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-2finger-scroll
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.19
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.2
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-sidebar-scroll
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.19
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.2
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-1finger-tap
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.19
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.2
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-2fingers-tap
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.19
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.2
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-pinch
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.19
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.2
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-drag-drop
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.19
+ 2. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.2
+ 3. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.3 https://bugs.launchpad.net/kittyhawk/+bug/1285476
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchpad-DKMS-Removed
+_description:
+ PURPOSE:
+ 1. Make sure oem-touchpad-rmi4-1238726-dkms is removed after Kernel updated to 3.13.0-32
+ STEPS:
+ 1. install image
+ 2. run "dkms status"
+ VERIFICATION:
+ 1. oem-touchpad-rmi4-1238726-dkms should NOT be found
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.17.5
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.19.1
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.19.2
+
+plugin: manual
+id: kittyhawk2/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 and hold
+ 4. with 3 fingers, drag window up/down/left/right
+ 5. pinch window in/out with 3 fingers
+ 6. release 3 fingers
+ 7. drag the horizontal/vertical/diagonal resize arrows on the sides of window with 1 finger
+ VERIFICATION:
+ 1. tapping window with 3 fingers enters MT Grab Handle mode
+ 2. window can be dragged with 3 fingers
+ 3. window can be expanded/folded by pinching fingers apart/together
+ 4. window can be resized by dragging the horizontal/vertical/diagonal resize arrows on the sides of window
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.19.3
+
+plugin: manual
+id: kittyhawk2/baseOS/hardware-support/touchscreen-unity7-application
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.19.4
+
+
+
+
diff --git a/jobs/kittyhawk2/baseOS/installer.txt.in b/jobs/kittyhawk2/baseOS/installer.txt.in
new file mode 100644
index 0000000..8f953cd
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/installer.txt.in
@@ -0,0 +1,25 @@
+plugin: manual
+id: kittyhawk2/baseOS/installer/translated
+_description:
+ PURPOSE:
+ 1. Verify that the 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 2.0 (OEM 14.04 OSP1) PRD #1.5.1
+ 2. This test is better performed along with kittyhawk/baseOS/core/localization
+
+plugin: manual
+id: kittyhawk2/baseOS/installer/default-language
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.5.2
+
diff --git a/jobs/kittyhawk2/baseOS/launcher.txt.in b/jobs/kittyhawk2/baseOS/launcher.txt.in
new file mode 100644
index 0000000..7c2446b
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/launcher.txt.in
@@ -0,0 +1,15 @@
+plugin: manual
+id: kittyhawk2/baseOS/launcher/default
+_description:
+ PURPOSE:
+ 1. Make sure that Launcher has correct default 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", "Amazon", "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 2.0 (OEM 14.04 OSP1) PRD #1.8.1
+
diff --git a/jobs/kittyhawk2/baseOS/oobe.txt.in b/jobs/kittyhawk2/baseOS/oobe.txt.in
new file mode 100644
index 0000000..7c8bff8
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/oobe.txt.in
@@ -0,0 +1,160 @@
+plugin: manual
+id: kittyhawk2/baseOS/oobe/first-boot
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.6.1
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/no-fsck
+_description:
+ PURPOSE:
+ 1. Ensure that 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 2.0 (OEM 14.04 OSP1) PRD #1.6.2
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.6.3, #1.6.4
+
+plugin: local
+id: kittyhawk2/baseOS/oobe/oem-config-settings
+command:
+ cat ${PLAINBOX_PROVIDER_DATA}/../jobs/kittyhawk/baseOS/oobe/oem-config-settings.txt*
+_description: oem-config
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.6.10
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/reset-uuid
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.6.11
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/after-OOBE-recovery-creator
+_description:
+ PURPOSE:
+ 1. Verify that a 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 2.0 (OEM 14.04 OSP1) PRD #1.1.13, #1.6.15
+
+plugin: manual
+id: kittyhawk2/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 "customized" dkms packages (ex. for specific platform, proprietary driver) should be returned in Step 2. Only dkms packages with "generic" fixes can be included.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.6.16
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/poweron-to-oobe-time
+_description:
+ PURPOSE:
+ 1. Verify that the time needed 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 2.0 (OEM 14.04 OSP1) PRD #1.6.17
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.6.18
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.6.9, #2.1.3
+
+
diff --git a/jobs/kittyhawk2/baseOS/oobe/oem-config-settings.txt.in b/jobs/kittyhawk2/baseOS/oobe/oem-config-settings.txt.in
new file mode 100644
index 0000000..944db34
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/oobe/oem-config-settings.txt.in
@@ -0,0 +1,139 @@
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/checklist
+_description:
+ PURPOSE:
+ 1. Make sure that OEM-config guides the user through the following steps: Language selection, 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, Wifi/Wired Internet configuration, Set location, Keyboard layout, User account creation, Recovery media creation
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.6.5
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/language
+_description:
+ PURPOSE:
+ 1. Make sure that product prompts 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 2.0 (OEM 14.04 OSP1) PRD #1.6.6
+
+plugin: manual
+id: kittyhawk2/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 2.0 (OEM 14.04 OSP1) PRD #1.6.7
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/wireless
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.6.8
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/location-1
+_description:
+ PURPOSE:
+ 1. Make sure that the user is able to choose a location.
+ 2. Make sure that the default location 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 2.0 (OEM 14.04 OSP1) PRD #1.6.12
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/location-2
+_description:
+ PURPOSE:
+ 1. Make sure that the defalt location is based on the language chosen if system is not connected to network.
+ 2. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.6.12
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/keyboard
+_description:
+ PURPOSE:
+ 1. Make sure that the user is able 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 2.0 (OEM 14.04 OSP1) PRD #1.6.13
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/account
+_description:
+ PURPOSE:
+ 1. Make sure that the user is able 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 2.0 (OEM 14.04 OSP1) PRD #1.6.14
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/recovery
+_description:
+ PURPOSE:
+ 1. Make sure that recovery media creation prompts 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 2.0 (OEM 14.04 OSP1) PRD #1.6.15
+
+plugin: manual
+id: kittyhawk2/baseOS/oobe/oem-config-settings/recovery-media-creator
+_description:
+ PURPOSE:
+ 1. Make sure that 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 is available.
+ 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 2.0 (OEM 14.04 OSP1) PRD #1.6.15
+
diff --git a/jobs/kittyhawk2/baseOS/osp1-sw-features.txt.in b/jobs/kittyhawk2/baseOS/osp1-sw-features.txt.in
new file mode 100644
index 0000000..e15eeba
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/osp1-sw-features.txt.in
@@ -0,0 +1,133 @@
+plugin: manual
+id: kittyhawk2/baseOS/osp1-sw-features/lim-on-default
+_description:
+ PURPOSE:
+ 1. Make sure that LIM is on by default
+ STEPS:
+ 1. Install the image and Login to system.
+ 2. Go to "System Settings"->Appearance->Behavior Tab
+ VERIFICATION:
+ 1. Check if 'In the window's title bar' is selected by default.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.23.1
+ 2. KH2.0 Bug# 1370810
+
+plugin: manual
+id: kittyhawk2/baseOS/osp1-sw-features/click-to-minimize
+_description:
+ PURPOSE:
+ 1. Make sure that click to minimize is on by default
+ STEPS:
+ 1. Install the image and Login to system.
+ 2. Click on Chromium icon on launcher to open a webpage
+ 3. Click on Chromium icon on launcher again
+ 4. Open another Chromium webpage in a new window
+ 5. Click on Chromium icon on launcher again
+ VERIFICATION:
+ 1. Check if there is a single window opened (in Step 3) it will minimize the open window to the launcher bar
+ 2. Check if there are 2 open windows for an application (in Step 5), minimize on click won't work
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.23.2
+ 2. KH2.0 Bug# 1370812
+
+plugin: manual
+id: kittyhawk2/baseOS/osp1-sw-features/natural-scroll
+_description:
+ PURPOSE:
+ 1. Make sure that "Natural-scroll" feature is on by default
+ STEPS:
+ 1. Install the image and Login to system.
+ 2. Go to "System settings" -> "Mouse&Touchpad" -> "Touchpad" tab and check if Natural-scroll option is avalible and selected
+ 3. Click on Chromium icon on launcher to open a webpage
+ 4. Use Touchpad to Browse on a webpage 
+ 5. Use finger to swipe up and down on Touchpad
+ VERIFICATION:
+ 1. Natural-scroll option should be avalible and selected as default setting in Step 2.
+ 2. When user swipe up on touchpad, the webpage should go down
+ 3. When user swipe down on touchpad, the webpage should go up
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.23.4
+ 2. Please Select different touchpad vendor for testing (ie. Synatpics vs. Alps)
+ 3. KH2.0 Bug# 1370813 & Bug# 1399089 
+
+plugin: manual
+id: kittyhawk2/baseOS/osp1-sw-features/lowest-brightness
+_description:
+ PURPOSE:
+ 1. Check the screen display is not off when the brightness is set to the lowest
+ STEPS:
+ 1. Install the image and Login to system.
+ 2. Go to "System settings" -> "Brightness & Lock" and set the brightness to the lowest
+ 3. Click on brightness hotkey and set to the brightness to the lowest
+ VERIFICATION:
+ 1. When the brightness level is set to the lowest, the screen should dim with backlight on but not totally off (blackscreen)
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.23.5
+ 2. KH2.0 Bug# 1370819
+ 
+plugin: manual
+id: kittyhawk2/baseOS/osp1-sw-features/language-select-factory
+_description:
+ PURPOSE:
+ 1. Check if there is a language selection screen for factory installation
+ STEPS:
+ 1. Install Kitty Hawk 2.0 image
+ VERIFICATION:
+ 1. There should be a language selection screen for factory installation purpose
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.23.6
+ 2. KH2.0 Bug# 1370822
+ 3. Wait for Engineer to update the Changes for further verification purpose
+ 
+plugin: manual
+id: kittyhawk2/baseOS/osp1-sw-features/region-specific-install
+_description:
+ PURPOSE:
+ 1. Some applications need to be installed based on the region
+ STEPS:
+ 1. Install Kitty Hawk 2.0 image
+ 2. During oem-config, choose Simplified Chinese (zn-CH) for language selection
+ 3. Wait for the installation complete
+ VERIFICATION:
+ 1. When Simplified Chinese language is selected for installation, Kylin OS should be installed.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.23.7
+ 2. KH2.0 Bug# 1370822
+ 3. Reference: http://goo.gl/mdVBnV
+ 
+plugin: manual
+id: kittyhawk2/baseOS/osp1-sw-features/kernel-parameter-remove
+_description:
+ PURPOSE:
+ 1. Check if kernel parameter "pcie_aspm=force" is removed
+ STEPS:
+ 1. Install Kitty Hawk 2.0 image
+ 2. $cat /proc/cmdline
+ VERIFICATION:
+ 1. Check if kernel parameter "pcie_aspm=force" is removed.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.23.8
+ 2. KH2.0 Bug# 1375650
+
+plugin: manual
+id: kittyhawk2/baseOS/osp1-sw-features/dropbox
+_description:
+ PURPOSE:
+ 1. Check if dropbox application is pre-installed in OS
+ STEPS:
+ 1. Install Kitty Hawk 2.0 image
+ 2. Search Dropbox in Dash and try if it can be launched
+ 3. Install Kylin profile
+ 4. Search Dropbox in Dash and try if it can be launched
+ VERIFICATION:
+ 1. In Step 2, Dropbox should be found and able to be launched
+ 2. In Step 4, Dropbox should NOT be found and NOT able to be launched
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.23.9
+ 2. KH2.0 Bug# 1370828
+
+
+
+ 
+
+
diff --git a/jobs/kittyhawk2/baseOS/secure-boot.txt.in b/jobs/kittyhawk2/baseOS/secure-boot.txt.in
new file mode 100644
index 0000000..81bcb20
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/secure-boot.txt.in
@@ -0,0 +1,76 @@
+plugin: manual
+id: kittyhawk2/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: kittyhawk2/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 HSW, Intel Bay trail, Broadwell, Braswell 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: kittyhawk2/baseOS/secure-boot/UEFI-secureboot
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.6
+
+plugin: manual
+id: kittyhawk2/baseOS/secure-boot/OS-secureboot
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.7
+
+plugin: manual
+id: kittyhawk2/baseOS/secure-boot/recovery
+_description:
+ PURPOSE:
+ 1. Verify that 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 2.0 (OEM 14.04 OSP1) PRD #1.1.6, #1.1.7, #1.1.9
+
diff --git a/jobs/kittyhawk2/baseOS/startup.txt.in b/jobs/kittyhawk2/baseOS/startup.txt.in
new file mode 100644
index 0000000..1ba6f54
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/startup.txt.in
@@ -0,0 +1,59 @@
+plugin: manual
+id: kittyhawk2/baseOS/startup/text-free-startup-shutdown
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) 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: kittyhawk2/baseOS/startup/text-free-suspend
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) PRD #1.4.3 and #1.4.4
+
+plugin: manual
+id: kittyhawk2/baseOS/startup/boot-loader
+_description:
+ PURPOSE:
+ 1. Make sure that system BIOS launch the bootloader no more than 5 seconds after power-on on reference hardware and the bootloader runs in "quiet" mode with a timeout value of "0".
+ 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 2.0 (OEM 14.04 OSP1) 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: kittyhawk2/baseOS/startup/boot-speed
+_description:
+ PURPOSE:
+ 1. Make sure that 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 2.0 (OEM 14.04 OSP1) 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/kittyhawk2/baseOS/third-party-add-on.txt.in b/jobs/kittyhawk2/baseOS/third-party-add-on.txt.in
new file mode 100644
index 0000000..6435077
--- /dev/null
+++ b/jobs/kittyhawk2/baseOS/third-party-add-on.txt.in
@@ -0,0 +1,109 @@
+plugin: manual
+id: kittyhawk2/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
+ 2. Go to Home > Example folder > launch Josh Woodward-Swansong.ogg
+ VERIFICATION:
+ 1. gstreamerX.XX-fluendo-mp3 should be installed by default
+ 2. 'MP3 notice' must be displayed during the first time user does step 2
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.10.1
+
+plugin: manual
+id: kittyhawk2/baseOS/third-party-add-on/Adobe-flash
+_description:
+ PURPOSE:
+ 1. Make sure 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 default 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 2.0 (OEM 14.04 OSP1) PRD #1.10.2, #1.10.3
+
+plugin: manual
+id: kittyhawk2/baseOS/third-party-add-on/chromium-as-default
+_description:
+ PURPOSE:
+ 1. Verify that default browser is be Chromium
+ STEPS:
+ 1. Install Kittyhawk and observe slideshows displayed during isntallation phase 2 & 3
+ 2. After booting into OS, observe icons in the Launcher bar
+ 3. Launch Chromium
+ 4. Open dash and search for Firefox
+ 5. Launch "Tour" from Dash
+ 6. Launch "Help" from Dash
+ VERIFICATION:
+ 1. Slideshows displayed during installation should indicate that Chromium is the default browser.
+ 2. Chromium icon should be in the Launcher bar, Firefox icon should not
+ 3. Chromium can be launched and works correctly
+ 4. Firefox should be removed from system and not found when searching in dash
+ 5. Tour should be launched with Chromium as a default, and should include info on Chromium
+ 6. Help should include info on Chromium
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.18.1
+
+plugin: manual
+id: kittyhawk2/baseOS/third-party-add-on/chromium-touchscreen
+_description:
+ PURPOSE:
+ 1. Verify that users are able to browse with Touchscreen+Keyboard
+ 2. Verify that additional touchscreen features are supported by Chromium
+ STEPS:
+ 1. Install Kittyhawk and boot into OS
+ 2. Launch Chromium
+ 3. Interact with Chromium with touchscreen & keyboard (ex. tap links, scroll page, tap tool bar items, insert search keywords)
+ VERIFICATION:
+ 1. 1-finger touch should open link should open a link
+ 2. 1-finger long touch should open right-click menu
+ 3. 1-finger swipe should be horizontal and vertical scrolling
+ 4. 2-finger pinch-zoom should work correctly.
+ 5. Words should be able to be inserted with keyboard
+ 6. 2-finger swipe left or right should go backwards and forwards on web pages
+ 7. Should support touch enabled text selection
+ 8 . Should support touch enabled drag and drop.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.18.1
+
+plugin: manual
+id: kittyhawk2/baseOS/third-party-add-on/chromium-touchpad
+_description:
+ PURPOSE:
+ 1. Verify that users are able to browse with Touchpad+Keyboard
+ 2. Verify that additional touchpad features are supported by Chromium
+ STEPS:
+ 1. Install Kittyhawk and boot into OS
+ 2. Launch Chromium
+ 3. Interact with Chromium with touchpad (ex. scroll, click)
+ VERIFICATION:
+ 1. 1-finger tap to open link should open a link
+ 2. 2-finger tap should open right-click menu
+ 3. right & left click with touchpad should work correctly
+ 4. 2-finger vertical scrolling with touchpad should be supported
+ 5. 2-finger pinch-zoom should be supported in sites such as google map
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.18.1
+
+plugin: manual
+id: kittyhawk2/baseOS/third-party-add-on/chromium-mouse
+_description:
+ PURPOSE:
+ 1. Verify that users are able to browse with Mouse+Keyboard
+ STEPS:
+ 1. Install Kittyhawk and boot into OS
+ 2. Launch Chromium
+ 3. Interact with Chromium with a mouse (ex. click, double click, scroll)
+ VERIFICATION:
+ 1. scrolling with mouse should be smooth
+ 2. clicking with mouse left/right button should work
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #1.18.1
+
diff --git a/jobs/kittyhawk2/consumer/retail-mode.txt.in b/jobs/kittyhawk2/consumer/retail-mode.txt.in
new file mode 100644
index 0000000..8b19039
--- /dev/null
+++ b/jobs/kittyhawk2/consumer/retail-mode.txt.in
@@ -0,0 +1,217 @@
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/no-ubuntu-one
+_description:
+ PURPOSE:
+ 1. Verify that Ubuntu One should be completely removed in consumer mode
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When screen switches to login screen, press enter to enter retail mode as "guest"
+ 4. Check if Ubuntu One exists in consumer retail mode
+ VERIFICATION:
+ 1. Ubuntu One cloud icon should not be shown at desktop panel
+ 2. Ubuntu One should not exist in launcher
+ 3. Ubuntu One should not be found in installed applications
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.1.3
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/first-boot-mode-default
+_description:
+ PURPOSE:
+ 1. Making sure that Retail mode does not appear by default when installing a system
+ STEPS:
+ 1. Install image and finish installation process
+ VERIFICATION:
+ 1. The “First Boot” configuration wizard appears
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.1
+ 2. RETAIL-NON-UR-ENGLISH-0001, RETAIL-RECOVERY-ENGLISH-0001, RETAIL-NON-UR-CHINESE-0001
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/activate-retail-mode
+_description:
+ PURPOSE:
+ 1. Verify that there is an option to boot into retail mode.
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When screen switches to login screen, press enter to enter retail mode as "guest"
+ VERIFICATION:
+ 1. User is directed to login screen after step 2 and the only session available to the user is “Guest Session”
+ 2. User can enter retail mode OS in step 3
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.1
+ 2. RETAIL-NON-UR-ENGLISH-0002, RETAIL-RECOVERY-ENGLISH-0002, RETAIL-NON-UR-CHINESE-0002
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/setup-first-boot-mode
+_description:
+ PURPOSE:
+ 1. Verify that there is an option during boot or run time to change system back to standard mode.
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When screen switches to login screen press Ctrl+Shift+Alt simultaneously to login as the hidden OEM user
+ 3. The “admin” session will be started
+ 5. Double-click on “Prepare for shipping to end user” in the desktop (password is “oem”)
+ 7. Select “Standard (end-user)”
+ 8. Shutdown the system
+ 9. Boot up the system
+ VERIFICATION:
+ 1. After step 9, the system will run oem-config and configure a user for normal use
+ 2. The oem-config process can be completed and standard OS installation is successful.
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.2
+ 2. RETAIL-NON-UR-ENGLISH-0009, RETAIL-RECOVERY-ENGLISH-0009, RETAIL-NON-UR-CHINESE-0010
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/first-boot-after-configuration
+_description:
+ PURPOSE:
+ 1. Verify that when a user has configured a system, it is not possible to go back to retail mode
+ STEPS:
+ 1. During installation OOBE, select a language for the account (English)
+ 2. Set up networking (or skip)
+ 3. Select a timezone
+ 4. Select a keyboard layout
+ 5. Create an account (name/password). Leave Require my password to log in
+ 6. Once the configuration finishes, do not finish installation and reboot system
+ 7. Long press Ctrl+Shift+Alt (all left) during OOBE Plymouth
+ VERIFICATION:
+ 1. The retail mode account should not exist, user should not be able to enter retail mode in step 7
+ 2. The user account created in step 5 should already exist
+ 3. In Unity-Greeter, typing Ctrl+Shift+Alt does not expose the admin account
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.2
+ 2. RETAIL-NON-UR-ENGLISH-0010, RETAIL-RECOVERY-ENGLISH-0010, RETAIL-NON-UR-CHINESE-0011
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/browse-retail-mode
+_description:
+ PURPOSE:
+ 1. Verify system only support one user with no login prompt
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When unity Greeter with “Guest Session” option is being shown, press enter
+ VERIFICATION:
+ 1. A Guest Session starts without a password prompt and login is successful
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.3
+ 2. RETAIL-NON-UR-ENGLISH-0003, RETAIL-RECOVERY-ENGLISH-0003, RETAIL-NON-UR-CHINESE-0004
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/no-terminal
+_description:
+ PURPOSE:
+ 1. Verify user shall have no access to a terminal from retail mode
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When unity Greeter with “Guest Session” option is being shown, press enter
+ 4. Try to launch the terminal by pressing Ctrl + Alt + T in retail mode
+ 5. Try to launch the terminal in Dash
+ 6. Try to switch to console mode with Ctrl + Alt + F1
+ VERIFICATION:
+ 1. Terminal should not be launched in step 4
+ 2. Terminal should not be launched in step 5
+ 3. Should not be able to switch to console mode in step 6
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.4
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/reset-option
+_description:
+ PURPOSE:
+ 1. Verify that staffs have an option to easily reset the settings and sample content
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When unity Greeter with “Guest Session” option is being shown, press enter
+ 4. Do some system settings and delect/add some pictures,videos,documents
+ 5. Log out
+ 6. Log in
+ VERIFICATION:
+ 1. Settings & contents should reset after step 6
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.13
+ 2. If reset after login, then this case pass.
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/language-flexible
+_description:
+ PURPOSE:
+ 1. Verify that retail mode have flexible installation of region appropriate content
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When screen switches to login screen press Ctrl+Shift+Alt simultaneously to login as the hidden OEM user
+ 4. The “admin” session will be started. Double-click on “Reconfigure System Settings” in the desktop (password is be “oem”)
+ 5. Configure retail mode using the wizard:
+ 6. Select "Chinese" as language, timezone, and a keyboard layout
+ 7. Shutdown the system and boot up the system
+ VERIFICATION:
+ 1. Unity Greeter and the guest retail mode session should be in Chinese
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.14
+ 2. RETAIL-NON-UR-CHINESE-0003
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/localization-sample
+_description:
+ PURPOSE:
+ 1. Verify that retail mode includes localization of sample content
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When screen switches to login screen press Ctrl+Shift+Alt simultaneously to login as the hidden OEM user
+ 4. The “admin” session will be started. Double-click on “Reconfigure System Settings” in the desktop (password is be “oem”)
+ 5. Configure retail mode using the wizard:
+ 6. Select "Chinese" as language, timezone, and a keyboard layout
+ 7. Shutdown the system and boot up the system
+ 8. Check Documents folder
+ VERIFICATION:
+ 1. "Documents" folder contents should be in Chinese
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #2.3.15
+ 2. RETAIL-NON-UR-CHINESE-0004
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/demo
+_description:
+ PURPOSE:
+ 1. Verify that retail mode demo contents are correctly displayed
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When unity Greeter with “Guest Session” option is being shown, press enter
+ 4. Check if all demo files (pictures, videos, ,documents) are correct by repeating the following steps for each demo content:
+ 5. Launch each of the following folders: Pictures, Videos, Documents, Music from Nautilus Home directory
+ 6. Check if each folder contains corresponding picture/video/PDF or LibreOffice/audio files
+ 7. Double-click files in each folder and check if they can be viewed or played
+ VERIFICATION:
+ 1. Each folder should not be empty and should contain demo files
+ 2. Demo files should be able to be correctly viewed or played
+ NOTES:
+ 1. RETAIL-NON-UR-ENGLISH-0004, RETAIL-RECOVERY-ENGLISH-0004, RETAIL-NON-UR-CHINESE-0005
+ 2. RETAIL-NON-UR-ENGLISH-0005, RETAIL-RECOVERY-ENGLISH-0005, RETAIL-NON-UR-CHINESE-0006
+ 3. RETAIL-NON-UR-ENGLISH-0006, RETAIL-RECOVERY-ENGLISH-0006, RETAIL-NON-UR-CHINESE-0007
+ 4. RETAIL-NON-UR-ENGLISH-0007, RETAIL-RECOVERY-ENGLISH-0007, RETAIL-NON-UR-CHINESE-0008
+
+plugin: manual
+id: kittyhawk2/consumer/retail-mode/limited-power-settings
+_description:
+ PURPOSE:
+ 1. Verify that Shutdown/Suspend/Hibernate are disabled in retail mode
+ STEPS:
+ 1. Install image
+ 2. When installation reaches OOBE Plymouth (Ubuntu logo with dots), long press Ctrl+Shift+Alt (all left) and keep the keys pressed until you hear a sound
+ 3. When screen switches to login screen, press enter to enter retail mode as "guest"
+ 4. Click on the power indicator icon
+ VERIFICATION:
+ 1. Suspend/Hibernate/Shutdown options should not be available in step 4
+ 2. Log Out option should be available in step 4
+ NOTES:
+ 1. RETAIL-NON-UR-ENGLISH-0008, RETAIL-RECOVERY-ENGLISH-0008, RETAIL-NON-UR-CHINESE-0009
+
diff --git a/jobs/kittyhawk2/kylin/applications.txt.in b/jobs/kittyhawk2/kylin/applications.txt.in
new file mode 100644
index 0000000..1f63126
--- /dev/null
+++ b/jobs/kittyhawk2/kylin/applications.txt.in
@@ -0,0 +1,183 @@
+plugin: manual
+id: kittyhawk2/kylin/applications/china-photo-scope
+_description:
+ PURPOSE:
+ 1. Verifiy the China photo scope for searching Chinese photos
+ STEPS:
+ 1. Launch terminal and execute "dpkg -l | grep unity-china"
+ 2. Make sure the network is connected
+ 3. Open Dash on the top of Launcher bar, select "photo" icon at bottom of dash menu
+ 4. Type keyword in search bar (ex. "nikon" or "尼康")
+ VERIFICATION:
+ 1. unity-china-photo-scope should be listed in output of step 1
+ 2. Related Chinese scope photos should be listed under the search bar in step 2
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.5.1
+
+plugin: manual
+id: kittyhawk2/kylin/applications/china-music-scope
+_description:
+ PURPOSE:
+ 1. Verifiy the China Music Scope for searching Chinese music
+ STEPS:
+ 1. Launch terminal and execute "dpkg -l | grep unity-china"
+ 2. Make sure the network is connected
+ 3. Open Dash on the top of Launcher bar, select "music" icon at bottom of dash menu
+ 4. Type keyword in search bar (ex. "jay" or "周杰伦")
+ VERIFICATION:
+ 1. unity-china-music-scope should be listed in output of step 1
+ 2. Related Chinese scope music should be listed under the search bar in step 2
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.5.1
+
+plugin: manual
+id: kittyhawk2/kylin/applications/china-video-scope
+_description:
+ PURPOSE:
+ 1. Verifiy the China video Scope for searching Chinese video
+ STEPS:
+ 1. Launch terminal and execute "dpkg -l | grep unity-china"
+ 2. Make sure the network is connected
+ 3. Open Dash on the top of Launcher bar, select "video" icon at bottom of dash menu
+ 4. Type keyword in search bar (ex. "jay" or "周杰伦")
+ VERIFICATION:
+ 1. unity-china-video-scope should be listed in output of step 1
+ 2. Related Chinese scope videos should be listed under the search bar in step 2
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.5.1
+
+plugin: manual
+id: kittyhawk2/kylin/applications/youker-assistant
+_description:
+ PURPOSE:
+ 1. Verify that youker-assistant (优客助手) is included
+ STEPS:
+ 1. Install Kylin image
+ 2. In Dash, enter "Youker" or "优客助手"
+ 3. Verify that Youker Assistant is included
+ 4. Launch Youker Assistant and make sure contents are correct
+ VERIFICATION:
+ 1. Youker Assistant should be included and contents should work
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.5.2
+
+plugin: manual
+id: kittyhawk2/kylin/applications/lunar-calendar
+_description:
+ PURPOSE:
+ 1. Verify the Chinese lunar calendar application is installed
+ STEPS:
+ 1. Click the calendar icon in indicators area on the top right corner of the Desktop
+ 2. Check calendar version with command "dpkg -l | grep chinese-calendar"
+ VERIFICATION:
+ 1. Verify Chinese lunar calendar can be expanded and unexpanded
+ 2. Verify that the Chinese lunar calendar content is correct & display is not corrupted
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.5.3
+
+plugin: manual
+id: kittyhawk2/kylin/applications/weather-indicator
+_description:
+ PURPOSE:
+ 1. Verify the weather forecast indicator is installed
+ STEPS:
+ 1. Click the weather forecast icon in indicators area on the top right corner of the Desktop and set location
+ 2. Check weather indicator version with command "dpkg -l | grep indicator-china-weather"
+ VERIFICATION:
+ 1. Verify user can set weather forecast according to selected locale
+ 2. Verify that weather info correctly corresponds to selected location
+ 3. Verify that indicator-china-weather version is correct
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.5.4
+
+plugin: manual
+id: kittyhawk2/kylin/applications/no-ubuntu-one
+_description:
+ PURPOSE:
+ 1. Verify that Ubuntu One should be completely removed in consumer mode
+ STEPS:
+ 1. Install image and boot into Kylin OS
+ 2. Check if Ubuntu One exists
+ 3. Execute "dpkg -l" and check if Ubuntu One related packages exist
+ VERIFICATION:
+ 1. Ubuntu One cloud icon should not be shown at desktop panel
+ 2. Ubuntu One should not exist in launcher
+ 3. Ubuntu One should not be found in installed applications
+ 4. Ubuntu One should not auto start after logging in to OS
+ 5. "dpkg -l" should not return Ubuntu One packages (ubiquity-plugin-ubuntuone lintian)
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.5.5, #3.9.1
+
+plugin: manual
+id: kittyhawk2/kylin/applications/input-method
+_description:
+ PURPOSE:
+ 1. Verify the input method is fcitx with Sougu engine
+ STEPS:
+ 1. Click the input method icon in indicators area on the top right corner of the Desktop
+ 2. Launch sytem settings > Language support (语言支持)
+ VERIFICATION:
+ 1. The input method is fcitx instead of ibus
+ 2. Input method works and can switch between Chinese and English
+ 3. Sougu engine is available in input method drop list
+ 4. "Language(语言)" tab > "Keyboard input method system(键盘输入方式系统)" default value should be "fcitx" in step 2
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.6.1
+
+plugin: manual
+id: kittyhawk2/kylin/applications/localization
+_description:
+ PURPOSE:
+ 1. Verify the localization of Chromium, Thunderbird and LibreOffice
+ STEPS:
+ 1. Install Kylin image
+ 2. Launch Chromium, Thunderbird & LibreOffice
+ VERIFICATION:
+ 1. Chromium, Thunderbird & LibreOffice contents should be localized to Chinese characters
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.6.2
+
+plugin: manual
+id: kittyhawk2/kylin/applications/launcher
+_description:
+ PURPOSE:
+ 1. Verify that Kuaipan (快盘) icon & LibreOffice icons are added to the Unity launcher as default
+ STEPS:
+ 1. Log into Kylin OS
+ 2. Check if Kuaipan and LibreOffice icons are shown in Launcher
+ VERIFICATION:
+ 1. Kuaipan & LibreOffice icons should be shown in the Unity Launcher
+ 2. Kuaipan & LibreOffice should be able to be launched from Dash and Unity Launcher
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.7.2
+
+plugin: manual
+id: kittyhawk2/kylin/applications/no-ibus
+_description:
+ PURPOSE:
+ 1. Verify that ibus should not be available in Kylin
+ STEPS:
+ 1. Install Kylin image and boot into OS
+ 2. Execute command "dpkg -l | grep ibus"
+ 3. Click the input method icon in indicators area on the top right corner of the Desktop
+ VERIFICATION:
+ 1. no ibus related packages ( ibus ibus-gtk ibus-gtk3 python-ibus ibus-pinyin-db-android libopencc1) should be returned after step 2
+ 2. input method should be fcitx instead of ibus in step 3
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.9.1
+ 2. https://bugs.launchpad.net/kittyhawk/+bug/1293390 comment #5: due to dependency to ibus in unity, ibus related packages cannot be removed completely, so the current workaround is to set indicator-keyboard icon invisible. If ibus indicator is invisible then this case can count as passed in Kittyhawk.
+
+plugin: manual
+id: kittyhawk2/kylin/applications/remove-unwanted-packages
+_description:
+ PURPOSE:
+ 1. Verify that unneeded firefox & 10n packages are removed
+ STEPS:
+ 1. Install Kylin OS
+ 2. Execute command "dpkg - l | grep language"
+ 3. Execute command "dpkg - l | grep firefox"
+ VERIFICATION:
+ 1. The following packages should not be listed in output of step 1 & step 2: language-pack-de language-pack-es language-pack-pt firefox-locale-de firefox-locale-es firefox-locale-pt
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.9.2
+
diff --git a/jobs/kittyhawk2/kylin/core.txt.in b/jobs/kittyhawk2/kylin/core.txt.in
new file mode 100644
index 0000000..74ebfd3
--- /dev/null
+++ b/jobs/kittyhawk2/kylin/core.txt.in
@@ -0,0 +1,41 @@
+plugin: manual
+id: kittyhawk2/kylin/core/base-image
+_description:
+ PURPOSE:
+ 1. Verify that base is 14.04 OEM image
+ STEPS:
+ 1. Install the system and power on the device after installation complete
+ 2. execute command "lsb_release -a"
+ VERIFICATION:
+ 1. make sure output of command indicates that base image version is 14.04 OEM image
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.1.1
+
+plugin: manual
+id: kittyhawk2/kylin/core/kylin-profile
+_description:
+ PURPOSE:
+ 1. Verify that kylin profile is included in the main 14.04 OEM image
+ STEPS:
+ 1. Install the release 14.04 OSP1 image
+ 2. During oem-config, please choose Simplified Chinese (zh_CN) and to finish the installation
+ VERIFICATION:
+ 1. After installation completed, Kylin should be installed depends on Simplified Chinese (zh_CN) language that is chosen for installation
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.1.1
+ 2. If other language is chosen, only Ubuntu OS should be installed. (It is verified with PRD #1.1.8 localization Test)
+
+plugin: manual
+id: kittyhawk2/kylin/core/recovery
+_description:
+ PURPOSE:
+ 1. Verify that Kylin system can recover back to Kylin
+ STEPS:
+ 1. Install the system
+ 2. Reboot the system and press esc or shift+esc to enter grub menu before entering OS
+ 3. After entering grub, press F9 to start Ubuntu recovery
+ VERIFICATION:
+ 1. When Ubuntu recovery is complete, system should still be Kylin
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.1.4
+
diff --git a/jobs/kittyhawk2/kylin/installer.txt.in b/jobs/kittyhawk2/kylin/installer.txt.in
new file mode 100644
index 0000000..5263014
--- /dev/null
+++ b/jobs/kittyhawk2/kylin/installer.txt.in
@@ -0,0 +1,28 @@
+plugin: manual
+id: kittyhawk2/kylin/installer/translated
+_description:
+ PURPOSE:
+ 1. Verify that OS installer should be fully translated in supported languages: English, Simplified Chinese
+ STEPS:
+ 1. Launch OS installer and follow instruction to install OS
+ 2. In language selection page, select one of the following languages: Simplified Chinese
+ 3. Continue the install
+ 4. Repeat step 1 ~ 3 but select English in step 2
+ VERIFICATION:
+ 1. OS installer shall be fully translated in selected language: Simplified Chinese (zh_CN) or English in "ubiquity" & "oem-config"
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.2.1
+
+plugin: manual
+id: kittyhawk2/kylin/installer/default-language
+_description:
+ PURPOSE:
+ 1. Verify the default installer language is Simplified Chinese
+ STEPS:
+ 1. Check the default langauge in language selection step
+ VERIFICATION:
+ 1. It should be Simplified Chinese which is highlighted
+ 2. All related text should be in simplified Chinese during installation process if user uses default language
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.2.2
+
diff --git a/jobs/kittyhawk2/kylin/oobe.txt.in b/jobs/kittyhawk2/kylin/oobe.txt.in
new file mode 100644
index 0000000..4ad8c43
--- /dev/null
+++ b/jobs/kittyhawk2/kylin/oobe.txt.in
@@ -0,0 +1,40 @@
+plugin: manual
+id: kittyhawk2/kylin/oobe/all-languages
+_description:
+ PURPOSE:
+ 1. Verify the first time end-user starts the device the setup shall default to Simplified Chinese.
+ STEPS:
+ 1. Install the system and power on the device after installation complete
+ VERIFICATION:
+ 1. The default language is Simplified Chinese in the language selection page with only English present as the other language
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.3.1
+
+plugin: manual
+id: kittyhawk2/kylin/oobe/slideshow
+_description:
+ PURPOSE:
+ 1. Verify the first time end-user boots a machine with Ubuntu Kylin installed, the user should see the Kylin slideshow
+ STEPS:
+ 1. Install the system
+ 2. Check the slideshows displayed after the first boot
+ 3. After OOBE, complete the required steps and check the slideshows displayed afterwards
+ VERIFICATION:
+ 1. Kylin specific slideshow should be displayed before OOBE
+ 2. Kylin specific slideshow should be displayed during OOBE
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.3.2
+
+plugin: manual
+id: kittyhawk2/kylin/oobe/no-ubuntu1
+_description:
+ PURPOSE:
+ 1. Verify that U1 signup screen shouldn't appear during OOBE
+ STEPS:
+ 1. Install Kylin image
+ 2. During OOBE process, make sure Ubuntu One signup screen does NOT show up
+ VERIFICATION:
+ 1. During OOBE process, Ubuntu One signup screen should NOT show up
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 LTS) PRD #3.3.3
+
diff --git a/jobs/kittyhawk2/kylin/third-party-add-on.txt.in b/jobs/kittyhawk2/kylin/third-party-add-on.txt.in
new file mode 100644
index 0000000..b5a0040
--- /dev/null
+++ b/jobs/kittyhawk2/kylin/third-party-add-on.txt.in
@@ -0,0 +1,88 @@
+plugin: manual
+id: kittyhawk2/kylin/third-party-add-on/fonts
+_description:
+ PURPOSE:
+ 1. Verify the default Chinese font is Hanyi (汉仪)
+ STEPS:
+ 1. Launch "LibreOffice Writer"
+ 3. Choose "汉仪宋体" or "汉仪楷体"
+ 4. Start Chinese Input Method by pressing [CTRL]+[SPACE]
+ 5. Input some Chinese characters
+ 6. Check if the Chinese characters used in Kylin OS are also Hanyi
+ VERIFICATION:
+ 1. The font is "Hanyi"?
+ 2. Chinese characters are in "汉仪宋体" or "汉仪楷体" font in step 5
+ 3. Chinese characters used in Kylin OS are also Hanyi
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.1.3, #3.7.4
+
+plugin: manual
+id: kittyhawk2/kylin/third-party-add-on/Kingsoft-Kuaipan
+_description:
+ PURPOSE:
+ 1. Verify that Kingsoft Kuaipan (金山快盘) cloud file syncing application is included
+ STEPS:
+ 1. Install Kylin Image
+ 2. Click the "Kingsoft Kuaipan (金山快盘)" icon in the launcher
+ 3. Check that "Kingsoft Kuaipan (金山快盘)" works correctly
+ 4. Try to Search "Kauipan" from Dash, and check if it can be launched
+ 5. Check "Kingsoft Kuaipan (金山快盘)" version with command "dpkg -l | grep kuaipan"
+ VERIFICATION:
+ 1. Kingsoft Kuaipan cloud file syncing application is included
+ 2. "Kingsoft Kuaipan (金山快盘)" can be launched and should work correctly in step 3 & 4
+ 3. "Kingsoft Kuaipan (金山快盘)" version should be correct in step 5
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.7.2, #3.7.7
+
+plugin: manual
+id: kittyhawk2/kylin/third-party-add-on/office-suite
+_description:
+ PURPOSE:
+ 1. Verify that the WPS Office Suite from Kingsoft is NOT installed and NOT shown in launcher.
+ 2. Verify that LibreOffice launcher icons are displayed on launcher, and app is still pre-installed.
+ STEPS:
+ 1. Log in to system
+ 2. Check Kingsoft package version with command "dpkg -l | grep kingsoft-office"
+ 3. Check if LibreOffice / WPS icons exist in Launcher bar
+ 4. Launch Dash and enter "calc", "impress", "writer"
+ VERIFICATION:
+ 1. Kingsoft package should NOT be found in Step 2
+ 2. WPS Writer, Presentation, Spreadsheet icons should NOT be displayed on Unity launcher in step 3
+ 3. LibreOffice icons should be displayed on launcher, in step 3
+ 4. LibreOffice can be successfully launched in step 4
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.7.1, #3.7.2
+
+plugin: manual
+id: kittyhawk2/kylin/third-party-add-on/baidu-search
+_description:
+ PURPOSE:
+ 1. Verify Baidu search engine is installed
+ 2. Verify Baidu search result is shown when entering search keyword in the Baidu search bar
+ 3. Verify TN code is in the Baidu search result link
+ STEPS:
+ 1. Click "Firefox Web Browser" from the Launcher bar
+ 2. Enter any search keyword in the Baidu search bar in Firefox
+ VERIFICATION:
+ 1. The default search engine on the right of Navigation Toolbar is Baidu
+ 2. Baidu search result should show
+ 3. Search result link URL should include http://www.baidu.com/s?{keyword}&tn=ubuntuu_dg
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.7.5
+
+plugin: manual
+id: kittyhawk2/kylin/third-party-add-on/baidu-default-home-page
+_description:
+ PURPOSE:
+ 1. Verify that the default Search Engine should be Baidu and use our affiliate code.
+ 2. Verify that the default start page should be start.ubuntu.com which points (at the moment) to Baidu and contains Canonical's affiliate code.
+ STEPS:
+ 1. Click the default browser icon from the Launcher bar
+ VERIFICATION:
+ 1. The default home page is http://start.ubuntu.com/14.04/Baidu/
+ 2. The default hope page should be Baidu Search, with Ubuntu logo at top of search bar and Ubuntu help, Ubuntu store & Ubuntu community links at bottom of search bar.
+ 3. The browser's toolbar search should be Baidu, search results should also be Baidu search result page
+ NOTES:
+ 1. Kitty Hawk 2.0 (OEM 14.04 OSP1) PRD #3.7.5, #3.7.6
+
+