diff options
Diffstat (limited to 'meta/lib/oeqa/manual')
| -rw-r--r-- | meta/lib/oeqa/manual/abat.patch | 64 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/bsp-hw.json | 626 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/build-appliance.json | 96 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/crops.json | 294 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/eclipse-plugin.json | 322 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/kernel-dev.json | 200 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/oe-core.json | 158 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/sdk.json | 32 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/toaster-managed-mode.json | 2572 | ||||
| -rw-r--r-- | meta/lib/oeqa/manual/toaster-unmanaged-mode.json | 1170 |
10 files changed, 5534 insertions, 0 deletions
diff --git a/meta/lib/oeqa/manual/abat.patch b/meta/lib/oeqa/manual/abat.patch new file mode 100644 index 0000000000..1541ac80cb --- /dev/null +++ b/meta/lib/oeqa/manual/abat.patch @@ -0,0 +1,64 @@ +######## +diff --git a/glxgears_check.sh b/glxgears_check.sh +index 17622b8..c4d3b97 100755 +--- a/glxgears_check.sh ++++ b/glxgears_check.sh +@@ -31,7 +31,7 @@ else + + sleep 6 + +- XPID=$( ps ax | awk '{print $1, $5}' | grep glxgears | awk '{print $1}') ++ XPID=$( ps | awk '{print $1, $5}' | grep glxgears | awk '{print $1}') + if [ ! -z "$XPID" ]; then + kill -9 $XPID >/dev/null 2>&1 + echo "glxgears can run, PASS!" +diff --git a/x_close.sh b/x_close.sh +index e287be1..3429f1a 100755 +--- a/x_close.sh ++++ b/x_close.sh +@@ -22,7 +22,7 @@ + # + function close_proc(){ + echo "kill process Xorg" +-XPID=$( ps ax | awk '{print $1, $5}' | egrep "X$|Xorg$" | awk '{print $1}') ++XPID=$( ps | awk '{print $1, $6}' | egrep "X$|Xorg$" | awk '{print $1}') + if [ ! -z "$XPID" ]; then + kill $XPID + sleep 4 +diff --git a/x_start.sh b/x_start.sh +index 9cf6eab..2305796 100755 +--- a/x_start.sh ++++ b/x_start.sh +@@ -24,7 +24,7 @@ + X_ERROR=0 + + #test whether X has started +-PXID=$(ps ax |awk '{print $1,$5}' |egrep "Xorg$|X$" |grep -v grep | awk '{print $1}') ++PXID=$(ps |awk '{print $1,$6}' |egrep "Xorg$|X$" |grep -v grep | awk '{print $1}') + if [ ! -z "$PXID" ]; then + echo "[WARNING] Xorg has started!" + XORG_STATUS="started" +@@ -35,9 +35,11 @@ else + #start up the x server + echo "Start up the X server for test in display $DISPLAY................" + +- $XORG_DIR/bin/X >/dev/null 2>&1 & ++ #$XORG_DIR/bin/X >/dev/null 2>&1 & ++ #sleep 8 ++ #xterm & ++ /etc/init.d/xserver-nodm start & + sleep 8 +- xterm & + fi + XLOG_FILE=/var/log/Xorg.0.log + [ -f $XORG_DIR/var/log/Xorg.0.log ] && XLOG_FILE=$XORG_DIR/var/log/Xorg.0.log +@@ -54,7 +56,7 @@ fi + X_ERROR=1 + fi + +- XPID=$( ps ax | awk '{print $1, $5}' | egrep "X$|Xorg$" |grep -v grep| awk '{print $1}') ++ XPID=$( ps | awk '{print $1, $6}' | egrep "X$|Xorg$" |grep -v grep| awk '{print $1}') + if [ -z "$XPID" ]; then + echo "Start up X server FAIL!" + echo +########
\ No newline at end of file diff --git a/meta/lib/oeqa/manual/bsp-hw.json b/meta/lib/oeqa/manual/bsp-hw.json new file mode 100644 index 0000000000..308a0807f3 --- /dev/null +++ b/meta/lib/oeqa/manual/bsp-hw.json @@ -0,0 +1,626 @@ +[ + { + "test": { + "@alias": "bsps-hw.bsps-hw.boot_and_install_from_USB", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "plugin usb which contains live image burned", + "expected_results": "User can choose install system from usb stick onto harddisk from boot menu or command line option \n" + }, + "2": { + "action": "configure device BIOS to firstly boot from USB if necessary", + "expected_results": "Installed system can boot up" + }, + "3": { + "action": "boot the device and select option \"Install\" from boot menu", + "expected_results": "" + }, + "4": { + "action": "proceed through default install process", + "expected_results": "" + }, + "5": { + "action": "Remove USB, and reboot into new installed system. \nNote: If installation was successfully completed and received this message \"\"(sdx): Volume was not properly unmounted...Please run fsck.\"\" ignore it because this was allowed according to bug 9652.", + "expected_results": "" + } + }, + "summary": "boot_and_install_from_USB" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.live_boot_from_USB", + "author": [ + { + "email": "juan.fernandox.ramos.frayle@intel.com", + "name": "juan.fernandox.ramos.frayle@intel.com" + } + ], + "execution": { + "1": { + "action": "Plugin usb which contains live image burned.", + "expected_results": "User can choose boot from live image on usb stick from boot menu or command line option" + }, + "2": { + "action": "Configure device BIOS to firstly boot from USB if necessary.", + "expected_results": "" + }, + "3": { + "action": "Reboot the device and boot from USB stick.", + "expected_results": "Live image can boot up with usb stick" + } + }, + "summary": "live_boot_from_USB" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.switch_among_multi_applications_and_desktop", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "launch several applications(like contacts, file manager, notes, etc)", + "expected_results": "user could switch among multi applications and desktop" + }, + "2": { + "action": "launch terminal", + "expected_results": "" + }, + "3": { + "action": "switch among multi applications and desktop", + "expected_results": "" + }, + "4": { + "action": "close applications \nNote: The case is for sato image only. ", + "expected_results": "" + } + }, + "summary": "switch_among_multi_applications_and_desktop" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.connman_offline_mode_in_connman-gnome", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "Launch connman-properties after system booting \n\n", + "expected_results": "" + }, + "2": { + "action": "choose \"offline mode\" and check the connection of all network interfaces ", + "expected_results": "All connection should be off after clicking \"offline mode\" . " + } + }, + "summary": "connman_offline_mode_in_connman-gnome" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.check_CPU_utilization_after_standby", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "Start up system", + "expected_results": "" + }, + "2": { + "action": "run \"top\" command and check if there is any process eating CPU time", + "expected_results": "" + }, + "3": { + "action": "make system into standby and resume it", + "expected_results": "" + }, + "4": { + "action": "run \"top\" command and check if there is any difference with the data before standby", + "expected_results": "There should be no big difference before/after standby with \"top\" . " + } + }, + "summary": "check_CPU_utilization_after_standby" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Add_multiple_files_in_media_player", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "Launch media player", + "expected_results": "" + }, + "2": { + "action": "Add multiple files(5 files) in media player at same time (ogg or wav)", + "expected_results": "" + }, + "3": { + "action": "Verify the sound.", + "expected_results": "Media player should be OK with this action, it reproduce files correctly." + } + }, + "summary": "Add_multiple_files_in_media_player" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.video_-_libva_check_(ogg_video_play)", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "check if libva is installed on system (or libogg)", + "expected_results": "" + }, + "2": { + "action": "copy sample ogg file to system", + "expected_results": "" + }, + "3": { + "action": "launch media player can play the ogg file", + "expected_results": "ogg file can be played without problem when libva is used (or libogg) " + } + }, + "summary": "video_-_libva_check_(ogg_video_play)" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.media_player_-_play_video_(ogv)", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "copy sample ogv file to system", + "expected_results": "" + }, + "2": { + "action": "launch media player and make sure it can play the ogv file", + "expected_results": "ogv file can be played without problem" + } + }, + "summary": "media_player_-_play_video_(ogv)" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.media_player_-_stop/play_button_(ogv)", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "copy sample ogv file to system", + "expected_results": "" + }, + "2": { + "action": "launch media player can play the ogv file", + "expected_results": "" + }, + "3": { + "action": "click \"stop\" button to stop playing", + "expected_results": "" + }, + "4": { + "action": "click \"start\" button to resume playing", + "expected_results": "ogv file can be start/stop without problem" + } + }, + "summary": "media_player_-_stop/play_button_(ogv)" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.audio_-_play_(ogg)_with_HDMI", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "copy sample ogg file to system", + "expected_results": "" + }, + "2": { + "action": "connect system with a monitor with HDMI", + "expected_results": "" + }, + "3": { + "action": "launch media player and play the ogg file", + "expected_results": "ogg file can be played without problem with HDMI" + } + }, + "summary": "audio_-_play_(ogg)_with_HDMI" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.audio_-_play_(wav)_with_HDMI", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "copy sample wav file to system", + "expected_results": "" + }, + "2": { + "action": "connect system with a monitor with HDMI", + "expected_results": "" + }, + "3": { + "action": "launch media player and play the wav file", + "expected_results": "wav file can be played without problem, with HDMI" + } + }, + "summary": "audio_-_play_(wav)_with_HDMI" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Graphics_-_ABAT", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "Download ABAT test suite from internal git repository, git clone git://tinderbox.sh.intel.com/git/abat", + "expected_results": "" + }, + "2": { + "action": "Apply following patch to make it work on yocto environment", + "expected_results": "" + }, + "3": { + "action": "Run \"./abat.sh\" to run ABAT test refer to abat.patch", + "expected_results": "All ABAT test should pass. \nNote : If below 3 fails appears ignore them. \n- start up X server fail.. due is already up \n- module [intel_agp] \n- module [i915]" + } + }, + "summary": "Graphics_-_ABAT" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Graphics_-_x11perf_-_2D", + "author": [ + { + "email": "alexandru.c.georgescu@intel.com", + "name": "alexandru.c.georgescu@intel.com" + } + ], + "execution": { + "1": { + "action": "Run \"x11perf -aa10text\" and \"x11perf -rgb10text\"", + "expected_results": "" + }, + "2": { + "action": "Get the FPS result and compare it with upstream graphics data on Sandybridge", + "expected_results": "There should not be big regression between Yocto and upstream linux . " + } + }, + "summary": "Graphics_-_x11perf_-_2D" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Check_if_SATA_disk_can_work_correctly", + "author": [ + { + "email": "yi.zhao@windriver.com", + "name": "yi.zhao@windriver.com" + } + ], + "execution": { + "1": { + "action": "Run fdisk command to create partition on SATA disk. ", + "expected_results": "The SATA device can mount, umount, read and write. " + }, + "2": { + "action": "Mount/Umount \n mke2fs /dev/sda1 \n mount -t ext2 /dev/sda1 /mnt/disk \n umount /mnt/disk", + "expected_results": "" + }, + "3": { + "action": "Read/Write (filesystem) \n touch /mnt/disk/test.txt \n echo abcd > /mnt/disk/test.txt \n cat /mnt/disk/test.txt", + "expected_results": "" + }, + "4": { + "action": "Read/Write (raw) \n dd if=/dev/sda1 of=/tmp/test bs=1k count=1k \n This command will read 1MB from /dev/sda1 to /tmp/test", + "expected_results": "" + } + }, + "summary": "Check_if_SATA_disk_can_work_correctly" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Install_and_boot_from_USB-drive_to_HDD-drive", + "author": [ + { + "email": "david.israelx.rodriguez.castellanos@intel.com", + "name": "david.israelx.rodriguez.castellanos@intel.com" + } + ], + "execution": { + "1": { + "action": "Get a HDD drive.", + "expected_results": "User can choose install system from USB stick on HDD drive from boot menu or command line option \n" + }, + "2": { + "action": "Plugin USB which contains live image burned (USB1).", + "expected_results": "Installed system can boot up." + }, + "3": { + "action": "Configure device BIOS to firstly boot from USB if necessary", + "expected_results": "" + }, + "4": { + "action": "Boot the device and select option \"Install\" from boot menu.", + "expected_results": "" + }, + "5": { + "action": "Make sure that the divice in which image is going to be installed is the HDD drive.", + "expected_results": "" + }, + "6": { + "action": "Proceed through default install process.", + "expected_results": "" + }, + "7": { + "action": "Remove USB1, and reboot into new installed system.", + "expected_results": "" + } + }, + "summary": "Install_and_boot_from_USB-drive_to_HDD-drive" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Install_and_boot_from_USB-drive_to_SD-drive", + "author": [ + { + "email": "david.israelx.rodriguez.castellanos@intel.com", + "name": "david.israelx.rodriguez.castellanos@intel.com" + } + ], + "execution": { + "1": { + "action": "Get a SD-drive with enough free space to install an image.", + "expected_results": "User can choose install system from USB stick on SD-drive from boot menu or command line option. \n" + }, + "2": { + "action": "Plugin USB which contains live image burned (USB1).", + "expected_results": "Installed system can boot up." + }, + "3": { + "action": "Configure device BIOS to firstly boot from USB if necessary", + "expected_results": "" + }, + "4": { + "action": "Boot the device and select option \"Install\" from boot menu.", + "expected_results": "" + }, + "5": { + "action": "Make sure that the device in which image is going to be installed is the SD-drive.", + "expected_results": "" + }, + "6": { + "action": "Proceed through default install process.", + "expected_results": "" + }, + "7": { + "action": "Remove USB1, and reboot into new installed system.", + "expected_results": "" + } + }, + "summary": "Install_and_boot_from_USB-drive_to_SD-drive" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Test_boot_on_serial_communication_SD", + "author": [ + { + "email": "juan.fernandox.ramos.frayle@intel.com", + "name": "juan.fernandox.ramos.frayle@intel.com" + } + ], + "execution": { + "1": { + "action": "1.- Create a yocto project image in a SD card \nexample \n2 - Configure a connection like shown in the link avobe: \nhttps://wiki.yoctoproject.org/wiki/MinnowMax_board_Serial_video_connection_guide \n3 - Verify the Minow Max board is connected to the host \n4 - Boot the system to desktop \n5 - Open a Terminal and check the IP \nIn Terminal type $ifconfig\"", + "expected_results": "Verify you can create a live image \n" + } + }, + "summary": "Test_boot_on_serial_communication_SD" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Test_boot_on_serial_communication_HDD", + "author": [ + { + "email": "juan.fernandox.ramos.frayle@intel.com", + "name": "juan.fernandox.ramos.frayle@intel.com" + } + ], + "execution": { + "1": { + "action": "1 - Create a yocto project image in a HDD \nexample \n2 - Configure a connection like shown in the link avobe: \nhttps://wiki.yoctoproject.org/wiki/MinnowMax_board_Serial_video_connection_guide \n3 - Verify the Minow Max board is connected to the host \n4 - Boot the system to desktop \n5 - Open a Terminal and check the IP \nIn Terminal type $ifconfig\"> ", + "expected_results": "Verify you can create a live image \n" + } + }, + "summary": "Test_boot_on_serial_communication_HDD" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Test_boot_on_serial_communication_USB", + "author": [ + { + "email": "juan.fernandox.ramos.frayle@intel.com", + "name": "juan.fernandox.ramos.frayle@intel.com" + } + ], + "execution": { + "1": { + "action": "1.- Create a yocto project image in a USB \nexample <dd if= core-image-sato-sdk.hddimg of =/dev/sdb>", + "expected_results": "Verify you can create a live image \n" + }, + "2": { + "action": "Configure a connection like shown in the link avobe: \nhttps://wiki.yoctoproject.org/wiki/MinnowMax_board_Serial_video_connection_guide\n\n", + "expected_results": "Video signal is present and not delayed \n" + }, + "3": { + "action": " Verify the Minow Max board is connected to the host", + "expected_results": "Verify the system boot ok and no errors are present \n" + }, + "4": { + "action": " Boot the system to desktop", + "expected_results": " Check that a valid IP is retrieved" + }, + "5": { + "action": " Open a Terminal and check the IP \nIn Terminal type $ifconfig\" ", + "expected_results": "" + } + }, + "summary": "Test_boot_on_serial_communication_USB" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Test_Seek_bar_and_volume_control", + "author": [ + { + "email": "juan.fernandox.ramos.frayle@intel.com", + "name": "juan.fernandox.ramos.frayle@intel.com" + } + ], + "execution": { + "1": { + "action": "Run media player and load a media file ", + "expected_results": "Media player correctly open audio/video file \n" + }, + "2": { + "action": "Verify that seek and volume control are present ", + "expected_results": "Seek bar and volume control are present \n" + }, + "3": { + "action": "Verify that selecting the speaker icon opens the volume control", + "expected_results": "Volume control bar must appear \n" + }, + "4": { + "action": "Verify you can increase and decrease volume level with the volume control", + "expected_results": "Volume level must be increased and decreased \n" + }, + "5": { + "action": "Observe that slider on the seek bar moves along with the video/audio play", + "expected_results": "Video/audio file can be played and slider moves along with the video/audio play \n" + }, + "6": { + "action": "Verify you can navigate the video with the slider back and forward", + "expected_results": "The slider can move back and forward in the seek bar \n" + }, + "7": { + "action": "Verify that seek and volume control are functional in full screen mode", + "expected_results": "Press the full screen mode icon, seek bar and volume control must work fine \n" + }, + "8": { + "action": "Verify that pressing << or >> while playing a file makes the slide goes slow/backwards or faster", + "expected_results": "Verify << and >> works correctly" + } + }, + "summary": "Test_Seek_bar_and_volume_control" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.Check_if_watchdog_can_reset_the_target_system", + "author": [ + { + "email": "yi.zhao@windriver.com", + "name": "yi.zhao@windriver.com" + } + ], + "execution": { + "1": { + "action": "1.Check if watchdog device exist in /dev/ directory. Run command echo 1 > /dev/watchdog and wait for 60s. Then, the target will reboot.", + "expected_results": "The watchdog device exist in /dev/ directory and can reboot the target.\n" + } + }, + "summary": "Check_if_watchdog_can_reset_the_target_system" + } + }, + { + "test": { + "@alias": "bsps-hw.bsps-hw.System_can_boot_up_via_NFS", + "author": [ + { + "email": "yi.zhao@windriver.com", + "name": "yi.zhao@windriver.com" + } + ], + "execution": { + "1": { + "action": "Connect the board's first serial port to your workstation and then start up your favourite serial terminal so that you will be able to interact with the serial console. If you don't have a favourite, picocom is suggested: $ picocom /dev/ttyS0 -b 115200 ", + "expected_results": "The system can boot up without problem\n" + }, + "2": { + "action": "Power up or reset the board and press a key on the terminal when prompted to get to the U-Boot command line ", + "expected_results": "" + }, + "3": { + "action": "Set up the environment in U-Boot: => setenv ipaddr => setenv serverip ", + "expected_results": "" + }, + "4": { + "action": "Download the kernel and boot: => tftp tftp $loadaddr vmlinux => bootoctlinux $loadaddr coremask=0x3 root=/dev/nfs rw nfsroot=: ip=::::edgerouter:eth0:off mtdparts=phys_mapped_flash:512k(boot0),512k(boot1),64k@3072k(eeprom)\n", + "expected_results": "" + } + }, + "summary": "System_can_boot_up_via_NFS" + } + } +] diff --git a/meta/lib/oeqa/manual/build-appliance.json b/meta/lib/oeqa/manual/build-appliance.json new file mode 100644 index 0000000000..82a556e93e --- /dev/null +++ b/meta/lib/oeqa/manual/build-appliance.json @@ -0,0 +1,96 @@ +[ + { + "test": { + "@alias": "build-appliance.build-appliance.Build_core-image-minimal_with_build-appliance-image", + "author": [ + { + "email": "corneliux.stoicescu@intel.com", + "name": "corneliux.stoicescu@intel.com" + } + ], + "execution": { + "1": { + "action": "Build with AUTOREV or download from Autobuilder an image for Yocto Build Appliance. ", + "expected_results": "" + }, + "2": { + "action": "Boot the image under VMWare Player. ", + "expected_results": "" + }, + "3": { + "action": "Build qemux86 core-image-minimal using bitbake command line in the build-appliance-image ", + "expected_results": "" + }, + "4": { + "action": "Launch the image just built using runqemu. ", + "expected_results": "core-image-minimal should build and boot. " + } + }, + "summary": "Build_core-image-minimal_with_build-appliance-image" + } + }, + { + "test": { + "@alias": "build-appliance.build-appliance.Build_a_image_without_error_(added_recipe)", + "author": [ + { + "email": "sstncr@gmail.com", + "name": "sstncr@gmail.com" + } + ], + "execution": { + "1": { + "action": "Launch Build Appliance", + "expected_results": "User could build a image without error and the added package is in the image" + }, + "2": { + "action": "Set \"Machine\" in conf/local.conf, for example, qemuarm", + "expected_results": "" + }, + "3": { + "action": "Install a new package to the image, for example, acpid. Set the following line in conf/local.conf: IMAGE_INSTALL:append = \" acpid\"", + "expected_results": "" + }, + "4": { + "action": "Build a image using bitbake command line, for example, bitbake core-image-minimal", + "expected_results": "" + }, + "5": { + "action": "After build finished, launch the image and check if the added package built into image", + "expected_results": "" + } + }, + "summary": "Build_a_image_without_error_(added_recipe)." + } + }, + { + "test": { + "@alias": "build-appliance.build-appliance.Create_core-image-sato-sdk_using_build_appliance", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Build with AUTOREV or download from Autobuilder an image for Yocto Build Appliance. ", + "expected_results": "" + }, + "2": { + "action": "Boot the image under VMWare Player. ", + "expected_results": "" + }, + "3": { + "action": "Build qemux86 core-image-sato-sdk using bitbake command line in the build-appliance-image ", + "expected_results": "" + }, + "4": { + "action": "Launch the image just built using runqemu. ", + "expected_results": "" + } + }, + "summary": "Create_core-image-sato-sdk_using_build_appliance" + } + } +]
\ No newline at end of file diff --git a/meta/lib/oeqa/manual/crops.json b/meta/lib/oeqa/manual/crops.json new file mode 100644 index 0000000000..5cfa653843 --- /dev/null +++ b/meta/lib/oeqa/manual/crops.json @@ -0,0 +1,294 @@ +[ + { + "test": { + "@alias": "crops-default.crops-default.sdkext_eSDK_devtool_build_make", + "author": [ + { + "email": "francisco.j.pedraza.gonzalez@intel.com", + "name": "francisco.j.pedraza.gonzalez@intel.com" + } + ], + "execution": { + "1": { + "action": "IMPORTANT NOTE: The firsts 5 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n\n", + "expected_results": "" + }, + "2": { + "action": " Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n", + "expected_results": "" + }, + "3": { + "action": "Create the following tree of files <crops-esdk-workdir-workspace>/sdkext/files/myapp <crops-esdk-workdir-workspace>/sdkext/files/myapp_cmake \n\n\n", + "expected_results": "" + }, + "4": { + "action": " Create the following files withing the myapp directory myapp.c and the Makefile. Write the following inside of each file: \n---------------------------------------- \nMakefile should contain \n\nall: myapp \n\nmyapp: myapp.o \n\t$(CC) $(LDFLAGS) $< -o $@ \n\nmyapp.o: myapp.c \n\t$(CC) $(CFLAGS) -c $< -o $@ \n\nclean: \n\trm -rf myapp.o myapp \n\n----------------------------- \nmyapp.c shold contain \n\n\n#include <stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n \n\treturn 0; \n} \n------------------------------------ \n\n", + "expected_results": "be sure that the indentations on the makefile are tabs not spaces. \n\n" + }, + "5": { + "action": " Create the following files within the myapp_cmake directory CMakeLists.txt and myapp.c. Write the following inside each file: \n\n------------------------------------ \nCMakeLists.txt should contain: \n\ncmake_minimum_required (VERSION 2.6) \nproject (myapp) \n# The version number. \nset (myapp_VERSION_MAJOR 1) \nset (myapp_VERSION_MINOR 0) \n\n# add the executable \nadd_executable (myapp myapp.c) \n\ninstall(TARGETS myapp \nRUNTIME DESTINATION bin) \n\n------------------------------------------ \nmyapp.c should contain: \n\n#include <stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n\n\treturn 0; \n} \n------------------------------------------------- \n\n", + "expected_results": "Be sure that the indentations on CMakeLists.txt is tabs not spaces." + }, + "6": { + "action": " source environment-setup-i586-poky-linux \n\n", + "expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n" + }, + "7": { + "action": " run command which devtool \n\n", + "expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n " + }, + "8": { + "action": "devtool add myapp <directory>(this is myapp dir) \n\n\n", + "expected_results": "The directory you should input is the myapp directory. This should automatically create the recipe myapp.bb under <crops-esdk-workdir-workspace>/recipes/myapp/myapp.bb" + }, + "9": { + "action": " devtool build myapp \n\n", + "expected_results": "This should compile an image" + }, + "10": { + "action": " devtool reset myapp ", + "expected_results": "This cleans sysroot of the myapp recipe, but it leaves the source tree intact. meaning it does not erase." + } + }, + "summary": "sdkext_eSDK_devtool_build_make" + } + }, + { + "test": { + "@alias": "crops-default.crops-default.sdkext_devtool_build_esdk_package", + "author": [ + { + "email": "francisco.j.pedraza.gonzalez@intel.com", + "name": "francisco.j.pedraza.gonzalez@intel.com" + } + ], + "execution": { + "1": { + "action": "IMPORTANT NOTE: The firsts 5 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n\n", + "expected_results": "" + }, + "2": { + "action": " Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n", + "expected_results": "" + }, + "3": { + "action": " Create the following tree of files <crops-esdk-workdir-workspace>/sdkext/files/myapp/ \n <crops-esdk-workdir-workspace>/sdkext/files/myapp_cmake \n\n", + "expected_results": "" + }, + "4": { + "action": " Create the following files withing the myapp directory myapp.c and the Makefile. Write the following inside of each file: \n---------------------------------------- \nMakefile should contain \n\nall: myapp \n\nmyapp: myapp.o \n\t$(CC) $(LDFLAGS) $< -o $@ \n\nmyapp.o: myapp.c \n\t$(CC) $(CFLAGS) -c $< -o $@ \n\nclean: \n\trm -rf myapp.o myapp \n\n----------------------------- \nmyapp.c shold contain \n\n#include <stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n \n\treturn 0; \n} \n------------------------------------ \n\n", + "expected_results": "be sure that the indentations on the makefile are tabs not spaces. \n\n" + }, + "5": { + "action": " Create the following files within the myapp_cmake directory CMakeLists.txt and myapp.c. Write the following inside each file: \n\n------------------------------------ \nCMakeLists.txt should contain: \n\ncmake_minimum_required (VERSION 2.6) \nproject (myapp) \n# The version number. \nset (myapp_VERSION_MAJOR 1) \nset (myapp_VERSION_MINOR 0) \n\n# add the executable \nadd_executable (myapp myapp.c) \n\ninstall(TARGETS myapp \nRUNTIME DESTINATION bin) \n\n------------------------------------------ \nmyapp.c should contain: \n\n#include<stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n\n\treturn 0; \n} \n------------------------------------------------- \n\n", + "expected_results": "Be sure that the indentations on CMakeLists.txt is tabs not spaces. \n\n" + }, + "6": { + "action": " source environment-setup-i586-poky-linux \n\n", + "expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n" + }, + "7": { + "action": " run command which devtool \n\n", + "expected_results": " this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n" + }, + "8": { + "action": " devtool add myapp <directory> (this is myapp dir) \n\n", + "expected_results": " The directory you should input is the myapp directory. This should automatically create the recipe myapp.bb under <crops-esdk-workdir-workspace>/recipes/myapp/myapp.bb \n\n" + }, + "9": { + "action": " devtool package myapp \n\n", + "expected_results": " you should expect a package creation of myapp and it should be under the /tmp/deploy/ \n\n" + }, + "10": { + "action": " devtool reset myapp ", + "expected_results": "This cleans sysroot of the myapp recipe, but it leaves the source tree intact. meaning it does not erase.\n</package_format>" + } + }, + "summary": "sdkext_devtool_build_esdk_package" + } + }, + { + "test": { + "@alias": "crops-default.crops-default.sdkext_devtool_build_cmake", + "author": [ + { + "email": "francisco.j.pedraza.gonzalez@intel.com", + "name": "francisco.j.pedraza.gonzalez@intel.com" + } + ], + "execution": { + "1": { + "action": "IMPORTANT NOTE: The firsts 5 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n\n", + "expected_results": "" + }, + "2": { + "action": " Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n", + "expected_results": "" + }, + "3": { + "action": " Create the following tree of files <crops-esdk-workdir-workspace>/sdkext/files/myapp \n <crops-esdk-workdir-workspace>/sdkext/files/myapp_cmake \n\n", + "expected_results": "" + }, + "4": { + "action": " Create the following files withing the myapp directory myapp.c and the Makefile. Write the following inside of each file: \n---------------------------------------- \nMakefile should contain \n\nall: myapp \n\nmyapp: myapp.o \n\t$(CC) $(LDFLAGS) $< -o $@ \n\nmyapp.o: myapp.c \n\t$(CC) $(CFLAGS) -c $< -o $@ \n\nclean: \n\trm -rf myapp.o myapp \n\n----------------------------- \nmyapp.c shold contain \n\n#include <stdio.h> \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n \n\treturn 0; \n} \n------------------------------------ \n\n", + "expected_results": "be sure that the indentations on the makefile are tabs not spaces. \n\n" + }, + "5": { + "action": " Create the following files within the myapp_cmake directory CMakeLists.txt and myapp.c. Write the following inside each file: \n\n------------------------------------ \nCMakeLists.txt should contain: \n\ncmake_minimum_required (VERSION 2.6) \nproject (myapp) \n# The version number. \nset (myapp_VERSION_MAJOR 1) \nset (myapp_VERSION_MINOR 0) \n\n# add the executable \nadd_executable (myapp myapp.c) \n\ninstall(TARGETS myapp \nRUNTIME DESTINATION bin) \n\n------------------------------------------ \nmyapp.c should contain: \n\n#include \n\nint \nmain(int argc, char *argv[]) \n{ \n\tprintf(\"Hello world\\n\"); \n\n\treturn 0; \n} \n------------------------------------------------- \n\n", + "expected_results": "Be sure that the indentations on CMakeLists.txt is tabs not spaces. \n\n" + }, + "6": { + "action": " source environment-setup-i586-poky-linux \n\n", + "expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n" + }, + "7": { + "action": " run command which devtool \n\n", + "expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n" + }, + "8": { + "action": " devtool add myapp <directory> (this is myapp_cmake dir) \n\n", + "expected_results": "The directory you should input is the myapp_cmake directory. This should automatically create the recipe myapp.bb under <crops-esdk-workdir-workspace>/recipes/myapp/myapp.bb \n\n" + }, + "9": { + "action": " devtool build myapp \n\n", + "expected_results": "This should compile an image \n\n" + }, + "10": { + "action": " devtool reset myapp ", + "expected_results": "This cleans sysroot of the myapp recipe, but it leaves the source tree intact. meaning it does not erase. " + } + }, + "summary": "sdkext_devtool_build_cmake" + } + }, + { + "test": { + "@alias": "crops-default.crops-default.sdkext_extend_autotools_recipe_creation", + "author": [ + { + "email": "francisco.j.pedraza.gonzalez@intel.com", + "name": "francisco.j.pedraza.gonzalez@intel.com" + } + ], + "execution": { + "1": { + "action": "IMPORTANT NOTE: The firsts 2 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n\n", + "expected_results": "" + }, + "2": { + "action": "Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n", + "expected_results": "" + }, + "3": { + "action": " source environment-setup-i586-poky-linux \n\n", + "expected_results": " This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n" + }, + "4": { + "action": "run command which devtool \n\n", + "expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n" + }, + "5": { + "action": "devtool sdk-install -s libxml2 \n\n", + "expected_results": "this should install libxml2 \n\n" + }, + "6": { + "action": "devtool add librdfa https://github.com/rdfa/librdfa \n\n", + "expected_results": "This should automatically create the recipe librdfa.bb under /recipes/librdfa/librdfa.bb \n\n" + }, + "7": { + "action": "devtool build librdfa \n\n", + "expected_results": "This should compile \n\n" + }, + "8": { + "action": "devtool reset librdfa ", + "expected_results": "This cleans sysroot of the librdfa recipe, but it leaves the source tree intact. meaning it does not erase." + } + }, + "summary": "sdkext_extend_autotools_recipe_creation" + } + }, + { + "test": { + "@alias": "crops-default.crops-default.sdkext_devtool_kernelmodule", + "author": [ + { + "email": "francisco.j.pedraza.gonzalez@intel.com", + "name": "francisco.j.pedraza.gonzalez@intel.com" + } + ], + "execution": { + "1": { + "action": "IMPORTANT NOTE: The firsts 2 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\n", + "expected_results": "" + }, + "2": { + "action": " Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n", + "expected_results": "" + }, + "3": { + "action": "source environment-setup-i586-poky-linux \n\n", + "expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n \n" + }, + "4": { + "action": "run command which devtool \n\n", + "expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n" + }, + "5": { + "action": "devtool add kernel-module-hello-world https://git.yoctoproject.org/git/kernel-module-hello-world \n\n", + "expected_results": "This should automatically create the recipe kernel-module-hello-world.bb under <crops-esdk-workdir-workspace>/recipes/kernel-module-hello-world/kernel-module-hello-world.bb " + }, + "6": { + "action": "devtool build kernel-module-hello-world \n\n", + "expected_results": "This should compile an image \n\n" + }, + "7": { + "action": "devtool reset kernel-module-hello-world ", + "expected_results": "This cleans sysroot of the kernel-module-hello-world recipe, but it leaves the source tree intact. meaning it does not erase." + } + }, + "summary": "sdkext_devtool_kernelmodule" + } + }, + { + "test": { + "@alias": "crops-default.crops-default.sdkext_recipes_for_nodejs", + "author": [ + { + "email": "francisco.j.pedraza.gonzalez@intel.com", + "name": "francisco.j.pedraza.gonzalez@intel.com" + } + ], + "execution": { + "1": { + "action": "IMPORTANT NOTE: The firsts 2 steps refer to configuration of the environment to run the rest of the steps. These only apply for CROPS-eSDK. \n\n\nlets say variable npm = npm://registry.npmjs.org;name=winston;version=2.2.0 \n\n", + "expected_results": "" + }, + "2": { + "action": "Initiate your Crops-esdk environment as it says in wiki https://github.com/crops/docker-win-mac-docs/wiki \n\n", + "expected_results": "" + }, + "3": { + "action": "source environment-setup-i586-poky-linux \n\n", + "expected_results": "This should output a message that says SDK environment now set up; additionally you may now run devtool to perform development tasks etc etc ... \n\n" + }, + "4": { + "action": "run command which devtool \n\n", + "expected_results": "this should output the directory of the devtool script and it should be within the sdk workdir you are working in. \n\n" + }, + "5": { + "action": " 4a) git clone git://git.openembedded.org/meta-openembedded in layers/build directory \n \n4b) Add meta-openembedded/meta-oe in bblayer.conf as mentioned below: ${SDKBASEMETAPATH}/layers/build/meta-openembedded/meta-oe \\ \n\n4c) devtool add \"npm://registry.npmjs.org;name=npm;version=2.2.0\" \n\n", + "expected_results": " This should automatically create the recipe npm.bb under /recipes/npm/npm.bb \n\n" + }, + "6": { + "action": "devtool build npm \n\n", + "expected_results": "This should compile an image \n\n" + }, + "7": { + "action": " devtool reset npm", + "expected_results": "This cleans sysroot of the npm recipe, but it leaves the source tree intact. meaning it does not erase." + } + }, + "summary": "sdkext_recipes_for_nodejs" + } + } +] diff --git a/meta/lib/oeqa/manual/eclipse-plugin.json b/meta/lib/oeqa/manual/eclipse-plugin.json new file mode 100644 index 0000000000..6c110d0656 --- /dev/null +++ b/meta/lib/oeqa/manual/eclipse-plugin.json @@ -0,0 +1,322 @@ +[ + { + "test": { + "@alias": "eclipse-plugin.eclipse-plugin.support_SSH_connection_to_Target", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "In Eclipse, swich to Remote System Explorer to create a connention baseed on SSH, input the remote target IP address as the Host name, make sure disable the proxy in Window->Preferences->General->Network Connection, set Direct as Active Provider field. ", + "expected_results": "the connection based on SSH could be set up." + }, + "2": { + "action": "Configure connection from Eclipse: Run->Run Configurations->C/C++ Remote Application\\ ->New Connection->General->SSH Only ", + "expected_results": "" + }, + "3": { + "action": "Then right click to connect, input the user ID and password. ", + "expected_results": "" + }, + "4": { + "action": "expand the connection, it will show the Sftp Files etc. \nNOTE. Might need to change dropbear to openssh and add the packagegroup-core-eclipse-debug recipe", + "expected_results": "" + } + }, + "summary": "support_SSH_connection_to_Target" + } + }, + { + "test": { + "@alias": "eclipse-plugin.eclipse-plugin.Launch_QEMU_from_Eclipse", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Set the Yocto ADT's toolchain root location, sysroot location and kernel, in the menu Window -> Preferences -> Yocto ADT. \n \n", + "expected_results": "" + }, + "2": { + "action": "wget https://downloads.yoctoproject.org/releases/yocto/yocto-$VERSION/machines/qemu/qemux86/ (ex:core-image-sato-sdk-qemux86-date-rootfs-tar-bz2) \nsource /opt/poky/version/environment-setup-i585-poky-linux \n\nExtract qemu with runqemu-extract-sdk /home/user/file(ex.core-image-sato-sdk-qemux86.bz2) \n/home/user/qemux86-sato-sdk \n\n", + "expected_results": " Qemu can be lauched normally." + }, + "3": { + "action": "(a)Point to the Toolchain: \n \nIf you are using a stand-alone pre-built toolchain, you should be pointing to the /opt/poky/{test-version} directory as Toolchain Root Location. This is the default location for toolchains installed by the ADT Installer or by hand. If ADT is installed in other location, use that location as Toolchain location.\nIf you are using a system-derived toolchain, the path you provide for the Toolchain Root Location field is the Yocto Project's build directory. \n \n E.g:/home/user/yocto/poky/build \n", + "expected_results": "" + }, + "4": { + "action": "(b)Specify the Sysroot Location: \nSysroot Location is the location where the root filesystem for the target hardware is created on the development system by the ADT Installer (SYSROOT in step 2 of the case ADT installer Installation). \n \n Local : e.g: /home/user/qemux86-sato-sdk \nUsing ADT : e.g :/home/user/test-yocto/qemux86 \n\n", + "expected_results": "" + }, + "5": { + "action": "(c)Select the Target Architecture: \n \nThe target architecture is the type of hardware you are going to use or emulate. Use the pull-down Target Architecture menu to make your selection. \n \n\n", + "expected_results": "" + }, + "6": { + "action": "(d) QEMU: \nSelect this option if you will be using the QEMU emulator. Specify the Kernel matching the QEMU architecture you are using. \n wget https://downloads.yoctoproject.org/releases/yocto/yocto-$VERSION/machines/qemu/qemux86/bzImage-qemux86.bin \n e.g: /home/$USER/yocto/adt-installer/download_image/bzImage-qemux86.bin \n\n", + "expected_results": "" + }, + "7": { + "action": "(e) select OK to save the settings. \n\n\n1: In the Eclipse toolbar, expose the Run -> External Tools menu. Your image should appear as a selectable menu item. \n2: Select your image in the navigation pane to launch the emulator in a new window. \n3: If needed, enter your host root password in the shell window at the prompt. This sets up a Tap 0 connection needed for running in user-space NFS mode. \n", + "expected_results": "" + } + }, + "summary": "Launch_QEMU_from_Eclipse" + } + }, + { + "test": { + "@alias": "eclipse-plugin.eclipse-plugin.Relocatable_SDK_-_C_-_Build_Hello_World_ANSI_C_Autotools_Project", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Launch a QEMU of target environment.(Reference to case \"ADT - Launch qemu by eclipse\") ", + "expected_results": "" + }, + "2": { + "action": "Select File -> New -> Project.", + "expected_results": "" + }, + "3": { + "action": "Double click C/C++.", + "expected_results": "" + }, + "4": { + "action": "Click C or C++ Project to create the project.", + "expected_results": "" + }, + "5": { + "action": "Expand Yocto ADT Project.", + "expected_results": "" + }, + "6": { + "action": "Select Hello World ANSI C Autotools Project.", + "expected_results": "" + }, + "7": { + "action": "Put a name in the Project name. Do not use hyphens as part of the name. \n \n", + "expected_results": "" + }, + "8": { + "action": "Click Next.", + "expected_results": "" + }, + "9": { + "action": "Add information in the Author and Copyright notice fields. \n1", + "expected_results": "" + }, + "10": { + "action": "Click Finish. \n1", + "expected_results": "" + }, + "11": { + "action": "If the \"open perspective\" prompt appears, click \"Yes\" so that you open the C/C++ perspective. \n1", + "expected_results": "" + }, + "12": { + "action": "In the Project Explorer window, right click the project -> Reconfigure project. \n1", + "expected_results": "" + }, + "13": { + "action": "In the Project Explorer window, right click the project -> Build project. \n1", + "expected_results": "Under the Project files, a new folder appears called Binaries. This indicates that the compilation have been successful and the project binary have been created. \n" + }, + "14": { + "action": "Right click it again and Run as -> Run Configurations. \n\t\t\tUnder Run Configurations expand \"C/C++ Remote Application\". A configuration for the current project should appear. Clicking it will display the configuration settings. \n\t\t\tin \"C/C++ Application\" field input Remote Absolute File path for C/C++ Application. e.g.: /home/root/myapplication \n\t\t\tIn \"Connection\" drop-down list make sure a TCF connection is set up for your target. If not, create a new one by clicking the New button. \n1", + "expected_results": "step 14 to step 16 -> Build succeed and the console outputs Hello world, you can also check the output on target." + }, + "15": { + "action": "After all settings are done, select the Run button on the bottom right corner \n\n1", + "expected_results": "" + }, + "16": { + "action": "Repeat the steps 14-15, but instead of using Run Configurations use Debug Configurations: \nRight click it again and Debug as -> Debug Configurations \nUnder Debug Configurations expand \"C/C++ Remote Application\". A configuration for the current project should appear. Clicking it will display the configuration settings. \nin \"C/C++ Application\" field input Remote Absolute File path for C/C++ Application.\ne.g.: /home/root/myapplication \nIn \"Connection\" drop-down list make sure a TCF connection is set up for your target. If not, create a new one by clicking the New button \n1", + "expected_results": "" + }, + "17": { + "action": "After all settings are done, select the Debug button on the bottom right corner", + "expected_results": "" + } + }, + "summary": "Relocatable_SDK_-_C_-_Build_Hello_World_ANSI_C_Autotools_Project" + } + }, + { + "test": { + "@alias": "eclipse-plugin.eclipse-plugin.Relocatable_SDK_-_C++_-_Build_Hello_World_C++_Autotools_project", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Launch a QEMU of target environment.(Reference to case \"ADT - Launch qemu by eclipse\") ", + "expected_results": "" + }, + "2": { + "action": "Select File -> New -> Project. ", + "expected_results": "" + }, + "3": { + "action": "Double click C/C++. ", + "expected_results": "" + }, + "4": { + "action": "Click C or C++ Project to create the project. ", + "expected_results": "" + }, + "5": { + "action": "Expand Yocto ADT Project. ", + "expected_results": "" + }, + "6": { + "action": "Select Hello World ANSI C++ Autotools Project. ", + "expected_results": "" + }, + "7": { + "action": "Put a name in the Project name. Do not use hyphens as part of the name. \n \n", + "expected_results": "" + }, + "8": { + "action": "Click Next.", + "expected_results": "" + }, + "9": { + "action": "Add information in the Author and Copyright notice fields.", + "expected_results": "" + }, + "10": { + "action": "Click Finish. \n1", + "expected_results": "" + }, + "11": { + "action": "If the \"open perspective\" prompt appears, click \"Yes\" so that you open the C/C++ perspective. \n1", + "expected_results": "" + }, + "12": { + "action": "In the Project Explorer window, right click the project -> Reconfigure project. \n1", + "expected_results": "" + }, + "13": { + "action": "In the Project Explorer window, right click the project -> Build project. \n\n1", + "expected_results": "under the Project files, a new folder appears called Binaries. This indicates that the compilation have been successful and the project binary have been created. \n" + }, + "14": { + "action": "Right click it again and Run as -> Run Configurations. \n\t\t\tUnder Run Configurations expand \"C/C++ Remote Application\". A configuration for the current project should appear. Clicking it will display the configuration settings. \n\t\t\tin \"C/C++ Application\" field input Remote Absolute File path for C/C++ Application. e.g.: /home/root/myapplication \n\t\t\tIn \"Connection\" drop-down list make sure a TCF connection is set up for your target. If not, create a new one by clicking the New button. \n1", + "expected_results": "step 14 to step 16 -> Build succeed and the console outputs Hello world, you can also check the output on target." + }, + "15": { + "action": "After all settings are done, select the Run button on the bottom right corner \n\n1", + "expected_results": "" + }, + "16": { + "action": "Repeat the steps 14-15, but instead of using Run Configurations use Debug Configurations: \n\t\tRight click it again and Debug as -> Debug Configurations \n\t\tUnder Debug Configurations expand \"C/C++ Remote Application\". A configuration for the current project should appear. Clicking it will display the configuration settings. \n\t\tin \"C/C++ Application\" field input Remote Absolute File path for C/C++ Application. \n\t\te.g.: /home/root/myapplication \n\t\tIn \"Connection\" drop-down list make sure a TCF connection is set up for your target. If not, create a new one by clicking the New button \n1", + "expected_results": "" + }, + "17": { + "action": "After all settings are done, select the Debug button on the bottom right corner", + "expected_results": "" + } + }, + "summary": "Relocatable_SDK_-_C++_-_Build_Hello_World_C++_Autotools_project" + } + }, + { + "test": { + "@alias": "eclipse-plugin.eclipse-plugin.Build_Eclipse_Plugin_from_source", + "author": [ + { + "email": "laurentiu.serban@intel.com", + "name": "laurentiu.serban@intel.com" + } + ], + "execution": { + "1": { + "action": "Clone eclipse-poky source. \n \n - git clone git://git.yoctoproject.org/eclipse-poky \n\n", + "expected_results": "Eclipse plugin is successfully installed \n\nDocumentation is there. For example if you have release yocto-2.0.1 you will found on https://downloads.yoctoproject.org/releases/yocto/yocto-2.0.1/eclipse-plugin/mars/ archive with documentation like org.yocto.doc-development-$date.zip \n \n" + }, + "2": { + "action": "Checkout correct tag. \n\n - git checkout <eclipse-version>/<yocto-version> \n\n", + "expected_results": "After plugin is build you must have 4 archive in foder scripts from eclipse-poky: \n - org.yocto.bc - mars-master-$date.zip \n - org.yocto.doc - mars-master-$date.zip --> documentation \n - org.yocto.sdk - mars-master-$date.zip \n - org.yocto.sdk - mars-master-$date.-archive.zip --> plugin " + }, + "3": { + "action": "Move to scripts/ folder. \n\n", + "expected_results": "" + }, + "4": { + "action": "Run ./setup.sh \n\n", + "expected_results": "" + }, + "5": { + "action": "When the script finishes, it prompts a command to issue to build the plugin. It should look similar to the following: \n\n$ ECLIPSE_HOME=/eclipse-poky/scripts/eclipse ./build.sh /&1 | tee -a build.log \n\nHere, the three arguments to the build script are tag name, branch for documentation and release name. \n\n", + "expected_results": "" + }, + "6": { + "action": "On an eclipse without the Yocto Plugin, select \"Install New Software\" from Help pull-down menu \n\n", + "expected_results": "" + }, + "7": { + "action": "Select Add and from the dialog choose Archive... Look for the *archive.zip file that was built previously with the build.sh script. Click OK. \n\n", + "expected_results": "" + }, + "8": { + "action": "Select all components and proceed with Installation of plugin. Restarting eclipse might be required.\n", + "expected_results": "" + } + }, + "summary": "Build_Eclipse_Plugin_from_source" + } + }, + { + "test": { + "@alias": "eclipse-plugin.eclipse-plugin.Eclipse_Poky_installation_and_setup", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Install SDK \n\ta)Download https://autobuilder.yocto.io/pub/releases//toolchain/x86_64/poky-glibc-x86_64-core-\timage-sato-i586-toolchain-.sh \n\tb)Run the SDK installer and accept the default installation directory ", + "expected_results": "" + }, + "2": { + "action": "Install \"Eclipse IDE for C/C++ Developers\" Oxygen release (4.7.0) \n\ta) Go to https://www.eclipse.org/downloads/packages/all, click \"Oxygen R\" \n\tb) Click to download the build for your OS \n\tc) Click \"Download\" button to download from a mirror \n\td) Run \"tar xf\" to extract the downloaded archive ", + "expected_result": "" + }, + "3": { + "action": "Install \"Eclipse IDE for C/C++ Developers\" Oxygen release (4.7.0) (Continue) \n\te) Run \"eclipse/eclipse\" to start Eclipse \n\tf) Optional step for host machine within Intel network: In Eclipse workbench window, go to \"Window\" menu -> \"Preferences...\". \n\tg) In \"Preferences\" dialog, go to \"General\" -> \"Network Connections\", set \"Active Provider\" to \"Manual\". In \"Proxy \tentries\" table, select HTTP and click \"Edit\" and enter host \"proxy-chain.intel.com\" port 911, click OK. Repeat for HTTPS with port 912 \nClick OK to close \"Preferences\" dialog. \n\th) Go to \"File\" menu -> \"Restart\" to restart Eclipse for proxy settings to take effect. ", + "expected_result": "" + }, + "4": { + "action": "Install Eclipse Poky plugins \n\ta) Download https://autobuilder.yocto.io/pub/releases/<yocto-version>/eclipse-plugin/<eclipse-version>/org.yocto.sdk-development-<date>-archive.zip \n\tb) In Eclipse workbench window, go to \"Help\" menu -> \"Install New Software...\" \n\tc) In \"Install\" dialog, click \"Add...\" button \n\td) In \"Add Repository\" dialog, enter \"Eclipse Poky\" for (repository) Name, click \"Archive...\" ", + "expected_results": "" + }, + "5": { + "action": "Install Eclipse Poky plugins (continue) \n\te) In \"Repository archive\" browse dialog, select the downloaded Eclipse Poky repository archive \n\tf) Back in \"Add Repository\" dialog, click \"OK\" \n\tg) Back in \"Install\" dialog, make sure \"Work with:\" is set to \"Eclipse Poky\" repository, tick \"Yocto Project \tDocumentation Plug-in\" and \"Yocto Project SDK Plug-in\", click \"Next >\" and verify plugins/features name/version, \tclick \"Next >\" and accept license agreement, click \"Finish\" \n\th) If \"Security Warning\" dialog appears, click \"OK\" to install unsigned content. \n\ti) In \"Software Updates\" dialog, click \"Yes\" to restart Eclipse to complete Eclipse Poky plugins installation. ", + "expected_results": "" + }, + "6": { + "action": "Setup Eclipse Poky to use SDK \n\ta) In Eclipse workbench window, go to \"Window\" menu -> \"Preferences\". \n\tb) In \"Preferences\" window, go to \"Yocto Project SDK\", in \"Cross Compiler Options\" frame, select \"Standalone pre-\tbuilt toolchain\". ", + "expected_results": "Eclipse Poky plugins installed and running successfully, e.g. observe that \"Yocto Project Tools\" menu is available on Eclipse workbench window." + } + }, + "summary": "Eclipse_Poky_installation_and_setup" + } + } +] diff --git a/meta/lib/oeqa/manual/kernel-dev.json b/meta/lib/oeqa/manual/kernel-dev.json new file mode 100644 index 0000000000..0dd99199dc --- /dev/null +++ b/meta/lib/oeqa/manual/kernel-dev.json @@ -0,0 +1,200 @@ +[ + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_defconfig", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_7 ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_7", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_7" + } + }, + "summary": "Kernel_dev_defconfig" + } + }, + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_defconfig+fragments", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_8 ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_8", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_8" + } + }, + "summary": "Kernel_dev_defconfig+fragments" + } + }, + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_Applying_patches", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results" + } + }, + "summary": "Kernel_dev_Applying_patches" + } + }, + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_linux-yocto-local-source", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_2 ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_2", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_2" + } + }, + "summary": "Kernel_dev_linux-yocto-local-source" + } + }, + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_linux-yocto-custom-local-source", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_3 ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_3", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_3" + } + }, + "summary": "Kernel_dev_linux-yocto-custom-local-source" + } + }, + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_recipe-space_meta", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_5 ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_5", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_5" + } + }, + "summary": "Kernel_dev_recipe-space_meta" + } + }, + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_External_source", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_6 ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_6", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_6" + } + }, + "summary": "Kernel_dev_External_source" + } + }, + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_building_external_modules(hello-mod)", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_10 ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup_10", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_10" + } + }, + "summary": "Kernel_dev_building_external_modules(hello-mod)" + } + }, + { + "test": { + "@alias": "kernel-dev.kernel-dev.Kernel_dev_local_parallel_meta", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Follow the Set Up procedure to complete the common and specific prerequisites for this test case. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Setup https://wikioproject.org/wiki/Kernel_Development_Test_Cases#Prerequisites_4 ", + "expected_results": "" + }, + "2": { + "action": "Execute the test case steps asdocumented on the \"Kernel Development Test Cases\" wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Steps_4", + "expected_results": "Review expected results on thethe \"Kernel Development Test Cases\"wiki. https://wiki.yoctoproject.org/wiki/Kernel_Development_Test_Cases#Expected_Results_4" + } + }, + "summary": "Kernel_dev_local_parallel_meta" + } + } +]
\ No newline at end of file diff --git a/meta/lib/oeqa/manual/oe-core.json b/meta/lib/oeqa/manual/oe-core.json new file mode 100644 index 0000000000..4ad524d89b --- /dev/null +++ b/meta/lib/oeqa/manual/oe-core.json @@ -0,0 +1,158 @@ +[ + { + "test": { + "@alias": "oe-core.bitbake.Test_bitbake_menuconfig", + "author": [ + { + "email": "jose.perez.carranza@intel.com", + "name": "jose.perez.carranza@intel.com" + } + ], + "execution": { + "1": { + "action": "clone poky \n \n", + "expected_results": "" + }, + "2": { + "action": "cd poky \n\n", + "expected_results": "" + }, + "3": { + "action": "source oe-init-build-env && cd build \n\n", + "expected_results": "" + }, + "4": { + "action": "set below in local.conf \n\n \tMACHINE = \"qemux86\" \n\n", + "expected_results": "" + }, + "5": { + "action": "bitbake linux-yocto -c kernel_configme -f \n\n", + "expected_results": "" + }, + "6": { + "action": "bitbake linux-yocto -c menuconfig \n\n", + "expected_results": "" + }, + "7": { + "action": "Once menuconfig launches, use the interface to navigate through the selections and \n enable option \"64-bit kernel\" \n\n", + "expected_results": "" + }, + "8": { + "action": "Save changes and set name of the file as \"test.config\" ", + "expected_results": "Open file: \n \npoky/build//tmp/work/qemux86-poky-linux/linux-yocto/4.X.X+*/linux-qemux86-standard-build/test.config \n \n \n\nand verify that changes are present in the file as follows: \n \nCONFIG_64BIT=y \n \nCONFIG_X86_64=y" + } + }, + "summary": "Test_bitbake_menuconfig" + } + }, + { + "test": { + "@alias": "oe-core.bitbake.test_bitbake_devshell", + "author": [ + { + "email": "jose.perez.carranza@intel.com", + "name": "jose.perez.carranza@intel.com" + } + ], + "execution": { + "1": { + "action": "clone poky ", + "expected_results": "" + }, + "2": { + "action": "cd poky ", + "expected_results": "" + }, + "3": { + "action": "source oe-init-build-env && cd build ", + "expected_results": "" + }, + "4": { + "action": "bitbake matchbox-desktop ", + "expected_results": "Package was build correctly " + }, + "5": { + "action": "bitbake matchbox-desktop -c devshell ", + "expected_results": "A terminal with a shell prompt within the OpenEmbedded build environment is opened " + }, + "6": { + "action": "Verify that \"matchbox-desktop\" binary file is not created under\"src\" directory ", + "expected_results": "" + }, + "7": { + "action": "Run command:./configure ${CONFIGUREOPTS} && make ", + "expected_results": "Verify that \"matchbox-desktop\" binary file was created successfully under \"src/\" directory " + }, + "8": { + "action": "Exit fromthe devshell terminal,exit ", + "expected_results": "Terminal back to the build directory" + } + }, + "summary": "test_bitbake_devshell" + } + }, + { + "test": { + "@alias": "oe-core.bitbake.test_dependency_explorer_is_launched", + "author": [ + { + "email": "jose.perez.carranza@intel.com", + "name": "jose.perez.carranza@intel.com" + } + ], + "execution": { + "1": { + "action": "clone poky ", + "expected_results": "" + }, + "2": { + "action": "cd poky ", + "expected_results": "" + }, + "3": { + "action": "source oe-init-build-env ", + "expected_results": "" + }, + "4": { + "action": "bitbake -u taskexp -g core-image-full-cmdline \n\nNOTE: To execute the last command of this test, it's necessary that the machine is executing an X11 server, or if that's not the case (for example, if running the test on a headless server), it is required to enable ssh X11 forwarding on both, the server and the client, and have the X11 server running on the client. \n\nThe instructions to enable X11 forwarding vary between distributions. But for example, these are the steps to enable it between a server running openSUSE Leap 42.1 and a client with Fedora 24: \nA. On the server, make sure /home//.ssh/config contains the line: \n ForwardX11 yes \nB. On the server, make sure xauth is installed by running: \n which xauth \nC. On the client, connect to the server, enabling X11 forwarding, for example by using: \n ssh -X user@server \nNOTE 2: depexp was renamed to taskexp on 2.3 M4", + "expected_results": "Verify that a \"dependency explorer\" is opened and file \n dependencies are listed " + } + }, + "summary": "test_dependency_explorer_is_launched" + } + }, + { + "test": { + "@alias": "oe-core.bitbake.test_bitbake_sane_error_for_invalid_layer", + "author": [ + { + "email": "jose.perez.carranza@intel.com", + "name": "jose.perez.carranza@intel.com" + } + ], + "execution": { + "1": { + "action": "clone poky \n", + "expected_results": "" + }, + "2": { + "action": "cd poky \n \n", + "expected_results": "" + }, + "3": { + "action": "source oe-init-build-env && cd build \n \n", + "expected_results": "" + }, + "4": { + "action": "Add a invalid layer to conf/bblayers.conf \"<poky dir>/my-invalid-layer\" \n\t\n", + "expected_results": "" + }, + "5": { + "action": "bitbake core-image-minimal", + "expected_results": "Below error should be displayed:\n\"ERROR: Layer directory does not exist! Please check BBLAYERS in <poky dir>/<build dir>/conf/bblayers.conf\"" + } + }, + "summary": "test_bitbake_sane_error_for_invalid_layer" + } + } +] diff --git a/meta/lib/oeqa/manual/sdk.json b/meta/lib/oeqa/manual/sdk.json new file mode 100644 index 0000000000..21d892d26d --- /dev/null +++ b/meta/lib/oeqa/manual/sdk.json @@ -0,0 +1,32 @@ +[ + { + "test": { + "@alias": "sdk.sdk_runqemu.test_install_cross_toolchain_can_run_multiple_qemu_for_x86", + "author": [ + { + "email": "ee.peng.yeoh@intel.com", + "name": "ee.peng.yeoh@intel.com" + } + ], + "execution": { + "1": { + "action": "Prepare kernel, rootfs tar.bz2 image, and qemu configuration \n \ta. Download kernel, rootfs tar.bz2 image and qemu configuration from public autobuilder webpage \n \tb. Goto https://autobuilder.yocto.io/pub/releases/<target_release>/machines/qemu/qemux86/ \n \tc. Download \n \t \ti. rootfs tar.bz2: core-image-sato-sdk-qemux86.tar.bz2 \n \t\tii. kernel: bzImage-qemux86.bin \n \t\tiii. qemu configuration: core-image-sato-sdk-qemux86.qemuboot.conf ", + "expected_results": "Download completes successfully." + }, + "2": { + "action": "Download & install toolchain tarball matching your host from public autobuilder \n \ta. Goto https://autobuilder.yocto.io/pub/releases/<target_release>/toolchain/x86_64/ \n \tb. Download poky-glibc-x86_64-core-image-sato-<type-arch>-toolchain-<release-version>.sh \n \tc. Run command: poky-glibc-x86_64-core-image-sato-<type-arch>-toolchain-<release-version>.sh \n \td. After installation toolchain Run source command : source /toolchain-installed-path/environment-setup-<architecture name>-poky-linux", + "expected_results": "Toolchain gets installed successfully." + }, + "3": { + "action": "Extract rootfs twice into two images \n \ta. Run 2 commands below: \n runqemu-extract-sdk core-image-sato-sdk-qemux86.tar.bz2 qemux86_rootfs_image1 \n runqemu-extract-sdk core-image-sato-sdk-qemux86.tar.bz2 qemux86_rootfs_image2", + "expected_results": "Both images build successfully." + }, + "4": { + "action": " From the 2 terminals, start qemu to boot up both two images \n \ta. Run 2 commands below: \n runqemu <kernel-name> core-image-sato-sdk-qemux86.qemuboot.conf qemux86_rootfs_image1 \n runqemu <kernel-name> core-image-sato-sdk-qemux86.qemuboot.conf qemux86_rootfs_image2 ", + "expected_results": "Expect both qemu to boot up successfully." + } + }, + "summary": "test_install_cross_toolchain_can_run_multiple_qemu_for:x86" + } + } +]
\ No newline at end of file diff --git a/meta/lib/oeqa/manual/toaster-managed-mode.json b/meta/lib/oeqa/manual/toaster-managed-mode.json new file mode 100644 index 0000000000..1a71985c3c --- /dev/null +++ b/meta/lib/oeqa/manual/toaster-managed-mode.json @@ -0,0 +1,2572 @@ +[ + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.All_layers:_default_view", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table.", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"View compatible layers\" link situated on the right-hand side, mid-page, under the \"Project configuration\" menu, in the \"Layers\" table.", + "expected_results": "" + }, + "3": { + "action": "Check that the table is populated with the default layers (eg. meta-yocto-bsp, meta-yocto)", + "expected_results": "" + }, + "4": { + "action": "Check that by default the following columns are shown: Layer, Summary, Revision, Dependencies and Add/Delete", + "expected_results": "" + }, + "5": { + "action": "Check that the \"Revision\" entries match the release entry from the main project page, in the project details section.", + "expected_results": "" + }, + "6": { + "action": "Check that only one instance of the core layers (openembedded-core, meta-yocto and meta-yocto-bsp) shows in this table, and that instance has a branch that matches the selected project release from the main project page.", + "expected_results": "" + }, + "7": { + "action": "Check that in the \"Dependencies\" column some of the layers should have a square box with a number in it. When clicking on it, a small popup should appear containing a list of other layers required for this layer to work. Every layer listed here should also be a link to the layer's detail page. \n \n", + "expected_results": "" + }, + "8": { + "action": "From the \"Edit columns\" menu, activate the \"Git repository URL\" and the \"Subdirectory\" columns. In \"Git repository URL\": all the entries should have a link to the external site where the layer was downloaded from. Similarly, in \"Subdirectory\" links should exist, if a subdirectory entry is present.", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "All_layers:_default_view" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.All_layers:_Add/delete_layers", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n\n", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"View compatible layers\" link situated on the right-hand side, mid-page, under the \"Project configuration\" menus, in the \"Layers\" table. \n\n\n", + "expected_results": "" + }, + "3": { + "action": "Check that the Add/delete column is enabled. \n\n", + "expected_results": "" + }, + "4": { + "action": "Add a new layer \nPick a layer that hasn't been added to the project. \n \nClick on the \"Add layer\" button present in the \"Add/delete\" column. \nIf the layer has unsatisfied dependencies a dialog will appear listing the dependencies (in alphabetical order), each of them with a checkbox so that you can select / deselect them. All checkboxes are checked by default. If you click the \"Cancel\" button the dialog closes. If you click the \"Add layers\" button, the layers are added to the project. \n\nMake sure to uncheck at least 1 of the dependencies so you can check that only the checked dependencies are added, and not the unchecked one(s). ", + "expected_results": "" + }, + "5": { + "action": "Check that the \"Add layer\" button fades out and is replaced temporarily by a message like \"1 layer added\" and then it is replaced by the \"Delete layer\" button. \nCheck that a confirmation message is displayed at the top of the page similar to \"You have added 1 layer to project_name_here: meta-yocto-bsp\". \n\n", + "expected_results": "" + }, + "6": { + "action": "Delete an existing layer \nPick a layer that's already been added to the project. \nClick on the \"Delete layer\" button present in the \"Add/delete\" column. \nCheck that once the button is pressed, it fades out and is replaced temporarily by the message \"1 layer deleted\" and then it is replaced by the \"Add layer\" button. \nCheck that a confirmation is displayed at the top of the page similar to \"You have deleted 1 layer from project_name_here: meta-yocto-bsp\". ", + "expected_results": "All actions should complete successfully." + } + }, + "summary": "All_layers:_Add/delete_layers" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.All_targets:_Default_view", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": " If no images exist in the project, build an image by inserting \"core-image-minimal\" in the \"Recipes\" field and press the \"Build\" button. Wait for the image to finish building. \n\n", + "expected_results": "" + }, + "3": { + "action": "On the project page click on the \"Image Recipes\" link situated in the left-handed side of the page, under the \"Project configuration\" menus, in the \"COMPATIBLE METADATA\" table. \n\n", + "expected_results": "" + }, + "4": { + "action": "Check that \"Compatible image recipes\" table is populated. \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that the following columns are shown by default: \n\t\tImage recipe \n\t\tDescription \n \n\t\tLayer \n\t\tBuild \n\t\t Version ", + "expected_results": "" + } + }, + "summary": "All_targets:_Default_view" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Configuration_variables:_default_view", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n\n", + "expected_results": "" + }, + "2": { + "action": "In the main project page, click on \"BitBake variables\" in the left-hand side of the page, under the \"CONFIGURATION\" menu. \n\n", + "expected_results": "" + }, + "3": { + "action": "Check that default values are as follows: \n\tDISTRO - poky \n\tIMAGE_FSTYPES - ext3 jffs2 tar.bz2 \n\tIMAGE_INSTALL:append - \"Not set\" \n\tPACKAGE_CLASSES - package_rpm \n SSTATE_DIR - /homeDirectory/poky/sstate-cache \n\n", + "expected_results": "" + }, + "4": { + "action": "Check that under the \"Add variable\" section, the \"Variable\" field has the default text \"Type variable name\" present, the \"Value\" field has the default text \"Type variable value\" present and that the \"Add variable\" button is inactive. \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that under the \"Add variable\" section, there is text present that describes the variables that Toaster cannot modify. ", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Configuration_variables:_default_view" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Configuration_variables:_Test_UI_elements", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "In the main project page, click on \"BitBake variables\" in the left-hand side of the page, under the \"CONFIGURATION\" menu. \n\n", + "expected_results": "" + }, + "3": { + "action": "DISTRO: \n\t- check that the \"change\" icon is present (represented by a pen icon) \n\t- click on the \"change\" icon and check that the variable becomes an editable text field, populated with the current value of the variable \n\t- check that, if you delete the content of the text field, the save button is disabled \n\t- enter a distro name containing spaces (for example, \"poky tiny\") - check that an error message is shown explaining that the value entered cannot contain spaces \n\n", + "expected_results": "" + }, + "4": { + "action": "IMAGE_FSTYPES: \n\t- check that the \"change\" icon is present (represented by a pen icon) \n\t- click on the \"change\" icon and check that the variable becomes editable like so: the main input control is a set of checkboxes. There is a checkbox for each supported image type. The checkboxes are listed in ascending alphabetical order, broken down in 2 groups: \n\t\t", + "expected_results": "" + }, + "5": { + "action": "The selected types are checked and listed at the top \n\t\t", + "expected_results": "" + }, + "6": { + "action": "The other types are not checked and listed afterwards \n\t- check that all this is inside a scrollable div, and a text field is present above that filters out the content of the div as you type. \n\t- check that if there are no image types matching your typed string, a message is shown notifying you of this: \"No image types found\" \n\t- unselect all checkboxes and check that the save button is disabled and a message is shown: \"You must select at least one image type\" \n\t- select different checkboxes and hit save then make sure that the \tsaved value is consistent with the selected checkboxes \n\n", + "expected_results": "" + }, + "7": { + "action": "IMAGE_INSTALL:append: \n\t- check that the \"change\" icon is present (represented by a pen icon) \n\t- click on the \"change\" icon and check that the variable becomes a text field, populated with the current value of the variable. \n\n\t- check that the save button is disabled when the text field is empty \n\t- insert test in the text field (for example \"package1\") and hit save; be aware that there is no input validation for this variable \n\t- check that a new \"delete\" icon(a trashcan) has appeared next to the pen icon \n\t- check that clicking on the trashcan icon resets the value to \"Not set\" and makes the trashcan icon dissapear \n\n", + "expected_results": "" + }, + "8": { + "action": "PACKAGE_CLASSES: \n\t- check that the \"change\" icon is present (represented by a pen icon) \n\t- click on the \"change\" icon and check that the variable becomes editable with the following components: \n\t\t", + "expected_results": "" + }, + "9": { + "action": "A dropdown menu with values 'package_dev', 'package_ipk' and 'package_rpm' in this order. The value selected when you enter the editable state matches the first value of the variable (e.g. if the value is set to 'package_dev package_ipk' the value selected is 'package_dev'). \n \n\t\t", + "expected_results": "" + }, + "10": { + "action": "Two checkboxes, showing the 2 unselected values in the dropdown menu. \n\n\t- verify that the checkboxes are checked or unchecked to reflect the variable value (e.g. if the value is set to 'package_dev package_ipk', the 'package_ipk' checkbox is checked, and the 'package_rpm' checkbox is unchecked). \n\n\tBoth checkboxes can be unchecked. The value of the checkboxes changes dynamically as I change the selected value in the dropdown menu. This means that any changes to the dropdown menu should uncheck the checkboxes. \n\n\t- click on save and check that the value selected in the dropdown menu is the first value in the variable, followed by any checked checkboxes. \n\n\n", + "expected_results": "" + }, + "11": { + "action": "Adding variables: \n\t- check that the \"add variable\" form has 2 text fields: one for the variable name and a second one for the variable value, plus an \"add\" button that is disabled until both text fields have some input in them. \n \n\t- check variable name validation: variable names cannot have spaces, and can only include letters, numbers, underscores and dashes; variable names entered cannot match the name of a variable already on the list; variable names cannot match the blacklisted variables mentioned in the text on the right-hand side of the page \n\n\t - check that an error message is shown indicating validation has failed and why once you try to put in the value or click on the \"Add variable\" button ", + "expected_results": "All mentioned elements should be present and functional." + }, + "12": { + "action": "insert a valid combination and click on \"Add variable\"; check that a new variable/value pair is added at the bottom of the variable list and that the text fields in the \"add variable\" form are cleared and the \"add\" button is disabled \n\t- check that the added variable has a \"change\" icon present next to the variable value, and also that a \"delete\" icon is present next to the variable name \n\t- check that clicking the \"change\" icon makes the variable editable in a text field containing the value of the variable \n\t- check that, if you delete the content of the text field, the save button is\tdisabled\n\t- check that clicking on the \"delete\" button causes both the variable name and the variable value to be removed from the variables list", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Configuration_variables:_Test_UI_elements" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_Default_view", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"Builds\" , next to the \"Configuration\" Button. \n\n", + "expected_results": "" + }, + "3": { + "action": "Check that the page heading includes a counter with the number of builds run for the project(eg. \"Project builds (4)\"). \n\n", + "expected_results": "" + }, + "4": { + "action": "Check that the following table heads are visible by default: outcome, completed on, failed tasks, errors, warnings, image files. \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that by default the table is sorted by \"Completed on\" in descending order", + "expected_results": "All mentioned elements should be present." + } + }, + "summary": "Project_builds:_Default_view" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_Sorting_the_project_builds_table", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"View all project builds\" link situated below the top-most \"Build\" button and text field, next to the \"View all targets\" link \n\n\n", + "expected_results": "" + }, + "3": { + "action": "Verify that, by default, the table is sorted by \"Completed on\" in descending order. \n\n", + "expected_results": "" + }, + "4": { + "action": "Activate all columns from the \"Edit columns\" table. \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that the following columns are sortable, both in ascending and descending order: outcome, target, machine, started on, completed on, warning, project \n\n", + "expected_results": "" + }, + "6": { + "action": "Verify that hiding a column that is currently being used as the sorting criteria causes the sorting to reset to the default - i.e \"Completed on\" in descending order.", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Project_builds:_Sorting_the_project_builds_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_customize_the_columns_of_the_table", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"View all project builds\" link situated below the top-most \"Build\" button and text field, next to the \"View all targets\" link \n\n", + "expected_results": "" + }, + "3": { + "action": "Click on the \"Edit column\" menu and check that the selected columns match the columns currently being shown. \n\n", + "expected_results": "" + }, + "4": { + "action": "Check that the following columns cannot be removed from the shown columns: completed on, outcome, recipe \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that unchecked items changed to checked immediately appear in the table and that checked items changed to unchecked immediately disappear from the table.", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Project_builds:_customize_the_columns_of_the_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_filter_the_contents_of_the_table", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"View all project builds\" link situated below the top-most \"Build\" button and text field, next to the \"View all targets\" link. \n\n", + "expected_results": "" + }, + "3": { + "action": "Make sure the following columns have filters: outcome, started on, completed on, failed tasks. \n\n", + "expected_results": "" + }, + "4": { + "action": "Filters are mutually exclusive. Click a filter button of a one column and a filter dialogue occurs. Select a filter item. The filter result would be showed. Then select another filter item of another column and the previously applied filter is overridden by the newly selected filter when a filter from a different column is applied to the table. This filter will override the current filter.\" \n\n", + "expected_results": "" + }, + "5": { + "action": "Filters are overridden by search. Run a search query and you can see previous filter results are overridden by the results of the search query.", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Project_builds:_filter_the_contents_of_the_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Project_builds:_search_the_contents_of_the_table", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"View all project builds\" link situated below the top-most \"Build\" button and text field, next to the \"View all targets\" link. \n\n", + "expected_results": "" + }, + "3": { + "action": "When no search query has been entered, we have placeholder text saying: \"Search builds\". The placeholder text disappears when the first character is typed. \n\n", + "expected_results": "" + }, + "4": { + "action": "When a search query has been submitted and results returned: \n- We keep the search string in the text input field. \n- We provide a \"Clear search\" icon (icon-remove-sign). Click it to clear the search and display all packages. \n- We change the page heading to indicate the number of results returned by the search query. \n\n", + "expected_results": "" + }, + "5": { + "action": "If your search query returns no results, the page heading changes to \"No packages found\", and we show you an alert with a search form and an option to show all packages. \n\n", + "expected_results": "" + }, + "6": { + "action": "Searching does not change the state of the table: the same columns remain hidden and the same sorting applied. ", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Project_builds:_search_the_contents_of_the_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Layer_details_page:_Default_view", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"View compatible layers\" link situated in the \"Project configuration\" portion of the page, under \"Layers\" table. \n\n", + "expected_results": "" + }, + "3": { + "action": "Click on a layer (for example \"meta-aarch64\"). Notice that the page is divided into 2 columns: the left one is broken down into tabs; the right one provides information about the layer. \n\n", + "expected_results": "" + }, + "4": { + "action": "Check that breadcrumbs exist at the top of the page. Check that they work by clicking on them, then hitting back to return to the layer detail page. \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that the page heading includes the layer branch name - it should look something like meta-aarch64(dizzy) if the dizzy branch was selected. The branch name should also be present in the breadcrumbs. \n\n", + "expected_results": "" + }, + "6": { + "action": "The \"About\" information: \nit shows summary, description in this order, if not empty. If an information item is empty (like the Summary in the example shown in this page), it does not display. \n \n\n", + "expected_results": "" + }, + "7": { + "action": "The tabs: \nCheck that there are 3 tabs: \"layer details\", \"recipes\", \"machines\" showing up in this order. \n\n", + "expected_results": "" + }, + "8": { + "action": "\"Layer details\" tab: \nCheck that the tab shows: \n- A button to add / remove the layer to / from the project. In this tab, the button labels are\"Add the $layer_name layer to your project\" \"Delete the $layer_name layer from your project\" \n- Some details about the layer: repository URL, repository subdirectory, revision (the branch) and the list of layer dependencies. If any of the above details is blank (most likely, the subdirectory) it does not display.The icons next to the repository and subdirectory information are links to their web instances. Those links should open in a new window. \n\n", + "expected_results": "" + }, + "9": { + "action": "The \"Recipes\" tab: \nCheck that it shows: \n\t", + "expected_results": "" + }, + "10": { + "action": "A counter in the tab label showing the total number of targets provided by the layer \n\t", + "expected_results": "" + }, + "11": { + "action": "A button to add / remove the layer to / from the project. In this tab, the button labels are \"Add the $layer_name layer to your project to enable these targets\"/\"Delete the $layer_name layer from your project\" \n\t", + "expected_results": "" + }, + "12": { + "action": "A recipes table with the following columns: \n \n- Recipe \n- Description: the value of the DESCRIPTION variable. If not set, then the value of the SUMMARY variable. \n- Build recipe, which shows a \"build recipe\" button. The \"build recipe\" button is disabled when the layer is not added to the project. \n\nThe recipes table is sorted by \"Recipe\" in ascending alphabetical order. \n\n1", + "expected_results": "" + }, + "13": { + "action": "The \"Machines\" tab: \n\t", + "expected_results": "" + }, + "14": { + "action": "A counter in the tab label showing the total number of machines provided by the layer \n\t", + "expected_results": "" + }, + "15": { + "action": "A button to add/remove the layer to/from the project. In this tab, the button labels are \"Add the $layer_name layer to your project to enable these machines\"/\"Delete the $layer_name layer from your project\" \n\t", + "expected_results": "" + }, + "16": { + "action": "A machines table with the following columns: \n \n- Machine. \n \n- Description: The value of the DESCRIPTION variable in the .conf file \n- Select machine, which shows a \"select\" button. The \"select\" button is disabled when the layer is not added to the project. \nThe machines table is sorted by \"Machine\" in ascending alphabetical order. \n", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Layer_details_page:_Default_view" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Layer_details_page:_UI_functionality", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"View compatible layers\" link situated in the \"Project configuration\" portion of the page, under \"Layers\" \n\n", + "expected_results": "" + }, + "3": { + "action": "Click on a layer (for example \"meta-aarch64\"). \n\n", + "expected_results": "" + }, + "4": { + "action": "Adding/removing a layer: \nClick on \"Add the $layer_name_here layer to your project\" and verify that the \"Add layer\" button turns into a red button with the label \"Delete the $layer_name_here layer from your project\" and that at the top of the page, below the header, you see a message \"You have added 1 layer to $project_name_here: $layer_name_here\". This message can be dismissed by clicking on the \"X\" at the top right side of the message. ", + "expected_results": "" + }, + "5": { + "action": "Click on the red \"Delete the $layer_name_here from your project\" button and verify that the \"Delete layer\" button turns back into a grey button with the label \"Add the $layer_name_here to your project\" and that at the top of the page, below the header, you see a message \"You have deleted 1 layer to $project_name_here: $layer_name_here\". This message can be dismissed by clicking on the \"X\" at the top right side of the message. \n\n", + "expected_results": "" + }, + "6": { + "action": "Dependencies window: \n For a layer that has dependencies( for example \"meta-ettus\"), once you click the \"Add layer\" button, verify that you get a message window that presents the dependencies for this layer with the message \"$layer_name_here depends on some layers that are not added to your project. Select the ones you want to add:\", a list with a checkbox for each one and 2 options: \"Add layers\" or \"Cancel\". \nClicking on \"Add layers\" adds all the dependencies and the current layer. Clicking on \"Cancel\" takes you back to the layer detail page without adding any of the layers. \n\n", + "expected_results": "" + }, + "7": { + "action": "\"Recipes\" table \nCheck that if the layer hasn't been added to the project, the \"Build recipe\" button(s) are disabled. After the project is added, check that the \"Build recipe\" button(s) become active and clicking on a button sends you to the main project page and starts a build. \n\n", + "expected_results": "" + }, + "8": { + "action": "\"Machines table\" \nCheck that if the layer hasn't been added to the project, the \"Select machine\" button(s) are disabled. After the project is added, check that the \"Build machine\" button(s) become active and clicking on a button sends you to the main project page and modifies the project machine to the one selected. ", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Layer_details_page:_UI_functionality" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Importing_new_layers", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"Import layer\" link situated in the \"Project configuration\" portion of the page, under \"Layers\" table. \n\n", + "expected_results": "" + }, + "3": { + "action": "Check that the import layer form is shown, with the following elements as text fields to be filled out: \nLayer name (example: meta-imported) \nGit repository URL (example: git://github.com/shr-distribution/meta-smartphone.git) \nRepository subdirectory (optional) (example: meta-acer) \nRevision (example: master) \n\nIn addition, a separate portion of the form will be the \"Layer dependencies\" portion, where you can add dependency layers for the layer you are importing. This portion will contain a list of dependencies already added, with a trashcan icon next to them that will delete them when pressed and a text field with a \"add layer\" button next to it for adding dependencies. (for example: meta-android, meta-oe) \n\n", + "expected_results": "" + }, + "4": { + "action": "At the bottom of the form, check that a button exists with the label \"Import and add to project\". Check that this button is inactive until the required fields are filled out. \nCheck that clicking on the \"Import button\" takes you back to the main project page and that the imported layer, along with any dependencies, were added in the project's layers. ", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Importing_new_layers" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Layer_details_page:_UI_functionality_for_imported_layers", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Click on the \"View compatible layers\" link situated in the \"Project configuration\" portion of the page, under \"Layers\" table. \n\n", + "expected_results": "" + }, + "3": { + "action": "Select an imported layer (see in TC 1112 how to import a layer). \n\n", + "expected_results": "" + }, + "4": { + "action": "Page heading \nCheck that the page heading includes the branch, tag or commit as entered when importing the layer.\nIf it's a commit, Check that only the first 10 characters are shown followed by an ellipsis character. The full commit shows on hover.The branch, tag or commit information also shows in the breadcrumb. \n\n", + "expected_results": "" + }, + "5": { + "action": "The \"About\" information \nIt shows: \n- Summary \n- Description \nin this order. Those two items always show, independently of them being blank or not, since they can be edited by users. \n\nWhen an information item is empty, it shows as \"not set\" with a \"change\" icon. Click on the icon to add a value. \n\nFor \"Summary\" and \"Description\" clicking the \"change\" icon shows the selected information item in its editable state. It consists of a text area, set to 2 rows for the \"Summary\" and to 6 rows for the \"Description\", plus 'save' and 'cancel' buttons. \nThe 'save' buttons only activate when there is at least one character in the text area. \n\n", + "expected_results": "" + }, + "6": { + "action": "The tabs \nCheck that the tabs shown are: \n- \"Layer details\" \n- \"Recipes\" \n- \"Machines\" \nThe tabs should show in the order in which they are listed above. \n\n\"Layer details\" tab: \nIn not-editable pages, the tab shows: \n- A button to add / remove the layer to / from the project. In this tab, the button labels are: \n\t- \"Add the $layer_name layer to your project\" \n\t- \"Delete the $layer_name layer from your project\" \n\n- Some details about the layer: repository URL, repository subdirectory, revision (branch / tag / commit) and the list of layer dependencies. This is the information required from users when importing a layer. The subdirectory and the layer dependencies can be blank.", + "expected_results": "" + }, + "7": { + "action": "If blank, they show as \"not set\". \n\nEditing the \"Repository URL\" \nThe \"Git repository URL\" cannot be blank. Therefore, we show only a \"change\" icon next to it. When you click the icon, the text input field is set to the current value. If you delete the value from the input field, we disable the \"save\" button. We enable it again when you type something in the field. \n\nEditing the \"Repository subdirectory\" \nThe \"Repository subdirectory\" can be blank. Therefore, we show both \"change\" and \"delete\" icons. When you click the \"delete\" icon, we \nshow the label \"Not set\".", + "expected_results": "" + }, + "8": { + "action": "\nWhen you click the \"change\" icon, the text input field is set \nto the current value. \nIf you delete the value from the input field, we disable the \"save\" button. We enable it again when you type something in the field. \n \n\nEditing the \"Revision\" \nThe \"Revision\" cannot be blank. Therefore, we show only a \"change\" icon next to it. When you click the icon, the text input field is set to the current value. If you delete the value from the input field, we disable the \"save\" button. We enable it again when you type something in the field. \n\nThe \"Recipes\" tab \nIt shows: \n1: A counter in the tab label showing the total number of targets provided by the layer \n2: A button to add/remove the layer to/from the project. ", + "expected_results": "" + }, + "9": { + "action": "In this tab, the button labels are \n \n\"Add the $layer_name layer to your project to enable \nthese targets\" \n\"Delete the $layer_name layer from your project\" \n\n3: A \"Recipes\" table with the following columns: \n \n- Recipe \n- Description: the value of the DESCRIPTION variable. If not set, then the value of the SUMMARY variable. \n- Build recipe, which shows a \"build recipe\" button. The \"build recipe\" button is disabled when the layer is not added to the project. \nThe recipes table is sorted by \"Recipe\" in ascending alphabetical order. \n\nThe \"Machines\" tab: \nIt shows: \n1: A counter in the tab label showing the total number of machines provided by the layer \n2: A button to add/remove the layer to/from the project.", + "expected_results": "" + }, + "10": { + "action": "In this tab, the button labels are \n \n\t- \"Add the $layer_name layer to your project to enable these machines\" \n\t- \"Delete the $layer_name layer from your project\" \n3: A \"machines\" table with the following columns: \n- Machine. \n \n- Description: The value of the DESCRIPTION variable in the .conf file \n- Select machine, which shows a \"select\" button. The \"select\" button is disabled when the layer is not added to the project. \nThe machines table is sorted by \"Machine\" in ascending alphabetical order. ", + "expected_results": "All mentioned elements should be present and functional." + } + }, + "summary": "Layer_details_page:_UI_functionality_for_imported_layers" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Multiple_build_directories", + "author": [ + { + "email": "stanciux.mihail@intel.com", + "name": "stanciux.mihail@intel.com" + } + ], + "execution": { + "1": { + "action": "after starting Toaster for the first time, go to http://[localhost]:8000/admin/ and login with the admin user you created during setup. Click on the Build environments section, and on the BuildEnvironment object. \n\n\n\nNote: you can create a superuser to enter as admin with ... poky/bitbake/lib/toaster/manage.py createsuperuser \n\n\n", + "expected_results": "" + }, + "2": { + "action": "make note of the \"sourcedir\" and \"builddir\" values. The build dir will be something like \"/home/user/path/build\" \n\n", + "expected_results": "" + }, + "3": { + "action": " click \"back\", and click on the \"Add build environment\" button in the upper right corner. \n\n", + "expected_results": "" + }, + "4": { + "action": "enter Address \"2\", Betype: \"local\", \"sourcedir\" is to be set to whatever the original build env is set, and \"builddir\" is ANOTHER path at the same level as the original builddir - e.g. \"/home/user/path/build2\" \n\n", + "expected_results": "" + }, + "5": { + "action": "Click save \n\n", + "expected_results": "" + }, + "6": { + "action": "Execute command : /poky$ source oe-init-build-env build2 \n\n", + "expected_results": "" + }, + "7": { + "action": "Create new project \n\n", + "expected_results": "" + }, + "8": { + "action": "issue 2 build (e.g. core-image-minimal core-image-sato)\n\n\n\n\n\n", + "expected_results": "Both build commands should run simultaneously." + } + }, + "summary": "Multiple_build_directories" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Run_again_button_from_all_builds_page_must_run_the_specified_task", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": "Click on new project button.", + "expected_results": " Open create a new project page. \n" + }, + "3": { + "action": "Enter a project name, select a release and click on create project or select an existing project.", + "expected_results": " Project Created. \n" + }, + "4": { + "action": "Build a image task (ex: core-image-minimal:clean) and wait until build finish.\nfrom all build page.", + "expected_results": " Build task finishes successfully. \n" + }, + "5": { + "action": "Click on rebuild button from all build page.", + "expected_results": "Specified task will run again. \n" + }, + "6": { + "action": "Click on the build and verify if the number of tasks executed = 1.", + "expected_results": "Only the specified task is executed. \n" + }, + "7": { + "action": "From project builds page click on run again button.", + "expected_results": "Specified task will run again.\n" + }, + "8": { + "action": "Click on the build and verify if the number of tasks executed = 1.", + "expected_results": "" + } + }, + "summary": "Run_again_button_from_all_builds_page_must_run_the_specified_task" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Intel_layers_builds", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": "Click on new project button.", + "expected_results": "Open create a new project page. \n" + }, + "3": { + "action": "Enter a project name, select a release and click on create project.", + "expected_results": "Project Created. \n" + }, + "4": { + "action": "Click on layers tab.", + "expected_results": "Open compatible layers page. \n" + }, + "5": { + "action": "Search for intel.", + "expected_results": "Return results \n" + }, + "6": { + "action": "Add intel layers like: meta-intel, meta-intel-quark.", + "expected_results": "Layers added to project. \n" + }, + "7": { + "action": "Click on the added layer.", + "expected_results": "Open layer page. \n" + }, + "8": { + "action": "From machine tab, select a machine.", + "expected_results": "Machine has changed. \n" + }, + "9": { + "action": "Build a recipe(core-image-minimal) or a recipe from recipe tab.", + "expected_results": "Build finishes successfully." + } + }, + "summary": "Intel_layers_builds" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Download_other_artifacts", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Delete the build/tmp folder. (to make sure the rootfs task runs and other artifacts are generated for the build)", + "expected_results": "" + }, + "2": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n\t" + }, + "3": { + "action": "Click on new project button.", + "expected_results": "Open create a new project page. \n\t" + }, + "4": { + "action": "Enter a project name, select a release and click on create project.", + "expected_results": "Project Created. \n\t" + }, + "5": { + "action": "Build an image recipe (ex: core-image-minimal) and wait until build finish.", + "expected_results": "Build finishes successfully. \n\t" + }, + "6": { + "action": "Click on the built recipe.", + "expected_results": "Open build summary page. \n\t" + }, + "7": { + "action": "From other artifacts tab click on a link.", + "expected_results": "You can download other artifacts." + } + }, + "summary": "Download_other_artifacts" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Download_licence_manifest", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Delete the build/tmp folder. (to make sure license manifest is generated)", + "expected_results": "" + }, + "2": { + "action": "Start Toaster \n\n", + "expected_results": "Toaster starts. \n" + }, + "3": { + "action": "Click on new project button. \n\n", + "expected_results": "Open create a new project page. \n" + }, + "4": { + "action": "Enter a project name, select a release and click on create project. \n\n", + "expected_results": "Project Created. \n" + }, + "5": { + "action": "Build an image recipe (ex: core-image-minimal) and wait until build finish. \n\n", + "expected_results": "Build finishes successfully. \n" + }, + "6": { + "action": "Click on the built recipe. \n\n", + "expected_results": "Open build summary page. \n" + }, + "7": { + "action": "From Image tab click on \"Download\" button for License manifest.", + "expected_results": "You can download license manifest." + } + }, + "summary": "Download_licence_manifest" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_dependencies_layers", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": "Click on new project button.", + "expected_results": "Open create a new project page. \n" + }, + "3": { + "action": "Enter a project name, select a release and click on create project.", + "expected_results": "Project Created. \n" + }, + "4": { + "action": "Click on Layers.", + "expected_results": "Open compatible layers page. \n" + }, + "5": { + "action": "Add a layer with multi-level dependencies. (ex: meta-acer) \nThis layer depends on meta-networking, which in turn depends on meta-android. \n \n", + "expected_results": "The selected layer and dependencies were added to project. \n" + }, + "6": { + "action": "Check if meta-python appears in the dependencies list, and add the layers to project.", + "expected_results": "" + }, + "7": { + "action": "Delete a dependency layer.", + "expected_results": "Layer removed from project. \n \n" + }, + "8": { + "action": "Build a recipe (ex: core-image-minimal) and wait until build finish.\n", + "expected_results": "Build will fail with an error.\n\n\t" + } + }, + "summary": "Test_dependencies_layers" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_build_recipe_button_from_recipes_page", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": "Click on new project button.", + "expected_results": "Open create a new project page. \n" + }, + "3": { + "action": "Enter a project name, select a release and click on create project.", + "expected_results": "Project Created. \n" + }, + "4": { + "action": "Click on software recipes / image recipes.", + "expected_results": "Open compatible software recipes page. \n" + }, + "5": { + "action": "Select a recipe and click on 'add layer' button.", + "expected_results": "Layer added to project and the 'add layer' button becomes 'build recipe'. \n" + }, + "6": { + "action": "Click on \"Build recipe\" button for one recipe (ex : core-image-minimal / busybox).", + "expected_results": "Build finishes successfully." + }, + "7": { + "action": "Test this for software and image recipes tables.", + "expected_results": "" + } + }, + "summary": "Test_build_recipe_button_from_recipes_page" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_compatible_machines", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": "Click on new project button.", + "expected_results": "Open create a new project page. \n" + }, + "3": { + "action": "Enter a project name, select a master release and click on create project.", + "expected_results": "Project Created. \n" + }, + "4": { + "action": "Go to machines page.", + "expected_results": "Open compatible machines page. \n" + }, + "5": { + "action": "Choose a machine and click on add layer for it. (intel-core2-32)", + "expected_results": "Layers added to project and add layer button becomes select machine. \n" + }, + "6": { + "action": "Click on select machine.", + "expected_results": "Machine has changed. \n" + }, + "7": { + "action": "Go to layer page that generate the machine. (meta-intel)", + "expected_results": "Open layer page \n" + }, + "8": { + "action": "Build a recipe generated by that layer.", + "expected_results": "Build finishes successfully." + } + }, + "summary": "Test_compatible_machines" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Builds_with_different_machines", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": "Click on new project button.", + "expected_results": "Open create a new project page. \n" + }, + "3": { + "action": "Enter a project name, select a master release and click on create project.", + "expected_results": "Project Created. \n" + }, + "4": { + "action": "Select a machine (ex: qemux86-64)", + "expected_results": "The machine has changed. \n" + }, + "5": { + "action": "Build a recipe (ex: core-image-minimal) and wait until buid finish.", + "expected_results": "Build finishes successfully. \n" + }, + "6": { + "action": "Go to project page and change the machine (ex: qemumips)", + "expected_results": "The machine has changed. \n" + }, + "7": { + "action": "Build a recipe (ex: core-image-sato) and wait until build finish.", + "expected_results": "Build finishes successfully. \n\nYou can build recipes with different machines." + }, + "8": { + "action": "Check on build summary page that the machine match the machine selected.", + "expected_results": "" + } + }, + "summary": "Builds_with_different_machines" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_bitbake_variables_-_IMAGE_FSTYPES", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": "Click on new project button.", + "expected_results": "Open create a new project page. \n" + }, + "3": { + "action": "Enter a project name, select release and click on create project.", + "expected_results": "Project Created. \n" + }, + "4": { + "action": "Go to Configuration --> BitBake variables", + "expected_results": "Open Bitbake variables page. \n" + }, + "5": { + "action": "Change IMAGE_FSTYPES variable, add some image types like: hddimg, ext4, etc.", + "expected_results": "Image types were added. \n" + }, + "6": { + "action": "Build a recipe (ex: core-image-minimal) and wait until build finish.", + "expected_results": "Build finishes successfully. \n" + }, + "7": { + "action": "Verify in the build summary page if the image types selected were built.", + "expected_results": "All the image types selected appears in the build summary page." + } + }, + "summary": "Test_bitbake_variables_-_IMAGE_FSTYPES" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Software_recipes:_default_view", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": " Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n\n", + "expected_results": "" + }, + "2": { + "action": " If no images exist in the project, build an image by inserting \"core-image-minimal\" in the \"Recipes\" field and press the \"Build\" button. Wait for the image to finish building. \n\n", + "expected_results": "" + }, + "3": { + "action": "On the project page click on the \"Software Recipes\" link situated in the left-handed side of the page, under the \"Project configuration\" menus, in the \"COMPATIBLE METADATA\" table. \n\n\n", + "expected_results": "" + }, + "4": { + "action": "Check that \"Compatible software recipes\" table is populated. \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that the following columns are shown by default: \n\n\t\tSoftware recipe \n\t\tDescription \n \n\t\tLayer \n\t\tBuild \n\t\t Version ", + "expected_results": "" + } + }, + "summary": "Software_recipes:_default_view" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Software_recipes:_sorting_the_content_of_the_software_recipes_table", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Navigate to the \"Software Recipes\" page. \n\n", + "expected_results": "" + }, + "3": { + "action": "Make sure the table is sorted on the \"Software Recipe\" column by default in ascending order. \n\n", + "expected_results": "" + }, + "4": { + "action": "Activate all columns from the \"Edit column\" drop-down menu. Check that \"Build\" and \"Software Recipe\" columns cannot be unchecked. \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that \"Software Recipe\", \"Section\", \"License\", \"Layer\" are the only sortable table heads. \n\n", + "expected_results": "" + }, + "6": { + "action": "Sort the table by \"Layer\" and then navigate away by selecting a layer(such as meta-yocto). When you click \"back\" button in web-browser to go back to the \"Compatible image recipes\" table it should still be sorted by \"Layer\". \n\n", + "expected_results": "" + }, + "7": { + "action": "Sorting and \"Edit columns\" \nIf you use the \"Edit columns\" menu to hide the column with the applied sorting, we revert the sorting to the default sorting (i.e. \"Recipe\"). The default sorting always uses one of the core columns, which cannot be hidden using the \"Edit columns\" menu. \n\n", + "expected_results": "" + }, + "8": { + "action": "Sorting and search \nSearching should have no impact on the applied sorting. Any results returned should be sorted by the sorting criteria selected when the search query was submitted. \nSort recipes by \"Layer\" column heading. Input a string (such as \"meta\") in search box and click search button. Make sure results returned are sorted by \"Layer\".", + "expected_results": "" + } + }, + "summary": "Software_recipes:_sorting_the_content_of_the_software_recipes_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Software_recipes:_Searching_the_content_of_the_software_recipes_table", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "Navigate to the \"Software Recipes\" page. \n\n", + "expected_results": "" + }, + "3": { + "action": "Check that the search is made of a text input field and a \"Search\" button in a toolbar above the table. \n\n", + "expected_results": "" + }, + "4": { + "action": "When no search query has been entered, we have placeholder text saying: \"Search compatible software recipes\". \n\n", + "expected_results": "" + }, + "5": { + "action": "Input \"core\" in the text input field. The placeholder text disappears when the first character is typed. Click search button. \n\n", + "expected_results": "" + }, + "6": { + "action": " \n(1) returned results \nThe search string is kept in the text input field. The results returned occur. Click \"Clear search\" icon to clear the search and display the compatible recipes. \n(2) no results returned \nIf your search query returns no results, the page heading changes to \"No recipes found\", and we show you an alert with a search form and an option to show all targets. Check that \"show compatible recipes\" button is available. \n\n", + "expected_results": "" + }, + "7": { + "action": "When I run a search, the search happens against the following columns (independently of they being shown or hidden):\n- Software Recipe\n- Recipe version\n- Description\n- Recipe file\n- Section\n- License\n- Layer\n- Revision\nInput a string to search for the above column headings separately to make sure that the search happens against the columns. \n", + "expected_results": "" + }, + "8": { + "action": "Search, sorting and \"Edit columns\" \nSearching does not change the state of the table: the same columns remain hidden and the same sorting applied when search results are displayed, but filters are cleared by the search results.\nSearch a string and make sure that the same columns remain hidden and the same sorting applied. \n\n", + "expected_results": "" + }, + "9": { + "action": "Search and filters \nThe scope of the filters is the content currently on the table (this means all table pages, not only the one displayed). The scope of the search is always the content of the database. \n\nIf I run a search query, any filter applied afterwards will filter the content returned by the search query. \n\nIf I run a search query while a filter is applied, the filter is cleared by the results of the search query (i.e. we display the results of the search query and clear the filter applied beforehand). The same happens if I click the \"Clear search\" icon when a filter is applied to a set of search results (both search results and applied filter are cleared, and the table shows all the targets). ", + "expected_results": "" + } + }, + "summary": "Software_recipes:_Searching_the_content_of_the_software_recipes_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Software_recipes:_Filter_the_contents_of_the_software_recipes_table", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All builds\" table.", + "expected_results": "" + }, + "2": { + "action": "Navigate to the \"Software Recipes\" page.", + "expected_results": "" + }, + "3": { + "action": "Make sure the following table column has filters: \n- Build", + "expected_results": "" + }, + "4": { + "action": "Filters are mutually exclusive. Click a filter button of a one column and a filter dialogue occurs. Select a filter item. The filter result would be showed. Then select another filter item of another column and the previously applied filter is overridden by the newly selected filter when a filter from a different column is applied to the table. In this state, we show some help text next to the \"Apply\" button, saying \"You can only apply one filter to the table. This filter will override the current filter.\"", + "expected_results": "" + }, + "5": { + "action": "Filters are overridden by search. Run a search query and you can see previous filter results are overridden by the results of the search query.", + "expected_results": "" + } + }, + "summary": "Software_recipes:_Filter_the_contents_of_the_software_recipes_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_the_packages_included_in_the_image", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": " Click on new project button.", + "expected_results": " Open create a new project page. \n" + }, + "3": { + "action": " Enter a project name, select a release and click on create project.", + "expected_results": " Project Created. \n" + }, + "4": { + "action": " Build a recipe (ex: core-image-minimal) and wait until build finish.", + "expected_results": " Build finishes successfully. \n" + }, + "5": { + "action": " Click on the built recipe.", + "expected_results": " Open build summary page. \n" + }, + "6": { + "action": " Under IMAGES tab click on the recipe built.", + "expected_results": "Image page open. \n" + }, + "7": { + "action": "Click on a package name.", + "expected_results": "Open the package page. \n" + }, + "8": { + "action": "Under file title click on the link to file.", + "expected_results": "You are redirected to directory structure and you can see where the file is located." + } + }, + "summary": "Test_the_packages_included_in_the_image" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_the_filters_from_a_image_page", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": " Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": " Click on new project button.", + "expected_results": " Open create a new project page. \n" + }, + "3": { + "action": " Enter a project name, select a release and click on create project.", + "expected_results": " Project Created. \n" + }, + "4": { + "action": " Build a recipe (ex: core-image-minimal) and wait until build finish.", + "expected_results": " Build finishes successfully. \n" + }, + "5": { + "action": " Click on the built recipe.", + "expected_results": " Open build summary page. \n" + }, + "6": { + "action": "Click on Configuration - Bitbake Variables.", + "expected_results": "Open bitbake variables page. \n" + }, + "7": { + "action": "Test Description filter. ", + "expected_results": "Filter works ok. (filter returns only items that match the selected criteria) " + } + }, + "summary": "Test_the_filters_from_a_image_page" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_dependencies_link", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": " Start Toaster.", + "expected_results": "Toaster starts. \n" + }, + "2": { + "action": " Click on new project button.", + "expected_results": " Open create a new project page. \n" + }, + "3": { + "action": " Enter a project name, select a release and click on create project.", + "expected_results": " Project Created. \n" + }, + "4": { + "action": " Build a recipe (ex: core-image-minimal) and wait until build finish.", + "expected_results": " Build finishes successfully. \n" + }, + "5": { + "action": " Click on the built recipe.", + "expected_results": " Open build summary page. \n" + }, + "6": { + "action": "Click on recipes tab.", + "expected_results": "Open recipes page. \n" + }, + "7": { + "action": "Click on edit columns and select Dependencies.", + "expected_results": "Dependencies column is shown in the table. \n" + }, + "8": { + "action": "Click on a number of dependencies.", + "expected_results": "A pop up with dependencies will appear. \n" + }, + "9": { + "action": "Click on a dependency. ", + "expected_results": "Open recipe dependency page. " + } + }, + "summary": "Test_dependencies_link" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_recipe_file_link", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster. \n\n\t", + "expected_results": "Toaster starts. \n\n\t" + }, + "2": { + "action": " Click on new project button. \n\n\t", + "expected_results": " Open create a new project page. \n\n\t" + }, + "3": { + "action": " Enter a project name, select a release (ex: master) and click on create project. \n\n\t", + "expected_results": " Project Created. \n\n\t" + }, + "4": { + "action": "Click on Image recipes tab. \n\n\t", + "expected_results": "Open Compatible image recipes table. \n\n\t" + }, + "5": { + "action": "Click on edit columns and select recipe file. \n\n\t", + "expected_results": "Recipe file column appears in the table. \n\n\t" + }, + "6": { + "action": "Click on the blue button near a recipe file. \n\n\t", + "expected_results": "" + }, + "7": { + "action": "Repet steps - 4 to 6 for software recipes.", + "expected_results": "" + } + }, + "summary": "Test_recipe_file_link" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.See_packages_size", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster. \n\n\t", + "expected_results": " Toaster starts. \n\n\t" + }, + "2": { + "action": " Click on new project button. \n\n\t", + "expected_results": " Open create a new project page. \n\n\t" + }, + "3": { + "action": " Enter a project name, select a release and click on create project. \n\n\t", + "expected_results": " Project Created. \n\n\t" + }, + "4": { + "action": " Build a recipe (ex: core-image-minimal) and wait until build finish. \n\n\t", + "expected_results": " Build finishes successfully. \n\n\t" + }, + "5": { + "action": " Click on the built recipe. \n\n\t", + "expected_results": " Open build summary page. \n\n\t" + }, + "6": { + "action": "Click on packages tab. \n\n\t", + "expected_results": "Open packages page. \n\n\t" + }, + "7": { + "action": "Click on size to sort the table. ", + "expected_results": "You can check the size of each package. \n\nWhen you click on 'Size' the first time, the correct sorting is the inverse one (biggest package on top). Clicking a second time will invert the sorting (you'll see packages with 0 B size on top)." + } + }, + "summary": "See_packages_size" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Build_multiple_recipes", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": " Start Toaster. \n\n\t", + "expected_results": " Toaster starts. \n\n\t" + }, + "2": { + "action": " Click on new project button. \n\n\t", + "expected_results": " Open create a new project page. \n\n\t" + }, + "3": { + "action": " Enter a project name, select a release and click on create project. \n\n\t", + "expected_results": " Project Created. \n\n\t" + }, + "4": { + "action": " Build a multiple recipes (ex: \"core-image-minimal core-image-sato\") and wait until build finish. ", + "expected_results": "Builds finishes successfully. \n\nYou can build multiple recipes with toaster" + } + }, + "summary": "Build_multiple_recipes" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Build_a_recipe_with_different_distro", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": " Start Toaster. \n\n\t", + "expected_results": " Toaster starts. \n\n\t" + }, + "2": { + "action": " Click on new project button. \n\n\t", + "expected_results": " Open create a new project page. \n\n\t" + }, + "3": { + "action": " Enter a project name, select a release and click on create project. \n\n\t", + "expected_results": " Project Created. \n\n\t" + }, + "4": { + "action": "From project page click on Bitbake variables tab. \n\n\t", + "expected_results": "Open Bitbake variables page. \n\n\t" + }, + "5": { + "action": "Click on change button for distro. \n\n\t", + "expected_results": "A type in form appears. \n\n\t" + }, + "6": { + "action": "Change distro (ex: poky-tiny). \n\n\t", + "expected_results": "Distro has changed. \n\n\t" + }, + "7": { + "action": "Add specific layers for distro (meta-qt3, meta-qt4) \n\t\n\t", + "expected_results": "Layers added to the project \n\n\t" + }, + "8": { + "action": " Build a recipe (ex: core-image-minimal) and wait until build finish.", + "expected_results": "Build finishes successfully. \n\nThe 'success' criteria for this one should be that the build is reported as using the poky-tiny distro in the build summary page, and that the DISTRO variable value in the bitbake variables table is set to the value specified in toaster (poky-tiny again)." + } + }, + "summary": "Build_a_recipe_with_different_distro" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_package_format_-_ipk_rpm_deb", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": " Start Toaster. \n\n\t", + "expected_results": " Toaster starts. \n\n\t" + }, + "2": { + "action": " Click on new project button. \n\n\t", + "expected_results": " Open create a new project page. \n\n\t" + }, + "3": { + "action": " Enter a project name, select a release and click on create project. \n\n\t", + "expected_results": " Project Created. \n\n\t" + }, + "4": { + "action": "From the project page click on bitbake variables tab. \n\n\t", + "expected_results": "Open bitbake variables page. \n\n\t" + }, + "5": { + "action": "Click on change button near PACKAGE_CLASSES and select all the package formats (rpm, deb, ipk). \n\n\t", + "expected_results": "Package classes selected. \n\n\t" + }, + "6": { + "action": "Build a recipe (ex: core-image-minimal) and wait until build finish.", + "expected_results": "Build finishes successfully.\nYou can see the package classes in the build summary page." + } + }, + "summary": "Test_package_format_-_ipk_rpm_deb" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Test_IMAGE_INSTALL_append_variable", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster. \n\n", + "expected_results": " Toaster starts. \n\n\t" + }, + "2": { + "action": " Click on new project button. \n\n", + "expected_results": " Open create a new project page. \n\n\t" + }, + "3": { + "action": " Enter a project name, select a release and click on create project. \n\n", + "expected_results": " Project Created. \n\n\t" + }, + "4": { + "action": "From the project page click on bitbake variables tab. \n\n", + "expected_results": "Open bitbake variables page. \n\n\t" + }, + "5": { + "action": "Click on change button for IMAGE_INSTALL:append and add a variable (ex: acpid). \n\n", + "expected_results": "Variable added. \n\n\t" + }, + "6": { + "action": "Build a recipe (ex: core-image-minimal) and wait until build finish. \n\n", + "expected_results": "Build finishes successfully. \n\n\t" + }, + "7": { + "action": "After build finishes go to build page. \n\n", + "expected_results": "Open build summary page. \n\n\t" + }, + "8": { + "action": "Go to package tab and search for acpid.", + "expected_results": "You should get results for ssh packages." + } + }, + "summary": "Test_IMAGE_INSTALL:append_variable" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.New_custom_image:_default_view", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All projects\" table. \n\n\n", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"New custom image\" link situated on the left-hand side, near Configuration, builds, import layer \n\n\n", + "expected_results": "" + }, + "3": { + "action": "Check that the table is populated with the list of image recipes (eg. core-image minimal) \n\n\n", + "expected_results": "" + }, + "4": { + "action": " Check that by default the following columns are shown: Image recipe, Version, Description, Layer, Customise \n\n\n", + "expected_results": "" + }, + "5": { + "action": "From the \"Edit columns\" menu, activate the: Recipe file, Section, License, Git revision \n\n\n", + "expected_results": "" + }, + "6": { + "action": "Check that the \"Git revision\" entries match the release entry from the main project page, in the project details section. \n\n\n", + "expected_results": "" + }, + "7": { + "action": "Check that the image recipes provided by layers added to the project show a 'customise' button, while image recipes provided by layers not added to the project show an 'add layer' button ", + "expected_results": "" + } + }, + "summary": "New_custom_image:_default_view" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.New_custom_image:_sorting_the_content_of_new_custom_image_table", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All projects\" table. \n\n", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"New custom image\" link situated on the left-hand side, near Configuration, builds, import layer \n\n", + "expected_results": "" + }, + "3": { + "action": "Make sure that the table is sorted on the ‘Image recipe’ column by default in ascending order. \n\n", + "expected_results": "" + }, + "4": { + "action": "Clicking on Image recipe should revert the sorting. (from 'a to z' changes to 'z to a') \n\n", + "expected_results": "" + }, + "5": { + "action": "From the \"Edit columns\" menu activate all the columns. Check that ‘Image recipe’ and ‘Customise’ columns cannot be unchecked. \n\n", + "expected_results": "" + }, + "6": { + "action": "Check that Image recipe, Section, Layer and License are the only sortable table heads. \n\n", + "expected_results": "" + }, + "7": { + "action": "Sort the table by \"Layer\" and then navigate away by selecting an image. When you click the \"back\" button in the web-browser to go back, the \"New custom image\" table should still be sorted by \"Layer\". \nThis should apply also by navigating back to the page by any other means. \n\n", + "expected_results": "" + }, + "8": { + "action": "Sorting and \"Edit columns\" menu: If you use the \"Edit columns\" menu to hide the column with the applied sorting, we revert the sorting to the default sorting (i.e. \"Image recipe\"). The default sorting always uses one of the core columns, which cannot be hidden using the \"Edit columns\" menu \n\n", + "expected_results": "" + }, + "9": { + "action": "Sorting and search: Searching should have no impact on the applied sorting. Any results returned should be sorted by the sorting criteria selected when the search query was submitted. Sort recipes by \"Layer\" column heading. Input a string (such as \"core-image\") in search box and click search button. Make sure results returned are sorted by \"Layer\".", + "expected_results": "N/A" + } + }, + "summary": "New_custom_image:_sorting_the_content_of_new_custom_image_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.New_custom_image:_searching_the_content_of_new_custom_image_table", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All projects\" table. \n \n\n\n", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"New custom image\" link situated on the left-hand side, near Configuration, builds, import layer \n \n\n\n", + "expected_results": "" + }, + "3": { + "action": "Check that the search is made of a text input field and a \"Search\" button in a toolbar above the table. When no search query has been entered, the text input field should show the following placeholder text: \"Search select the image recipe you want to customise\" \n \n\n\n", + "expected_results": "" + }, + "4": { + "action": "Input \"core\" in the text input field. The placeholder text disappears when the first character is typed. Click search button. \n \n\n\n", + "expected_results": "" + }, + "5": { + "action": "The search string is kept in the text input field. The results returned occur. Click \"Clear search\" icon to clear the search and display the image recipes. If your search query returns no results, we show you an alert with a search form and an option to show all image recipes. Check that \"show all\" link is available. \n\n\n", + "expected_results": "" + }, + "6": { + "action": "Search, sorting and \"Edit columns\": Searching does not change the state of the table: the same columns remain hidden and the same sorting applied when search results are displayed, but filters are cleared by the search results. Search a string and make sure that the same columns remain hidden and the same sorting applied. \n\n\n", + "expected_results": "" + }, + "7": { + "action": "Search and filters \n \n\t•\tThe scope of the filters is the content currently on the table (this means all table pages, not only the one displayed). The scope of the search is always the content of the database. \n\n\n", + "expected_results": "" + }, + "8": { + "action": "If I run a search query, any filter applied afterwards will filter the content returned by the search query. \tIf I run a search query while a filter is applied, the filter is cleared by the results of the search query (i.e. we display the results of the search query and clear the filter applied beforehand). The same happens if I click the \"Clear search\" icon when a filter is applied to a set of search results (both search results and applied filter are cleared, and the table shows all the targets). ", + "expected_results": "\n \n" + } + }, + "summary": "New_custom_image:_searching_the_content_of_new_custom_image_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.New_custom_image:_Filter_the_contents_of_the_new_custom_image_table", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All projects\" table. \n\n\n", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"New custom image\" link situated on the left-hand side, near Configuration, builds, import layer \n\n\n", + "expected_results": "" + }, + "3": { + "action": "Make sure the following table column has filters: Customise \n\n\n", + "expected_results": "" + }, + "4": { + "action": "Click the filter button in the \"Customise\" column and a filter dialogue comes up. Select a filter option. The filter results should be showed. \n\n\n", + "expected_results": "" + }, + "5": { + "action": "Filters are overridden by search. Run a search query and you can see previous filter results are overridden by the results of the search query.", + "expected_results": "N/A" + } + }, + "summary": "New_custom_image:_Filter_the_contents_of_the_new_custom_image_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Create_new_custom_image", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All projects\" table. \n \n\n\n", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"New custom image\" link situated on the left-hand side, near Configuration, builds, import layer \n\n\n", + "expected_results": "" + }, + "3": { + "action": "Search for rpi-basic-image, click on 'add layer' button. Make sure a \"layer added\" notification shows and a \"customise\" button is displayed. Click the \"customise\" button, type a name for you new custom image and click on create custom image. \n\n", + "expected_results": "" + }, + "4": { + "action": "Verify that image was created: when you create the custom image you will be redirected to the custom image details page, and a notification at the top of the page should tell you: ‘Your custom image X has been created. You can now add or remove packages as needed. \n\n", + "expected_results": "" + }, + "5": { + "action": "If you select an image that has not been built beforehand you should not see the 'add / remove' packages table until you build the image. \n\n", + "expected_results": "" + }, + "6": { + "action": "If you select an image that has been built beforehand you should see the 'add / remove' packages table when you create the custom image. ", + "expected_results": "N/A" + } + }, + "summary": "Create_new_custom_image" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Custom_image_page_details", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "After you create a new custom image go to the custom image page, by clicking on the custom image. \n\n", + "expected_results": "" + }, + "2": { + "action": "Breadcrumbs \n \n\t * Observe that the 3 breadcrumbs at the top left are: \n \n\t\ta live link that will take you back to the project page \n\t\tCustom images: a live link that will take you back to the custom images table \n\t\timage name(toaster-custom-images): the name of the current custom image (not a link) \n \n\n\n", + "expected_results": "" + }, + "3": { + "action": "Observe the 2 buttons build Custom image and Download recipe file \n \n\ti.\tTest this 2 buttons \n\tii.\tYou should always be able to build the custom image, but you only should be able to download the recipe file when the package content of the custom image is known. When you cannot download the recipe file, the 'download' button at the top of the page is disabled, and the right hand column does not show information about the recipe file. \n\n", + "expected_results": "" + }, + "4": { + "action": "Observe that there is a right-hand box, with information about the images \n \n\ti.\tThere is a number of packages included in the custom image \n\tii.\tApprox package size \n \n\tiii.\tLayer \n \n\tiv.\tImage based on \n \n\tv.\tRecipe file (only when you can download it_ \n\tvi.\tVersion \n \n\tvii.\tLicense \n\n", + "expected_results": "" + }, + "5": { + "action": "Observe that the page includes a table with packages and you can add or remove packages from the custom image. The packages table only appears when: \n\na) the image recipe you chose as your base image when creating the custom image has been built within the project \n\nb) the custom image itself has been built \n\nIf no packages table shows, you see a notification with a build button instead. ", + "expected_results": "N/A" + } + }, + "summary": "Custom_image_page_details" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Custom_image_page_–_Add_|_Remove_packages_table", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "After you create a new custom image go to the custom image page, by clicking on the custom image. \n\n\n", + "expected_results": "" + }, + "2": { + "action": "Make sure that the table is sorted on the ‘Package’ column by default in ascending order. \n\n\n", + "expected_results": "" + }, + "3": { + "action": "Check that by default the following columns are shown: Package, Package Version, Approx Size \n\n\n", + "expected_results": "" + }, + "4": { + "action": "From the \"Edit columns\" menu, activate the: License, Recipe, Recipe version and Reverse dependencies columns \n\n", + "expected_results": "" + }, + "5": { + "action": "Check that ‘Package’, Approx Size, License, Recipe are the only sortable table heads. \n\n", + "expected_results": "" + }, + "6": { + "action": "Sorting and \"Edit columns\": If you use the \"Edit columns\" menu to hide the column with the applied sorting, we revert the sorting to the default sorting (i.e. \"Package\"). The default sorting always uses one of the core columns, which cannot be hidden using the \"Edit columns\" menu \n\n", + "expected_results": "" + }, + "7": { + "action": "Sorting and search: Searching should have no impact on the applied sorting. Any results returned should be sorted by the sorting criteria selected when the search query was submitted. Sort recipes by \"Recipe\" column heading. Input a string (such as \"acl\") in search box and click search button. Make sure results returned are still sorted by \"Recipe\". \n\n", + "expected_results": "" + }, + "8": { + "action": "Click \"Clear search\" icon to clear the search and display the Packages. \n\n", + "expected_results": "" + }, + "9": { + "action": "Make sure the following table column has filters: Add | Remove (Click on 'Edit custom image' in the left pane of the custom image) \n\n1", + "expected_results": "" + }, + "10": { + "action": "Click the filter button: a filter dialogue displays. Select a filter option. The filter results should be showed. \n\n1", + "expected_results": "" + }, + "11": { + "action": "Filters are overridden by search. Run a search query and you can see previous filter results are overridden by the results of the search query. \n\n1", + "expected_results": "" + }, + "12": { + "action": "This page needs a special no results message for the search. You can see in the doc attached to\nhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=9154 \n\nTo test it, enter a random string in the search input field (something like \"bbb\") and click the 'search' button. The special no results message includes the following: \n\na) instructions about searching and building recipes in order to generate new packages \n\nb) a search text input field with the search string you typed, a 'clear' icon and a search button. Click the 'clear' icon: the search field should be cleared and the full list of packages should be shown. \n\nc) a 'show all packages' link. Click the link: the search field should be cleared and the full list of packages should be shown. ", + "expected_results": "N/A" + } + }, + "summary": "Custom_image_page_–_Add_|_Remove_packages_table" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Adding_packages_without_dependencies_from_custom_images", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All projects\" table. \n\n ", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"New custom image\" link situated on the left-hand side, near Configuration, builds, import layer \n\n\n ", + "expected_results": " " + }, + "3": { + "action": "Choose an image recipe example:(core-image-sato) and click on the customise button on the far right (note if that layer is not added the button will say +Add layer, add it and then customise) \n\n\n ", + "expected_results": " A pop out should appear and you should get to give the new image a customized name. Then you will be redirected to a page of Add|Remove Packages. If this image has not been build it will not have packages.\n\n" + }, + "4": { + "action": "Build the new image if it has not been build, else start adding packages without dependencies example: attr-doc \n\n \n ", + "expected_results": "You should get a message in blue that says \"You have added 1 package to $image-custom-name: $package-name\" " + }, + "5": { + "action": "Build the image again.\n", + "expected_results": "Expected Result on step 5: the packages you have added should be installed in the image." + } + }, + "summary": "Adding_packages_without_dependencies_from_custom_images" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Removing_packages_without_and_with_dependencies__from_custom_images", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All projects\" table. \n\n ", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"New custom image\" link situated on the left-hand side, near Configuration, builds, import layer \n\n\n\n ", + "expected_results": " A pop out should appear and you should get to give the new image a customized name. Then you will be redirected to a page of Add|Remove Packages. If this image has not been build it will not have packages. \n\n" + }, + "3": { + "action": "Choose an image recipe example:(core-image-sato) and click on the customise button on the far right (note if that layer is not added the button will say +Add layer, add it and then customise) \n\n\n\n ", + "expected_results": "A pop out should appear and you should get to give the new image a customized name. Then you will be redirected to a page of Add|Remove Packages. If this image has not been build it will not have packages.\n\n" + }, + "4": { + "action": "Build the new image if it has not been build else start removing a packages (click on 'Edit custom image' in the left pane of the custom image) that have dependencies and packages that have no dependencies that are already included by clicking on the red button \"Remove Package\" \n\n\n \n ", + "expected_results": "You should get a message in blue that says \"You have removed 1 package to $image-custom-name: $package-name\" " + }, + "5": { + "action": "Build the image again.", + "expected_results": "the packages you have removed should not be installed in the image." + } + }, + "summary": "Removing_packages_without_and_with_dependencies__from_custom_images" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Adding_packages_with_dependencies", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Access a project page, either by creating a new project or accessing an existing project from the \"All projects\" table. \n\n ", + "expected_results": "" + }, + "2": { + "action": "On the project page click on the \"New custom image\" link situated on the left-hand side, near Configuration, builds, import layer \n\n\n ", + "expected_results": " " + }, + "3": { + "action": "Choose an image recipe example:(core-image-sato) and click on the customise button on the far right (note if that layer is not added the button will say +Add layer, add it and then customise) \n\n\n ", + "expected_results": "A pop out should appear and you should get to give the new image a customized name. Then you will be redirected to a page of Add|Remove Packages. If this image has not been build it will not have packages." + }, + "4": { + "action": "Build the new image if it has not been build else start adding packages that have dependencies ( you will be able to see in the dependencies column a little square with a number, that tells you the dependencies it holds) example: libattr this holds 2 dependencies( bash and glibc) ", + "expected_results": " You should get a pop-out that that say \"$package_name dependencies\" then it should list the dependencies. Once clicked on the add packages button it should add the packages listed in the pop-out." + }, + "5": { + "action": "Build the image again.", + "expected_results": "" + } + }, + "summary": "Adding_packages_with_dependencies" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Create_Project", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project by issuing a name and selecting a release version.", + "expected_results": "Once project is created it should redirect you to a new project configuration page" + }, + "3": { + "action": "Check that the h1 page title is set to the name the user typed in the new project form. ", + "expected_results": "" + } + }, + "summary": "Create_Project" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_project_detail_page_left_bar_menu", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n \n", + "expected_results": "Once project is created it should redirect you to a new project configuration page. \n\n" + }, + "3": { + "action": "Check the page contains the tabs \n Configuration ---> selected by default \n Compatible Metadata (separation label) \n Custom images \n Image recipes \n Software recipes \n Machines \n Layers \n Extra Configuration (separation label) \n BitBake variables \n\n", + "expected_results": " All elements are present. \n\n" + }, + "4": { + "action": "Click on each element to see if the h2 title is changing to the respective link clicked. Example if clicked on \"Custom Images\" then the h2 title should change to \"Custom images\"", + "expected_results": "All elements are clickable and h2 title changes to the corresponding title.." + } + }, + "summary": "Verify_project_detail_page_left_bar_menu" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Configuration_information_of_Project_Detail_page", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Clone Poky and start toaster \n\n", + "expected_results": "" + }, + "2": { + "action": "Create a master toaster project \n \n", + "expected_results": "Once project is created it should redirect you to a new project configuration page \n\n" + }, + "3": { + "action": "Check that the configuration button on the left side bar is selected by default \n\n", + "expected_results": " Expected result step 3 & 4: The configuration link next to the build link should be selected see attachment. \n\n\n\n" + }, + "4": { + "action": "The configuration details should include canvas: \n Machine \n Most built recipes \n Layers \n Project Release ", + "expected_results": "Expected result step 4: A machine must always be set. \n\nThe default layers specified in the Toaster configuration must always be listed in the layer section (in our case, for the poky configuration we should have openembedded-core, meta-poky and meta-yocto-bsp)" + } + }, + "summary": "Configuration_information_of_Project_Detail_page" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_Machine_information_of_project_detail_page", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n \n", + "expected_results": "Expected result step 2: Once project is created it should redirect you to a new project Configuration page \n\n" + }, + "3": { + "action": "The configuration details should include a label in bold font that says: \n Machine: this canvas should have the machine label type under it and an editing button on the side ", + "expected_results": "Expected result step 3: Compare to the attached snapshot. The machine must always be set." + } + }, + "summary": "Verify_Machine_information_of_project_detail_page" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_most_built_recipes_information_of_the_project_detail_page", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster ", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n \n", + "expected_results": "Expected result step 2: Once project is created it should redirect you to a new project configuration page " + }, + "3": { + "action": "The configuration details should include a label in bold font that says: \n Most built recipes: In this canvas one of the following information should show: \n\n a) If there has been no built recipes it should have a label that says: \n \"You haven't built any recipes yet, choose a recipe to build\" \n\n b) Else it should have a list of built recipes and a check box in front of it. So that it could be selected and built again ", + "expected_results": "Expected result step a: See ProjectDetailPage2.png attachment.\n\nExpected result step b: See ProjectDetailPage.png attachment." + } + }, + "summary": "Verify_most_built_recipes_information_of_the_project_detail_page" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_project_release_information_on_project_detail_page", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n \n", + "expected_results": "Expected result step 2: Once project is created it should redirect you to a new project configuration page. " + }, + "3": { + "action": "The configuration details should include a label in bold font that says: \n Project release: this canvas should also have a label that show the release project you chose at the beginning.", + "expected_results": "Expected result step 3: See attachment ProjectDetailPage.jnp." + } + }, + "summary": "Verify_project_release_information_on_project_detail_page" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_layer_information_of_the_project_detail_page", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Clone the poky environment git clone http://git.yoctoproject.org/git/poky", + "expected_results": "" + }, + "2": { + "action": "Start toaster", + "expected_results": "Expected result step 2: Once project is created it should redirect you to a new project configuration page. \n\n" + }, + "3": { + "action": "Create a toaster project \n \n", + "expected_results": "Expected result step 3: See attachment of layerCanvas.png\n" + }, + "4": { + "action": "The configuration details should include a label with bold font that says: \n Layer: this canvas should have 3 layers listed by default (openembedded-core, meta-poky, and meta-yocto-bsp). \n Each layer should have a trashcan icon at the side that can be used to erase the label from the project. \n The layer canvas should have a text box with the text \"type a layer name\" a button \"Add layer\" next to it. \n just underneath a \"view compatible layer | import layer\" link. ", + "expected_results": "" + } + }, + "summary": "Verify_layer_information_of_the_project_detail_page" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_project_detail_links", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster ", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n\n", + "expected_results": "Expected result step 2: Once project is created it should redirect you to a new project configuration page. \n\n" + }, + "3": { + "action": "The configuration details should include \n 4 links, starting in the upper left side the Configuration link, Builds(#) link, Import layer link, and the New custom image link. \n\n ", + "expected_results": "Expected result step 3: All links should be clickable and should have information or tables, or forms. see attachment projectDetailLinks.png" + } + }, + "summary": "Verify_project_detail_links" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_build_texbox_exists_and_works", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n \n", + "expected_results": " Once project is created it should redirect you to a new project configuration page. \n\n\n" + }, + "3": { + "action": "The configuration details should include \n After the 4 links (Configuration, Build(#), Import layer & New custom image) at the far right there should be a textbox with the label that says....\"Type the recipe you want to build\" and a button \"Build\" \n\n", + "expected_results": "See attachment buildTXT.png, The build button should be disabled whenever the text input field is empty, so that you cannot start a build with a blank target \n\n" + }, + "4": { + "action": "Type in the textbox an image you would like to build example (core-image-minimal) and click the build button.\n\n", + "expected_results": " Image starts building. Whenever there is information in the image recipes and software recipes tables, the text input field should present suggestions from the list of recipes provided by the layers in the \"layers\" list. The suggestions contain the string typed in the input field, and update as you type. They appear on typing the second character. A maximum of 8 suggestions can be shown. They are sorted as follows: first recipes starting with the string, in alphabetical order; then recipes containing the string, also in alphabetical order \n\n\nWhen you click the build button you are brought to the \"Builds\" tab, and a new build in progress appears at the top of the \"Latest project builds\" section" + } + }, + "summary": "Verify_build_texbox_exists_and_works." + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Veryfing_the_builds_link_show_proper_information", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n \n", + "expected_results": " Once project is created it should redirect you to a new project configuration page. \n\n\n" + }, + "3": { + "action": "The configuration details should include \n A builds tab that when clicking on, it should display one of the following: \n \n\n a) A label that says \"Latest project builds\" then a label with \"All project builds\" \n If you have a finished build or there is an ongoing builds then: \n You should see a progress bar of the ongoing builds in the project. \n You should see a table with the already done builds in the project. \n\n\n b) \"All project builds\" and a search textbox with a button nothing else only if there are no builds done in the project \n ", + "expected_results": "Expected result for step a): See ExistingBuilds.png attachment. \n\n\nExpected result for step b): See ZeroBuilds.png attachment. " + } + }, + "summary": "Veryfing_the_builds_link_show_proper_information" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_that_the_Import_layer_link_shows_the_form", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n\n", + "expected_results": " Once project is created it should redirect you to a new project configuration page. \n\n\n" + }, + "3": { + "action": "The configuration details should include \n An Import layer link that when clicking on, it should display: \n A label that says \"Layer repository information\" \n A label that says \"The layer you are importing must be compatible with Yocto Project master, which is the release you are using in this project.\" \n Form composed of the following elements: \n Layer name : textbox \n Git repository URL : textbox \n Repository subdirectory (optional) : textbox \n Git revision : textbox \n Layer dependencies (optional) : \"openembedded-core\" link and (trash icon), textbox and \"Add layer\" button \n Import and add to project : button", + "expected_results": " See attachment ImportLayerForm.png" + } + }, + "summary": "Verify_that_the_Import_layer_link_shows_the_form" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_that_New_Custom_Image_link_works_and_shows_information", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project \n\n", + "expected_results": " Once project is created it should redirect you to a new project configuration page \n\n\n" + }, + "3": { + "action": "The configuration details should include \n A \"New custom image\" tab that when clicking on, it should display: \n a Title label that says: \"Select the image recipe you want to customise(#number_or_recipes_available)\" \n A search textbox with the label of: \"Search and select the image recipe you want to customise\" \n A \"Search button\" \n A \"Edit columns\" button \n A table that will display the customise images available ", + "expected_results": "See attachment CustomImage.png" + } + }, + "summary": "Verify_that_New_Custom_Image_link_works_and_shows_information" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_most_built_recipe_shows_a_maximum_of_5_recipes", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project", + "expected_results": "" + }, + "3": { + "action": "Build 6 recipes example (core-image-sato, core-image-minimal, core-image-base) to name a few. ", + "expected_results": " All recipes are built correctly \n\n" + }, + "4": { + "action": "Wait for the recipes to finish ", + "expected_results": "" + }, + "5": { + "action": "Go to the configuration details.", + "expected_results": " You should see 5 of the 6 recipes that were build. If you order the recipes in alphabetical order you should see that the first 5 made the list. " + } + }, + "summary": "Verify_most_built_recipe_shows_a_maximum_of_5_recipes" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_order_sequence_of_listing_in_Most_build_recipes", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project", + "expected_results": "" + }, + "3": { + "action": "Build 6 recipes example (core-image-sato, core-image-minimal, core-image-base) to name a few. \n\n", + "expected_results": "All recipes are built correctly \n\n" + }, + "4": { + "action": "Wait for the recipes to finish \n\n", + "expected_results": "" + }, + "5": { + "action": "Go to the configuration details. \n\n", + "expected_results": " If you order the recipes in alphabetical order you should see that the first 5 made the list. Only 5 out of the 6 should make the list. \n\n" + }, + "6": { + "action": "Select the 6th recipe that did not make the list and build it again. ", + "expected_results": " Since the 6th recipe is now built twice it should make the list and the recipe in the 5th place should not appear." + } + }, + "summary": "Verify_order_sequence_of_listing_in_Most_build_recipes" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_Most_build_recipes_multiple_selection", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Start toaster", + "expected_results": "" + }, + "2": { + "action": "Create a toaster project", + "expected_results": "" + }, + "3": { + "action": "Build 4 recipes example (core-image-sato, core-image-minimal, core-image-base) to name a few. \n\n", + "expected_results": " All recipes are built correctly \n\n" + }, + "4": { + "action": "Wait for the recipes to finish. \n\n", + "expected_results": "" + }, + "5": { + "action": "Go to the configuration details. \n\n", + "expected_results": " You should see the 4 recipes in alphabetical order. You should also note that the Build button on the upper right hand corner is disabled since no recipe has been selected. \n\n" + }, + "6": { + "action": "Select 1 of the recipes in the most built recipes section. \n\n", + "expected_results": "The build button is automatically enabled. \n\n" + }, + "7": { + "action": "Select multiple (example 2 or 3) recipes in the most built recipes section. \n\n", + "expected_results": " The build button is enabled. \n\n" + }, + "8": { + "action": "Click on the build button to start building the recipes.", + "expected_results": "One recipe start to build and the others are on queue." + } + }, + "summary": "Verify_Most_build_recipes_multiple_selection" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_layer_addition_functionality", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Clone the poky environment git clone http://git.yoctoproject.org/git/poky", + "expected_results": "" + }, + "2": { + "action": "Start toaster", + "expected_results": " Once project is created it should redirect you to a new project configuration page. \n\n" + }, + "3": { + "action": "Create a toaster project with master release \n \n\n", + "expected_results": " See attachment of layerCanvas.png \n\n\n" + }, + "4": { + "action": "Add layers by typing the name in the \"Type a layer name\" input box and adding by clicking the button. \n\n", + "expected_results": " A list of layers with similar name to the one you are typing should appear, giving you the choice to add it. The default text \"Type a layer name\" should disappear as soon as you start typing. \n\n" + }, + "5": { + "action": "Add layers by clicking on the View compatible layers link just bellow the input text box. \n\n", + "expected_results": "This should redirect you to the compatible layers page where a list of compatible layers should appear and allow you to Add layers to the project. \n\n" + }, + "6": { + "action": "Add a layer by importing a layer clicking in the Import layer", + "expected_results": "This link should redirect you to the import layer form where you will be able to add layers from git repository or a local directory. \n\n\n" + } + }, + "summary": "Verify_layer_addition_functionality" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Verify_delete_layer_functionality", + "author": [ + { + "email": "libertad.gonzalez.de.la.cruz@intel.com", + "name": "libertad.gonzalez.de.la.cruz@intel.com" + } + ], + "execution": { + "1": { + "action": "Clone the poky environment git clone http://git.yoctoproject.org/git/poky\n", + "expected_results": "" + }, + "2": { + "action": "Start toaster", + "expected_results": " Once project is created it should redirect you to a new project configuration page.\n\n" + }, + "3": { + "action": "Create a toaster project master release \n \n", + "expected_results": "See attachment of layerCanvas.png \n\n" + }, + "4": { + "action": "Remove openembedded-core layer from the project by clicking the trash icon next to it. \n\n", + "expected_results": "The layer should disappear from the list and a notification should appear at the top of the page saying: \"You have removed 1 layer from your project: \". The layer_name should be a link to the corresponding layer detail page. The layer counter next to the \"layers\" heading should decrease by one. \n" + }, + "5": { + "action": "Remove all the layers from the project", + "expected_results": " you should see a message that reads: \n\nYou need to add some layers. For that you can: \n\n-View all layers compatible with this project \n\n-Import a layer \n\n-Read about layers in the documentation \n\nOr type a layer name below. \n\n\n The \"Choose from the layers compatible with this project\" link should go to the compatible layers page The \"Import a layer\" link should go to the import layer page The \"Read about layers in the documentation\" link should open in a new window and bring you to http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#understanding-and-creating-layers" + } + }, + "summary": "Verify_delete_layer_functionality" + } + }, + { + "test": { + "@alias": "toaster-managed-mode.toaster-managed.Download_task_log", + "author": [ + { + "email": "alexandru.costinx.roman@intel.com", + "name": "alexandru.costinx.roman@intel.com" + } + ], + "execution": { + "1": { + "action": "Start Toaster. ", + "expected_results": "Toaster starts." + }, + "2": { + "action": "Click on new project button.\n\n", + "expected_results": "Open create a new project page." + }, + "3": { + "action": " Enter a project name, select a release and click on create project or select an existing project. \n\n", + "expected_results": "Project Created." + }, + "4": { + "action": "Build a recipe (ex: core-image-minimal). \n\n", + "expected_results": "Build finish." + }, + "5": { + "action": "Click on the built recipe. \n\n", + "expected_results": "Open build summary page." + }, + "6": { + "action": "Click on tasks tab. \n\n", + "expected_results": "Open tasks page." + }, + "7": { + "action": "Click on a task executed successfully. \n\n", + "expected_results": "Open task page." + }, + "8": { + "action": "Click on \"Download task log\" button. \n", + "expected_results": "You can download the task log. \n" + }, + "9": { + "action": "Click on a failed task. \n", + "expected_results": "Open task page, not appear download task \n" + } + }, + "summary": "Download_task_log" + } + } +] diff --git a/meta/lib/oeqa/manual/toaster-unmanaged-mode.json b/meta/lib/oeqa/manual/toaster-unmanaged-mode.json new file mode 100644 index 0000000000..29d11a87d5 --- /dev/null +++ b/meta/lib/oeqa/manual/toaster-unmanaged-mode.json @@ -0,0 +1,1170 @@ +[ + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.Create_a_Yocto_project_and_start_the_Toaster", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Set up yocto project and toaster test environment. \ncd ${installdir} \ngit clone git://git.yoctoproject.org/poky \n\n", + "expected_results": "NA \n\n" + }, + "2": { + "action": "Start up toaster. \ncd ${installdir} \nsource poky/oe-init-build-env \nsource toaster start \n\n", + "expected_results": " \nlog: \nThe system will start. \nSyncing... \nCreating tables ... \nCreating table south_migrationhistory \nInstalling custom SQL ... \nInstalling indexes ... \nInstalled 0 object(s) from 0 fixture(s) \n > south \n\nNot synced (use migrations): \n - orm \n(use ./manage.py migrate to migrate these) \nRunning migrations for orm: \n - Migrating forwards to 0004_auto__add_field_package_installed_name. \n > orm:0001_initial \n > orm:0002_auto__add_field_build_timespent \n > orm:0003_timespent \n - Migration 'orm:0003_timespent' is marked for no-dry-run. \n > orm:0004_auto__add_field_package_installed_name \n - Loading initial data for orm. \nInstalled 0 object(s) from 0 fixture(s) \nserver address: 127.0.0.1, server port: 8200 \nSuccessful start." + }, + "3": { + "action": "Build the yocto project. \nbitbake core-image-minimal \n\n", + "expected_results": "Build successfully. \n" + }, + "4": { + "action": "Use a default web brower to see project build process. \nxdg-open http://localhost:8000/ \nWait for build completion. \n", + "expected_results": "You can open http://localhost:8000/ in a default browser. The build process is showed. " + } + }, + "summary": "Create_a_Yocto_project_and_start_the_Toaster." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.Sort_the_content_of_the_builds_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start up toaster.", + "expected_results": "Succeed to start up toaster. " + }, + "2": { + "action": "Create 2 builds, such as \"bitbake core-image-minimal\" and \"bitbake core-image-sato\". Wait for successful builds and then run: http://localhost:8000/", + "expected_results": "Succeed to build the targets. " + }, + "3": { + "action": "Enter \"All build\" table in web browser.", + "expected_results": "NA " + }, + "4": { + "action": "Click \"Completed on\" component to sort.", + "expected_results": "Build targets are sorted out by the \"Completed on\". " + }, + "5": { + "action": "Click \"Completed on\" component again to invert the sorting .", + "expected_results": "The sorting is inverted. " + }, + "6": { + "action": "Have a sort try in other columns. outcome, machine, started on, completed on, errors, warnings, project.", + "expected_results": "See item 4 and 5." + } + }, + "summary": "Sort_the_content_of_the_builds_table." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.Search_the_content_of_the_builds_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start up toaster.", + "expected_results": "NA " + }, + "2": { + "action": "Create 2 builds, such as \"bitbake core-image-minimal\" and \"bitbake core-image-sato\". Wait for successful builds and then run: xdg-open http://localhost:8000/", + "expected_results": "NA " + }, + "3": { + "action": "Enter \"All build\" table in web browser.", + "expected_results": "NA " + }, + "4": { + "action": "Input a string in search component and click search.", + "expected_results": "Show returned search results. When no search query has been entered, we have placeholder text saying: \"Search builds\". The placeholder text disappears when the first character is typed. " + }, + "5": { + "action": "See returned search results.", + "expected_results": "If your search query returns no results, the section heading changes to \"No builds found\", and we show you an alert with a search form and an option to show all builds. " + }, + "6": { + "action": "Click \"Clear search\" icon (icon-remove-sign). Observe all builds are showed. ", + "expected_results": "Click it to clear the search and display all builds." + } + }, + "summary": "Search_the_content_of_the_builds_table." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.Filter_the_content_of_the_builds_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start up toaster.", + "expected_results": "" + }, + "2": { + "action": "Create 2 builds, such as \"bitbake core-image-minimal\" and \"bitbake core-image-sato\". Wait for successful builds and then run: xdg-open http://localhost:8000/.", + "expected_results": "" + }, + "3": { + "action": "Enter \"All build\" table in web browser.", + "expected_results": "" + }, + "4": { + "action": "Make sure the following table columns have filters. \n- Outcome \n-- Started on \n- Completed on \n- Failed tasks", + "expected_results": "" + }, + "5": { + "action": "Filters are mutually exclusive. Click a filter button of a one column and a filter dialogue occurs. Select a filter item. The filter result would be showed. Then select another filter item of another column and the previously applied filter is overridden by the newly selected filter when a filter from a different column is applied to the table. In this state, we show some help text next to the \"Apply\" button, saying \"You can only apply one filter to the table. This filter will override the current filter.\"", + "expected_results": "" + }, + "6": { + "action": "Filters are overridden by search. Run a search query and you can see previous filter results are overridden by the results of the search query.", + "expected_results": "" + }, + "7": { + "action": "Have a try in filters of the following table columns. \n- Outcome \n- Started on \n- Completed on \n- Failed tasks \n", + "expected_results": "NA" + } + }, + "summary": "Filter_the_content_of_the_builds_table." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.Tasks_in_toaster_UI", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": " === TOASTER: Test Instructions for \"Tasks\", \"Time\", \"CPU Usage\", and \"Disk I/O\" pages === \n \nNOTE TO TESTERS: The three pages \"Time\", \"CPU Usage\", and \"Disk I/O\" are simple variations on the \"Tasks\" page. Those test instructions will demonstrate the respective unique parts. \n \n \n", + "expected_results": "" + }, + "2": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "3": { + "action": "In Toaster, select the build, and select the \"Tasks\" link in the left sidebar \n \n", + "expected_results": "" + }, + "4": { + "action": "Breadcrumbs \n \n * Observe that the 4 breadcrumbs at the top left are: \n \n : a live link that will take you back to the project page \n \t: a live link that will take you back to the project Builds page \n : a live link that will take you back to the image dashboard page \n \"Tasks\" \n \n * Test the breadcrumb live links, return to this page \n \n \n", + "expected_results": "" + }, + "5": { + "action": "General Layout \n \n * Observe the left-hand box with links to the other pages of the build \n \n * Observe the title of the table is \"Tasks\", in bold \n \n * Observe the search/filter bar above the table \n \n * Observe the number of table rows in each page matches the number selected in the \"Show rows\" dropdown menu \n \n * Observe at the bottom of the page the \"Showing XX to XX out of xxx entries\", the page selection links, and the \"Show Rows\" selection. \n \n \n", + "expected_results": "" + }, + "6": { + "action": "Columns \n \nNote: to restore the default columns in your browser, for example in Firefox, select \"Tools > Privacy > remove individual cookies\", find the cookies for the IP address of the Toaster engine (for example \"localhost\"), and remove each sub-cookie with the prefix \"_displaycols_*\" (or the whole cookie if those are the only sub-cookies). \n \n * Observe that the default columns are: \n \n \"Order, Recipe, Task, Executed, Outcome, Cache attempt\" \n \n * Click the \"Edit Columns\" button. ", + "expected_results": "" + }, + "7": { + "action": "Observe that the fields are sorted as follows (with the indicated items greyed) \n \n [ ] CPU usage \n [x] Cache attempt \n [ ] Disk I/O (ms) \n [x] Executed \n [x] Order {greyed} \n [x] Outcome \n [x] Recipe {greyed} \n [ ] Recipe version \n [x] Task {greyed} \n [ ] Time (secs) \n \n * For each of the greyed items, attempt to click them. Observe that they do not change. \n \n * For each of the non-greyed items, attempt to click them. Observe that the respective column dynamically appears when checked and disappears when un-checked. ", + "expected_results": "" + }, + "8": { + "action": "Search \n \n * Observe that the search text box background text is \"Search tasks\". \n \n * Set the search text to \"busybox\" and click \"Search\". Observe that only the busybox tasks are listed (about 16). \n \n * Click the \"X\" next to the search text box. Observe that all of the tasks re-appear. \n \n \n", + "expected_results": "" + }, + "9": { + "action": "Column sorts \n \n * Enable all of the columns. \n \n * Observe that by default the \"Order\" column header is in bold, it has a down-arrow icon, and that the table is sorted by this column in ascending order. \n \n * Observe that the columns are in this order, and are sortable only if indicated: \n \n Order {sortable} \n Recipe {sortable} \n Recipe version \n Task {sortable} \n Executed {sortable} \n Outcome {sortable} \n Cache attempt {sortable} \n Time (secs) {sortable} \n CPU usage {sortable} \n Disk I/O (ms) {sortable} ", + "expected_results": "" + }, + "10": { + "action": " Test that each of the sortable columns do sort, ascending and descending \n \n * Observe that each of the column headers have a question mark icon, and that hovering over it provides help text.", + "expected_results": "" + }, + "11": { + "action": "\"Executed\" Filter \n \n * Observe that the \"Executed\" column has the filter icon. Click on it and observe these values, where \"All Tasks\" is the default \n \n (*) All Tasks \n ( ) Executed Tasks \n ( ) Not Executed Tasks \n \n * Click on \"Executed Tasks\" and observe that only rows with the value \"Executed\" are displayed. \n \n * Click on \"Not Executed Tasks\" and observe that only rows with the value \"Not Executed\" are displayed. \n \n * Click on \"All Tasks\" and observe that all rows are displayed. \n \n \n", + "expected_results": "" + }, + "12": { + "action": "\"Outcome\" Filter \n \n * Observe that the \"Outcome\" column has the filter icon. Click on it and observe these values, where \"All Tasks\" is the default \n \n (*) All Tasks \n ( ) Succeeded Tasks \n ( ) Failed Tasks \n ( ) Cached Tasks \n ( ) Prebuilt Tasks \n ( ) Covered Tasks \n ( ) Empty Tasks \n \n * Click on each of the filter selections, and observe that the resulting row \"Outcome\" values match the selection. \n \n * Click on \"All Tasks\" and observe that all rows are displayed. \n \n \n1", + "expected_results": "" + }, + "13": { + "action": "\"Cache attempt\" Filter \n \n * Observe that the \"Cache attempt\" column has the filter icon. Click on it and observe these values, where \"All Tasks\" is the default \n \n (*) All Tasks \n ( ) Tasks with cache attempts \n ( ) Tasks with 'File not in cache' attempts \n ( ) Tasks with 'Failed' cache attempts \n ( ) Tasks with 'Succeeded' cache attempts \n \n * Click on each of the filter selections, and observe that the resulting row \"Outcome\" values match the selection. \n \n Note the with a clean build, only the \"All Tasks\" and \"Tasks with cache attempts\" will return rows. \n \n * Click on \"All Tasks\" and observe that all rows are displayed. \n \n \n1", + "expected_results": "" + }, + "14": { + "action": "Order, Task, Executed, Outcome, Cache attempt links \n \n * Observe that for a given row, the above values are live links that will both take you to the respective task detail page. Click the back button to return. \n\n * Observe that for a given row the values in \"Recipe\" and \"Recipe version\" are live links that will both take you to the respective recipe details page. Click the back button to return \n \n \n1", + "expected_results": "" + }, + "15": { + "action": "Time Page \n \n * \"In Toaster, select the build, and select the \"Time\" link in the left sidebar \n \n * Observe that the default columns are: \n \n \"Recipe\", \"Task\", \"Executed\", \" Outcome\", \"Time (secs)\" \n \n * Observe that the default sort is \"Time (secs)\", in descending order. \n \n * In the \"Edit Columns\" button, turn on all of the columns. \n \n * Observe that the page now matches the \"Tasks\" page, and passes the same tests. \n \n \n1", + "expected_results": "" + }, + "16": { + "action": "CPU Usage Page \n \n * \"In Toaster, select the build, and select the \"CPU Usage\" link in the left sidebar \n \n * Observe that the default columns are: \n \n \"Recipe\", \"Task\", \"Executed\", \"Outcome\", \"CPU Usage\" \n \n * Observe that the default sort is \"CPU Usage\", in descending order. \n \n * In the \"Edit Columns\" button, turn on all of the columns. \n \n * Observe that the page now matches the \"Tasks\" page, and passes the same tests. \n \n \n1", + "expected_results": "" + }, + "17": { + "action": "Disk I/O Page \n \n * \"In Toaster, select the build, and select the \"Disk I/O\" link in the left sidebar \n \n * Observe that the default columns are: \n \n \"Recipe\", \"Task\", \"Executed\", \"Outcome\", \"Disk I/O (ms)\" \n \n * Observe that the default sort is \"Disk I/O (ms)\", in descending order. \n \n * In the \"Edit Columns\" button, turn on all of the columns. \n \n * Observe that the page now matches the \"Tasks\" page, and passes the same tests. ", + "expected_results": "NA" + } + }, + "summary": "Tasks_in_toaster_UI" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.package_detail_in_toaster_UI", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "TOASTER: Test Instructions for \"Package Detail\" page \n \n", + "expected_results": "" + }, + "2": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". ", + "expected_results": "" + }, + "3": { + "action": "In Toaster, select the build, and select the \"Packages\" link in the left sidebar.", + "expected_results": "" + }, + "4": { + "action": "Select a package from the \"Package\" column.", + "expected_results": "" + }, + "5": { + "action": "Breadcrumbs \n * Observe that the 3 breadcrumbs at the top left are: \n : a live link that will take you back to the image dashboard page \n \"Packages\": a live link that will take you back to the Packages page \n \"bash\": the name of the current package (not a link) \n * Test the breadcrumb live links, return to this page ", + "expected_results": "" + }, + "6": { + "action": "General Layout \n * Click on any package \n * Observe that there is no the left-hand box \n * Observe that there is a right-hand box, with information about the package \n * Observe the title is the package name and version, in bold \n * Observe that, if the package is installed in an image, there is a link to the image(s) the package appears in \n * Observe that, if the package is not installed in the image, there are two tab buttons below the title ", + "expected_results": "" + }, + "7": { + "action": "Observe that the tab buttons are: \n Generated files (2) {highlighted} \n Runtime dependencies (4) \n", + "expected_results": "" + }, + "8": { + "action": "Generated files tab \n * Click the \"Generated files\" tab (which should be selected by default) \n * Observe that the number of files in the table matches the number in parenthesis after the \"Generated files\" tab title. \n * Observe that the columns in the table are \"File\" and \"Size\" \n * Observe that the table is sorted by \"File\" in ascending alphabetical order (A to Z). ", + "expected_results": "" + }, + "9": { + "action": "Runtime dependencies tab \n * Click the \"Runtime dependencies\" tab \n * Observe that the number of dependencies in the table matches the number in parenthesis after the \"Runtime dependencies\" tab title. \n * Observe that the columns in the table are: \n \"Package, Version, Size\" \n * Observe that the table is sorted by Package in ascending alphabetical order (A to Z) \n * Observe that the package name values are live links to the respective package details page. ", + "expected_results": "The information icon was eliminated on the columns that where self explanatory. " + }, + "10": { + "action": "Package information box \n * Observe that there is a right-hand box, with information about the package, including in this example the fields: \n \"Size, License, Recipe, Recipe version, Layer, Layer branch, Layer commit\" \n * Observe that each of the field has a question mark icon, and that hovering will provide help text. \n * Observe that none of the values in the right-hand box are blank \n * Observe that the \"Recipe\" value is a live link to the respective recipe detail page. ", + "expected_results": "" + } + }, + "summary": "package_detail_in_toaster_UI" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.recipes:_Sort_the_content_of_the_recipes_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Recipes\" link in the left sidebar. \n\n", + "expected_results": "" + }, + "3": { + "action": "Make sure that by default the \"Recipes\" table is sorted by \"Recipe\" in ascending alphabetical order (A to Z). \n\n", + "expected_results": "" + }, + "4": { + "action": "Sort my \"Recipes\" table by \"Section\" and then navigate away by selecting a recipe(such as click busybox recipe). When you click \"back\" button in web-browser to go back to the \"Recipes\" table it should still be sorted by \"Section\". \n\n", + "expected_results": "" + }, + "5": { + "action": "Make sure all column headings are sortable, except \"Recipe version\", \"Dependencies\", \"Reverse dependencies\" and \"Layer commit\". \n\n", + "expected_results": "" + }, + "6": { + "action": "Sorting and \"Edit columns\" \nIf you use the \"Edit columns\" menu to hide the column with the applied sorting, we revert the sorting to the default sorting (i.e. \"Recipe\"). The default sorting always uses one of the core columns, which cannot be hidden using the \"Edit columns\" menu. \nSort recipes by \"section\" column heading. Then hide \"Section\" column by \"Edit columns\". Make sure that the \"Recipes\" table is sorted by \"Recipe\" in ascending alphabetical order (A to Z). \nNOTE: Bug 5919 is filed against the issue. \n\n", + "expected_results": "" + }, + "7": { + "action": "Sorting and search \nSearching should have no impact on the applied sorting. Any results returned should be sorted by the sorting criteria selected when the search query was submitted. \nSort recipes by \"section\" column heading. Input a string (such as \"lib\") in search box and click search button. Make sure results returned should be sorted by \"section\". \n", + "expected_results": "NA" + } + }, + "summary": "recipes:_Sort_the_content_of_the_recipes_table." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.recipes:_Search_the_content_of_the_recipes_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "recipes: Search the content of the recipes table \n\n", + "expected_results": "" + }, + "2": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "3": { + "action": "In Toaster, select the build, and select the \"Recipes\" link in the left sidebar. \n\n", + "expected_results": "" + }, + "4": { + "action": "Observe the search is made of a text input field and a \"Search\" button in a toolbar above the table. \n\n", + "expected_results": "" + }, + "5": { + "action": "When no search query has been entered, we have placeholder text saying: \"Search recipes\". \n\n", + "expected_results": "" + }, + "6": { + "action": "Input \"lib\" in the text input field. The placeholder text disappears when the first character is typed. Click search button. \n\n", + "expected_results": "" + }, + "7": { + "action": " \n(1) returned results \nThe search string is kept in the text input field. The results returned occur. Click \"Clear search\" icon to clear the search and display all recipes. \n(2) no results returned \nIf your search query returns no results, the page heading changes to \"No recipes found\", and we show you an alert with a search form and an option to show all recipes. Observe \"show all recipes\" button is available. \n\n", + "expected_results": "" + }, + "8": { + "action": "When I run a search, the search happens against the following columns (independently of they being shown or hidden): \n- Recipe \n- Recipe version \n- Recipe file \n- Section \n- License \n- Layer \n- Layer branch \n- Layer commit \n\nInput a string to search for the above 8 column headings separately to make sure that the search happens against the columns. \n\n \n\n", + "expected_results": "" + }, + "9": { + "action": "Search, sorting and \"Edit columns\" \nSearching does not change the state of the table: the same columns remain hidden and the same sorting applied when search results are displayed, but filters are cleared by the search results.\nSearch a string and make sure that the same columns remain hidden and the same sorting applied. Since filter feature of recipes (4296) is obsolete, we don't have to test filter. \n\n", + "expected_results": "" + }, + "10": { + "action": "Search and filters \nThe scope of the filters is the content currently on the table (this means all table pages, not only the one displayed). The scope of the search is always the content of the database.\nSince filter feature of recipes (4296) is obsolete, we don't have to test filter. \n\nIf I run a search query, any filter applied afterwards will filter the content returned by the search query. \n\nIf I run a search query while a filter is applied, the filter is cleared by the results of the search query (i.e. we display the results of the search query and clear the filter applied beforehand).", + "expected_results": "NA" + }, + "11": { + "action": " The same happens if I click the \"Clear search\" icon when a filter is applied to a set of search results (both search results and applied filter are cleared, and the table shows all the tasks). \nSince filter feature of recipes (4296) is obsolete, we don't have to test filter. \n\n", + "expected_results": "NA" + } + }, + "summary": "recipes:_Search_the_content_of_the_recipes_table." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.recipes:_Customise_the_columns_of_the_recipes_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Recipes\" link in the left sidebar. \n\n", + "expected_results": "" + }, + "3": { + "action": "* Observe that the default columns are: \n \"Recipe, Recipe version, Recipe file, Section , License, Layer\" \n \n * Click the \"Edit Columns\" button. \n * Observe that the fields are sorted as follows (with the indicated items greyed) \n [ ] Dependencies \n [x] Layer \n [ ] Layer branch \n [ ] Layer commit \n [x] License \n [x] Recipe {greyed} \n [x] Recipe file \n [x] Recipe version {greyed} \n [ ] Reverse dependencies \n [x] Section \n \n * For each of the greyed items, attempt to click them. Observe that they do not change. \n * For each of the non-greyed items, attempt to click them. Observe that the respective column dynamically appears when checked and disappears when un-checked.\n", + "expected_results": "NA" + } + }, + "summary": "recipes:_Customise_the_columns_of_the_recipes_table." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.recipes:_View_a_table_with_all_the_recipes_included_in_an_image_recipe", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Recipes\" link in the left sidebar. \n\n", + "expected_results": "" + }, + "3": { + "action": "By default, the all recipes table displays the following columns in this order: \n(1) Recipe (2) Recipe version: the target version and revision (3) Dependencies (4)Reverse Dependencies (5) License: the value of the target's LICENSE variable (6) Layer: the name of the layer providing the target \n\n", + "expected_results": "" + }, + "4": { + "action": "In the \"Edit columns\" menu, table columns appear listed alphabetically. \nIn the table itself, the default order of columns is as follows: \n(1) Dependencies (2) Layer (3) Layer branch (4) Layer commit (5) License (6) Recipe (7) Recipe file (8) Reverse dependencies (9) Section (10) Version \n\nThe minimum table is made of the 2 columns that provide the information needed to identify a target: Recipe and Recipe version.", + "expected_results": "NA" + } + }, + "summary": "recipes:_View_a_table_with_all_the_recipes_included_in_an_image_recipe" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.recipes:_View_detailed_information_about_a_recipe。", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Create a default Yocto project (qemux86), and start the Toaster. \n \n $ source poky/oe-init-build-env \n $ source toaster start \n $ bitbake core-image-minimal \n $ http://localhost:8000/ \n \n", + "expected_results": "" + }, + "2": { + "action": "Select the \"core-image-minimal\" build link \n \n", + "expected_results": "" + }, + "3": { + "action": "Select the \"Recipes\" link in the left sidebar \n \nObserve that the recipes are listed in a table, and that each recipe name is a live URL link. \n \n", + "expected_results": "" + }, + "4": { + "action": "Observe that \"Packages\" link. It should have an appended value like \"(4)\". Now click on this link. \n \nObserve: \n a) The number of packages matches the previous number in parenthesis. \n \n b) Each package has a version and a size. The size may be zero. \n \n c) Note that if you hover on a package name, it will reveal a URL of the following form. This link should take you to the corresponding package detail page. \n \n localhost:8000/gui/build//package/ \n \n", + "expected_results": "" + }, + "5": { + "action": "Observe that recipes of \"Build Dependencies\" link has an appended value like \"(0)\". Now click on this link. \n \nObserve: \n a) No dependencies appear, and you get a message of the form: \n \n \"$RECIPE_NAME_VERSION has no build dependencies.\" \n \n", + "expected_results": "" + }, + "6": { + "action": "Observe that \"Reverse build dependencies\" link has an appended value like \"(1)\". Now click on this link. \n \nObserve: \n a) The number of packages matches the previous number in parenthesis. \n \n b) The recipe dependency should be \"packagegroup-core-boot\", \n \n c) There should be a respective version displayed, for example \"1.0-r11\" \n \n d) If you hover on the recipe name, it will reveal a URL of the following form. This link should take you to the corresponding recipe detail page. \n \n localhost:8000/gui/build//recipe/ \n \n", + "expected_results": "" + }, + "7": { + "action": "Click the breadcrumb \"Recipes\" at the top, locate the \"gdbm\" recipe, and select it. \n \n", + "expected_results": "" + }, + "8": { + "action": "Observe that \"Packages\" link. It should have an appended value like \"(0)\". Now click on this link. \n \nObserve: \n a) No packages appear, and you get a message of the form: \n \n \"$PACKAGE_NAME_VERSION does not build any packages.\" \n \n", + "expected_results": "" + }, + "9": { + "action": "Observe that \"Build dependencies\" link. It should have an appended value like \"(2)\". Now click on this link. \n \nObserve: \n a) The number of build dependencies matches the previous number in parenthesis. \n \n b) The recipe dependency should have values like \"gettext-native\" and \"libtool-cross\". \n \n c) There should be a respective versions displayed for each dependency. \n \n d) If you hover on a recipe name, it will reveal a URL of the following form. This link should take you to the corresponding recipe detail page. \n \n localhost:8000/gui/build//recipe/ \n \n1", + "expected_results": "" + }, + "10": { + "action": "Observe that \"Reverse build dependencies\" link. It should have an appended value like \"(0)\". Now click on this link. \n \nObserve: \n a) No reverse dependencies appear, and you get a message of the form: \n \n \"$RECIPE_NAME_VERSION does not build any packages.", + "expected_results": "NA" + } + }, + "summary": "recipes:_View_detailed_information_about_a_recipe。" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.variables:_Search_the_content_of_the_bitbake_variables_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Configuration\" link in the left sidebar. Then click \"BitBake variables\" tab. \n\n", + "expected_results": "" + }, + "3": { + "action": "When no search query has been entered, we have placeholder text saying: \"Search BitBake variables\". \n\n", + "expected_results": "" + }, + "4": { + "action": "Input \"lib\" in text input field. The placeholder text disappears when the first character is typed. Click search button. \n\n", + "expected_results": "" + }, + "5": { + "action": "Observe \"4 variables found\" is showed. (It may be other number.) \n If your search query returns no results, we display an alert with: \n - A h3 heading saying: \"No variables found\" \n - A search box \n - The search query is showed in the text input shield. \n - A link to show all variables. we show the variables table. \n\n", + "expected_results": "" + }, + "6": { + "action": "We provide a \"Clear search\" icon (icon-remove-sign). Click it to clear the search and display all variables. Check that the \"Clear search\" icon cannot be accessed using the tab key. \n\n", + "expected_results": "" + }, + "7": { + "action": "Verify search scope. \nWhen I run a search, the search happens against the following columns (independently of they being shown or hidden): \n- Variable \n- Value \n- Set in file \n- Description \n\n", + "expected_results": "" + }, + "8": { + "action": "Verify \"search, sorting and 'Edit columns'\" \nSearching does not change the state of the table: the same columns remain hidden and the same sorting applied \nwhen search results are displayed, but filters are cleared by the search results. \n\n", + "expected_results": "" + }, + "9": { + "action": "Search and filters \nIf I run a search query, any filter applied afterwards will filter the content returned by the search query. \nIf I run a search query while a filter is applied, the filter is cleared by the results of the search query. \n", + "expected_results": "NA" + } + }, + "summary": "variables:_Search_the_content_of_the_bitbake_variables_table" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.variables:_Sort_the_content_of_the_bitbake_variables_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Configuration\" link in the left sidebar. Then click \"BitBake variables\" tab. \n\n", + "expected_results": "" + }, + "3": { + "action": "By default, the \"variables\" table is sorted by \"Variable\" in ascending alphabetical order (A to Z). \n\n", + "expected_results": "" + }, + "4": { + "action": "Make sure that \"Variable\" column is sortable (Developers have disabled sort function of all other columns to avoid bug 6004) \n\n", + "expected_results": "" + }, + "5": { + "action": "Sorting and search \nSearching should have no impact on the applied sorting. Any results returned should be sorted by the sorting criteria selected when the search query was submitted.", + "expected_results": "NA" + } + }, + "summary": "variables:_Sort_the_content_of_the_bitbake_variables_table." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.builds:_View_a_table_of_all_the_builds_run_for_a_certain_build_directory", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start up toaster and open localhost:8000. ", + "expected_results": "" + }, + "2": { + "action": "You can see 'Latest builds' section lists. - Builds in progress, sorted by inverse start time (last one starting at the top). - 3 latest completed builds, as long as they are less than 24 hours old. If there are no builds in progress or builds completed within the last 24 hours we don't display it: the page shows only the 'All builds' section. ", + "expected_results": "" + }, + "3": { + "action": "You can see the following column headings. You can see the their description in https://bugzilla.yoctoproject.org/attachment.cgi?id=1617. outcome, recipe, machine, started on, completed on, failed tasks, errors, warnings, time, image files, project", + "expected_results": "NA" + } + }, + "summary": "builds:_View_a_table_of_all_the_builds_run_for_a_certain_build_directory" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.builds:_Customise_the_columns_of_the_builds_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start up toaster.", + "expected_results": "" + }, + "2": { + "action": "Create 2 builds, such as \"bitbake core-image-minimal\" and \"bitbake core-image-sato\". Wait for successful builds and then run: xdg-open http://localhost:8000/", + "expected_results": "" + }, + "3": { + "action": "Enter \"All build\" table in web browser.", + "expected_results": "" + }, + "4": { + "action": "Select a few item in \"Edit columns\" to show or hide them in all builds.", + "expected_results": "Unchecked items changed to checked should immediately appear in the table. Checked items changed to unchecked should immediately disappear from the table. If you uncheck the column with the applied sorting, when you close the \"Edit columns\" menu the applied sorting should revert to the table default sorting. Bug 5919 is filed for the function." + } + }, + "summary": "builds:_Customise_the_columns_of_the_builds_table" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.packages:_View_a_table_with_all_the_packages_built_for_an_image_recipe", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". ", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Packages\" link in the left sidebar. ", + "expected_results": "" + }, + "3": { + "action": "By default, the built packages table displays the following columns in this order: Package, Package version, Size ", + "expected_results": "" + }, + "4": { + "action": "Apart from the columns shown by default, the following additional columns are also available to users via the \"Edit columns\" menu: Layer, Layer branch, Layer commit, License, Recipe version ", + "expected_results": "" + }, + "5": { + "action": "Enable these columns and observe that table columns appear listed alphabetically in the \"Edit columns\" menu (1)Package (2)Package version (3)Size (4)License (5)Recipe (6)Recipe version (7)Layer (8)Layer branch (9)Layer commit ", + "expected_results": "" + }, + "6": { + "action": "The minimum table is made of the 2 columns that provide the information needed to identify a package: Package and Package version. Their corresponding checkboxes in the \"Edit columns\" menu appear always selected and are in an inactive state. ", + "expected_results": "NA" + } + }, + "summary": "packages:_View_a_table_with_all_the_packages_built_for_an_image_recipe" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.packages:_Sort_the_content_of_the_packages_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". ", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Packages\" link in the left sidebar. ", + "expected_results": "" + }, + "3": { + "action": "Observe that by default the \"built packages\" table is sorted by \"Package\" in ascending alphabetical order (A to Z). ", + "expected_results": "" + }, + "4": { + "action": "Click \"Size\" column heading to sort my \"built packages\" table by \"Size\". Then navigate away by selecting a package and you can see the package page. After click \"go back\" button in browser to return to the \"built packages\" table it should still be sorted by \"Size\". ", + "expected_results": "" + }, + "5": { + "action": "Observe that all except \"Package version\", \"Recipe version\", \"Layer commit\" are sortable. ", + "expected_results": "" + }, + "6": { + "action": "If you use the \"Edit columns\" menu to hide the column with the applied sorting, we revert the sorting to the default sorting (i.e. \"Package\"). The default sorting always uses one of the core columns, which cannot be hidden using the \"Edit columns\" menu. Bug 5919 is filed for the issue. ", + "expected_results": "" + }, + "7": { + "action": "Searching should have no impact on the applied sorting. Any results returned should be sorted by the sorting criteria selected when the search query was submitted. Sort packages by size and search a string. Observe that results returned should be sorted by size. ", + "expected_results": "" + }, + "8": { + "action": "In Toaster, select the build, and select the \"core-image*\" link in the left sidebar. Observe that by default the \"built packages\" table is sorted by \"Package\" in ascending alphabetical order (A to Z). ", + "expected_results": "" + }, + "9": { + "action": "If choose to sort my \"included packages\" table by \"Size\" and then navigate away by selecting a package, when I go back to the \"included packages\" table it should still be sorted by \"Size\". ", + "expected_results": "" + }, + "10": { + "action": "Enable all columns by \"Edit columns\". All except \"Package version\", \"Recipe version\", \"Dependencies\", \"Reverse dependencies\", \"Layer commit\", should be sortable. ", + "expected_results": "" + }, + "11": { + "action": "If you use the \"Edit columns\" menu to hide the column with the applied sorting, we revert the sorting to the default sorting (i.e. \"Package\"). The default sorting always uses one of the core columns, which cannot be hidden using the \"Edit columns\" menu. Bug 5919 is filed for the issue. ", + "expected_results": "" + }, + "12": { + "action": "Searching should have no impact on the applied sorting. Any results returned should be sorted by the sorting criteria selected when the search query was submitted. Sort packages by size and search a string. Observe that results returned should be sorted by size.", + "expected_results": "NA" + } + }, + "summary": "packages:_Sort_the_content_of_the_packages_table" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.packages:_Customise_the_columns_of_the_packages_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". ", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Packages\" link in the left sidebar. ", + "expected_results": "" + }, + "3": { + "action": "Observe that by default the \"built packages\" table is sorted by \"Package\" in ascending alphabetical order (A to Z). ", + "expected_results": "" + }, + "4": { + "action": "Select 1 column in \"Edit column\" to show the column. ", + "expected_results": "" + }, + "5": { + "action": "Deselect 1 column in \"Edit column\" to hide 1 column by \"Edit columns\".", + "expected_results": "NA" + } + }, + "summary": "packages:_Customise_the_columns_of_the_packages_table" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.packages:_Search_the_content_of_the_packages_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". ", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Packages\" link in the left sidebar. ", + "expected_results": "" + }, + "3": { + "action": "Observe that by default the \"built packages\" table is sorted by \"Package\" in ascending alphabetical order (A to Z). ", + "expected_results": "" + }, + "4": { + "action": "When no search query has been entered, we have placeholder text saying: \"Search packages built\". The placeholder text disappears when the first character is typed. ", + "expected_results": "" + }, + "5": { + "action": "When a search query has been submitted and results returned: ▪ We keep the search string in the text input field. ▪ We provide a \"Clear search\" icon (icon-remove-sign). Click it to clear the search and display all packages. ▪ We change the page heading to indicate the number of results returned by the search query. ", + "expected_results": "" + }, + "6": { + "action": "If your search query returns no results, the page heading changes to \"No packages found\", and we show you an alert with a search form and an option to show all packages. ", + "expected_results": "" + }, + "7": { + "action": "Searching does not change the state of the table: the same columns remain hidden and the same sorting applied. ", + "expected_results": "" + }, + "8": { + "action": "When I run a search, the search happens against the following columns (independently of they being shown or hidden): - Package - Package version - License - Recipe - Recipe version - Layer - Layer branch - Layer commit ", + "expected_results": "" + }, + "9": { + "action": "Hide all columns except \"Package\" and \"Package version\". Search a string which is included in other hidden columns, not the 2 columns. See if returned results occur. ", + "expected_results": "" + }, + "10": { + "action": "In Toaster, select the build, and select the \"core-image*\" link in the left sidebar. Observe that by default the \"included packages\" table is sorted by \"Package\" in ascending alphabetical order (A to Z). Rerun tests according to step 4~9.", + "expected_results": "NA" + } + }, + "summary": "packages:_Search_the_content_of_the_packages_table" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.View_detailed_information_about_a_layer", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n\n", + "expected_results": "" + }, + "2": { + "action": "Make sure that layer information is shown in: \n* recipes table \n All builds-> core-image-minimal-> recipes \n Select \"Layer\", \"Layer branch\", \"Layer commit\" in Edit columns and observe the 3 columns are showed. Note that the \"Layer branch\" column can be empty. \n\n* recipe details \n All builds-> core-image-minimal-> recipes \n Click a recipe and you can see \"Layer\", \"Layer branch\", \"Layer commit\", \"Recipe details\" information. Note that \"Layer branch\" is not required. If there is no layer branch, you should not see the \"Layer branch\" item on the list.", + "expected_results": "NA" + }, + "3": { + "action": "built packages table \n All builds-> core-image-minimal-> packages \n Select \"Layer\", \"Layer branch\", \"Layer commit\" in Edit columns and observer the 3 columns is showed. Note that the \"Layer branch\" column can be empty. \n\n* built package details \n All builds-> core-image-minimal-> packages \n Click a package and you can see \"Layer\", \"Layer branch\", \"Layer commit\" in package information. Note that \"Layer branch\" is not required. If there is no layer branch, you should not see the \"Layer branch\" item on the list. \n\n* image information \n All builds-> core-image-minimal-> core-image-minimal(images) \n Select \"Layer\", \"Layer branch\", \"Layer commit\" in Edit columns and observer the 3 columns is showed.", + "expected_results": "NA" + }, + "4": { + "action": "Note that the \"Layer branch\" column can be empty. \n\n* installed package details \n All builds-> core-image-minimal-> core-image-minimal(images) \n Click a package and you can see layer information in package information. Note that \"Layer branch\" is not required. If there is no layer branch, you should not see the \"Layer branch\" item on the list. \n\n* configuration \n All builds-> core-image-minimal-> Configuration \n You can see \"Layer\", \"Layer branch\", \"Layer commit\" in configuration summary. Note that the \"Layer branch\" column can be empty. \n\n* build dashboard \n All builds-> core-image-minimal \n You can see \"Layers\" in build summary. ", + "expected_results": "NA" + } + }, + "summary": "View_detailed_information_about_a_layer" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.Select_the_number_of_table_rows_displayed_per_page", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". ", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Packages\" link in the left sidebar. ", + "expected_results": "" + }, + "3": { + "action": "Users can select the number of rows they want to see in a table using the \"Show rows\" dropdown menu, which displays above and below each table. The options of the \"Show rows\" dropdown are: 10, 25, 50, 100, 150. ", + "expected_results": "" + }, + "4": { + "action": "The last selected option from the \"Show rows\" menu should be remembered: * Select one option, for example 10 * Click on a package name to navigate away from the built packages table * Click on the \"Packages\" link in the breadcrumb at the top of the page to go back to the packages table Note that 25 is still selected in the \"Show rows\" menu. ", + "expected_results": "" + }, + "5": { + "action": "Observe that the pagination widget is made of: - A \"Previous\" button - A \"Next\" button - A maximum of 5 page buttons. ", + "expected_results": "" + }, + "6": { + "action": "See the pagination function of \"Tasks\", \"Recipes\" links according to steps 3~4.", + "expected_results": "Expected result for step 4: This widget has no previous or next button if testing in toaster 2.2. see Bug 9831" + } + }, + "summary": "Select_the_number_of_table_rows_displayed_per_page" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.View_detailed_configuration_information_for_a_build", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". ", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Configuration\" link in the left sidebar. ", + "expected_results": "" + }, + "3": { + "action": "Observe that the configuration page has 2 tabs: - Summary - BitBake variables The Summary tab is the default tab. ", + "expected_results": "" + }, + "4": { + "action": "The following content is included in summary tab. (1) Build configuration (2) Layers (Layer, Layer branch - if any, Layer commit) ", + "expected_results": "" + }, + "5": { + "action": "Observe that \"BitBake variables\" tab includes \"Variable\", \"Value\", \" Set in file\", \"Description\" columns. ", + "expected_results": "" + }, + "6": { + "action": "Click filter button of \"Set in file\" column. Select \"Local configuration variables\" and click \"Apply\" button to see if filter function works well. ", + "expected_results": "" + }, + "7": { + "action": "In the \"Edit columns\" menu, table columns appear listed alphabetically: Description, Set in file, Value, Variable ", + "expected_results": "" + }, + "8": { + "action": "The minimum table is made of the \"Variable\" and \"Value\" columns. ", + "expected_results": "" + }, + "9": { + "action": "Click a variable and a \"History of ${variable}\" dialog will occur. The modal dialog shows the variable value followed by the history table, which has the following columns: - Order: indicates the sequence in which the files set the variable - Configuration file: the location in disk of the file that set the variable - Operation: the value of the operation field as stored in the database. - Line number: the line number where the operation is performed in the configuration file. For such variables, whose value is an empty string, the Value cell in the variables table isempty, which is probably the right thing. In the modal, instead of the variable value, we show an alert (with the class .alert-info) saying: \"The value of is an empty string\" ", + "expected_results": "" + }, + "10": { + "action": "Click arrow links in description tab to see linking variables to the Yocto Project reference manual.", + "expected_results": "NA" + } + }, + "summary": "View_detailed_configuration_information_for_a_build" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.variables:_Customise_the_columns_of_the_bitbake_variables_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". ", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Configuration\" link in the left sidebar. Then click \"BitBake variables\" tab. ", + "expected_results": "" + }, + "3": { + "action": "Show or hide columns by select or deselect options of \"Edit columns\".", + "expected_results": "NA" + } + }, + "summary": "variables:_Customise_the_columns_of_the_bitbake_variables_table" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.variables:_Filter_the_content_of_the_bitbake_variables_table", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"Configuration\" link in the left sidebar. Then click \"BitBake variables\" tab. \n\n", + "expected_results": "" + }, + "3": { + "action": "Observe \"Set in file\" and \"Description\" columns have filters. \n\n", + "expected_results": "" + }, + "4": { + "action": "Filters are mutually exclusive. Only one column filter can be applied to a table at any given time. \n\n", + "expected_results": "" + }, + "5": { + "action": "Filters are overridden by search. \nThe scope of the filters is the content currently on the table. \nThe scope of the search is always the full content of the database. \nSo: \n- if I run a search query, any filter applied afterwards will filter the content returned by the search query. \nSearch a string and apply a filter. Observe it would filter the content returned by the search query. \n\n- if I run a search query while a filter is applied, the filter is overridden by the results of the search query. \nApply a filter and search a string. Observe that the previous filtered result is overridden by the search. ", + "expected_results": "NA" + } + }, + "summary": "variables:_Filter_the_content_of_the_bitbake_variables_table" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.View_and_navigate_the_full_directory_structure_of_built_images", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build, and select the \"core-image-minimal\" link in the left sidebar. \n\n", + "expected_results": "" + }, + "3": { + "action": "Observe image information page has 2 tabs: \n- Packages included: this tab shows a table with all the packages installed in the image. The tab label includes the total number of packages listed in the table and their size. \n- Directory structure: this tab shows all the files included in the image. \n\n", + "expected_results": "" + }, + "4": { + "action": "By default, the included packages table displays the following columns in this order: \nPackage, Package version, Size, Dependencies \n\n", + "expected_results": "" + }, + "5": { + "action": "Apart from the columns shown by default, the following additional columns are also available to users via the \"Edit columns\" menu: \nLayer, Layer branch, Layer commit, License, Recipe, Recipe version. \n\n", + "expected_results": "" + }, + "6": { + "action": "The minimum table is made of the 2 columns that provide the information needed to identify a package: Package and Package version. \n\n", + "expected_results": "" + }, + "7": { + "action": "By default, the directory structure table shows the top level directories and files in the file system.\nThe table includes the following columns: \nDirectory/File, Symbolic link to, Source package, Size, Permissions, Owner, Group \nOpen some directories and see files. ", + "expected_results": "NA" + } + }, + "summary": "View_and_navigate_the_full_directory_structure_of_built_images" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.View_a_summary_of_all_the_information_available_for_a_build", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and build \"bitbake core-image-minimal\". \n \n", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select the build. \n\n", + "expected_results": "" + }, + "3": { + "action": "A 'Build dashboard' page is showed. \nThe 'Build dashboard' page has two main states: \n(1) Success state: when the build completes successfully. In the success state, if the build target(s) include an image recipe, the page displays an image content module, and the left navigation has an \"Images\" section at the top. \n(2) Fail state: when the build fails (shown in this page). In the fail state, the page always displays an errors content module, and the left navigation does not have an \"Images\" section at the top. \n\n", + "expected_results": "" + }, + "4": { + "action": "Observe that the page provides access to all information available for the selected build. \n(1) Images \n(2) Build: this group provides links to the following pages: \nConfiguration, Tasks, Recipes, Packages \n(3) Performance: this group provides links to the following pages: \nTime, CPU usage, Disk I/O \n\n", + "expected_results": "" + }, + "5": { + "action": "The page heading is made of the build target(s) and the machine, such as \"core-image-minimal qemux86\". If the build has more than one target, they show in ascending alphabetical order (A to Z) both in the page heading and in the \"Images\" section of the left navigation. If the build was successful, there is an image content module for each target that is an image recipe. The modules also show in ascending alphabetical order by target name. \n\n", + "expected_results": "" + }, + "6": { + "action": "Packages included, total package size, license manifest, image files are included in the images section. \n\n", + "expected_results": "" + }, + "7": { + "action": "The information of Machine, Distro, Layers is included in configuration content module of \"Build summary\" section. \nThe information of \"Total number of task\", \"Tasks executed\", \" Tasks not executed\", \"Reuse\" is included in the tasks content module. \nThe information of \"Recipes built\" and \"Packages built\" is included in the \"Recipes&Packages\" content module. ", + "expected_results": "NA" + } + }, + "summary": "View_a_summary_of_all_the_information_available_for_a_build" + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.Display_the_content_of_error_messages_and_warnings", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and create a successful build and a failed build. You can force a build to terminate by ctrl+c. ", + "expected_results": "" + }, + "2": { + "action": "Observe that the number of errors and warnings thrown by a build shows in both 'All builds' page and the 'Latest builds' section. ", + "expected_results": "" + }, + "3": { + "action": "Observe that the number and content of errors and warnings thrown by a build shows in the 'Build dashboard' page. ", + "expected_results": "" + }, + "4": { + "action": "Click warning or error links to see warning and error details. ", + "expected_results": "NA" + } + }, + "summary": "Display_the_content_of_error_messages_and_warnings." + } + }, + { + "test": { + "@alias": "toaster-unmanaged-mode.toaster-unmanaged.Build_summary_information_fully_implemented", + "author": [ + { + "email": "Yuan.Sun2@windriver.com", + "name": "Yuan.Sun2@windriver.com" + } + ], + "execution": { + "1": { + "action": "Start with a default Yocto project (qemux86), start the Toaster, and create 4 builds. \na) a successful build with images (bitbake core-image-minimal) \nb) a successful build without images (bitbake mtools-native) \nc) a failed build with errors and warnings (run \"bitbake core-image-sato\", then press control+c to terminate the build)", + "expected_results": "" + }, + "2": { + "action": "In Toaster, select a core-image-minimal build.", + "expected_results": "" + }, + "3": { + "action": "Observe that there is a 'Build dashboard' page captured by Toaster. The page does not exist for builds in progress, only for finished builds. \nThe 'Build dashboard' page is made of: \na) Breadcrumb \nb) Navigation \n IMAGES: core-image-minimal \n BUILD: \n Configuration \n Tasks \n Recipes \n Packages \n PERFORMANCE: \n Time \n CPU usage \n Disk I/O \nc) Page heading (core-image-minimal qemux86) \nd) Section heading (Images, Build summary) \ne) Build status notification (Completed on xx/xx/xx... Build time:xx:xx:xx)", + "expected_results": "" + }, + "4": { + "action": "Observe \"images\" section is made of the following \n.\na) Heading: core-image-minimal, which links to the \"Packages included\" tab of the image information page \nb) Number of packages installed: (packages included xx), which is a link to the \"Packages included\" tab of the image information page \nc) Total installed package size: xxMB \nd) License manifest (which is a link to the \"Packages included\" tab of the information page with the following columns showing: \"Package\", \"Package version\", \"License\" and \"Recipe\". We have bug 6079 open for this). Next to the license manifest is the path to the directory where you can find the license manifest file. \n \ne) Image files (rootfs file names and rootfs file sizes)", + "expected_results": "" + }, + "5": { + "action": "Observe \"Build summary\" section is made of the following. \na) Configuration (which is a link to the configuration page): \n Machine \n Distro \n Layers (sorted in alphabetical order) \nb) Tasks (which is a link to the tasks page) \n Total number of tasks (which is a link to the tasks page) \n Tasks executed (which is a link to the tasks page with the tasks executed filter applied) \n Tasks not executed (which is a link to the tasks pages with the tasks not executed filter applied)\n Reuse \nc) Note that \"Total number of tasks\" should equal number of \"Tasks executed\" + number of \"Tasks not executed\" \nd) Recipes (which is a link to the recipes page) & Packages (which is a link to the packages built page) ", + "expected_results": "" + }, + "6": { + "action": " Number of recipes built (which is a link to the recipes page) \n \n Number of packages built (which is a link to the packages built page)", + "expected_results": "" + }, + "7": { + "action": "Return to localhost:8000 and select a successful build without images (mtools-native) \n.\nObserve the build dashboard for a successful build of a target that is not an image recipe. There is no image content module, and no \"Images\" section in the left navigation.", + "expected_results": "" + }, + "8": { + "action": "Return to localhost:8000 and select the failed build (core-image-sato). Observe the build dashboard for the failed build. \n \na) the errors content module: \nThis module exists for those builds that throw error(s). It appears immediately below the build status notification. \nThe module has 2 states: \n▪ Expanded (shows number of errors and error content) \n▪ Collapsed (shows only the number of errors) \nBy default, the errors module is in the expanded state. \nErrors content modules include the following information: \n(1.1) A heading, which indicates the number of errors thrown by the build, and toggles the module between its 2 states on click. ", + "expected_results": "NA" + }, + "9": { + "action": "Transitions between states should use a slide up / slide down animation. \n(1.2) Error(s) content \n\nb) the warning content module: \nThis module exists for those builds that throw warning(s). \nIt is the last content module shown on the build dashboard. \nThe module has 2 states: \n▪ Expanded (shows number of warnings and warning content) \n▪ Collapsed (shows only the number of warnings) \nBy default, the warning module is in the collapsed state. Warnings content modules include the following information: \n(2.1) A heading, which indicates the number of warnings thrown by the build, and toggles the module between its 2 \nstates on click. Transitions between states should use a slide up / slide down animation. \n(2.2) Warning(s) content ", + "expected_results": "NA" + } + }, + "summary": "Build_summary_information_fully_implemented" + } + } +]
\ No newline at end of file |