From: Armin Kuster <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 13/20] OEQA: eclipse support was dropped in warrior
Date: Mon, 11 Nov 2019 20:33:32 -0800 [thread overview]
Message-ID: <dd10643070b0b467e486ff28f516590f672f1bdb.1573532188.git.akuster808@gmail.com> (raw)
In-Reply-To: <cover.1573532188.git.akuster808@gmail.com>
remove test
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
meta/lib/oeqa/manual/eclipse-plugin.json | 322 -------------------------------
1 file changed, 322 deletions(-)
delete mode 100644 meta/lib/oeqa/manual/eclipse-plugin.json
diff --git a/meta/lib/oeqa/manual/eclipse-plugin.json b/meta/lib/oeqa/manual/eclipse-plugin.json
deleted file mode 100644
index 9869150..0000000
--- a/meta/lib/oeqa/manual/eclipse-plugin.json
+++ /dev/null
@@ -1,322 +0,0 @@
-[
- {
- "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 autobuilder.yoctoproject.org/pub/releases//machines/qemu/qemux86/qemu (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 autobuilder.yoctoproject.org/pub/releases//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 enviroment.(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 enviroment.(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 http://autobuilder.yoctoproject.org/pub/releases/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"
- }
- }
-]
\ No newline at end of file
--
2.7.4
next prev parent reply other threads:[~2019-11-12 4:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 4:33 [PATCH 00/20] QA updates Armin Kuster
2019-11-12 4:33 ` [PATCH 01/20] OEQA: Add a check for MACHINE Armin Kuster
2019-11-12 4:33 ` [PATCH 02/20] OEQA: Add qemu checks Armin Kuster
2019-11-12 4:33 ` [PATCH 03/20] OEQA: Centrilize the base LTP routines Armin Kuster
2019-11-12 4:33 ` [PATCH 04/20] OEQA: update ltp runtimes to use new structure Armin Kuster
2019-11-14 1:53 ` Mittal, Anuj
2019-11-14 3:42 ` akuster808
2019-11-12 4:33 ` [PATCH 05/20] OEQA/runtime: Add ltp stress test Armin Kuster
2019-11-12 4:33 ` [PATCH 06/20] OEQA/manual: remove crash " Armin Kuster
2019-11-12 4:33 ` [PATCH 07/20] manual qa: drop ltpstress test Armin Kuster
2019-11-12 4:33 ` [PATCH 08/20] manual qa/bsp-qemu: remove rpm tests already done in runtime Armin Kuster
2019-11-12 4:33 ` [PATCH 09/20] manual qa/bsp-qemu: remove KVM enabled which is already done in selftest runqemu Armin Kuster
2019-11-12 4:33 ` [PATCH 10/20] manual/bsp-qemu: drop xserver test done at runtime Armin Kuster
2019-11-12 4:33 ` [PATCH 11/20] manual/bsp-qemu: remove only_one_connmand_in_background " Armin Kuster
2019-11-12 4:33 ` [PATCH 12/20] OEQA: remove postinit test done w/selftest runtime Armin Kuster
2019-11-12 4:33 ` Armin Kuster [this message]
2019-11-12 4:33 ` [PATCH 14/20] OEQA: move manual bash test to runtime Armin Kuster
2019-11-13 1:33 ` Mittal, Anuj
2019-11-13 1:49 ` akuster808
2019-11-12 4:33 ` [PATCH 15/20] OEQA: remove manual bash test Armin Kuster
2019-11-12 4:33 ` [PATCH 16/20] OEQA: remove manual useradd test Armin Kuster
2019-11-12 4:33 ` [PATCH 17/20] OEQA: move list-packageconfig-flags tests from manual to self Armin Kuster
2019-11-12 4:33 ` [PATCH 18/20] OEQA: remove manual PACKAGECONFIG_FLAGS tests Armin Kuster
2019-11-12 4:33 ` [PATCH 19/20] OEQA: add crosstab selftest Armin Kuster
2019-11-12 4:33 ` [PATCH 20/20] OEQA: remove crosstab test from manual Armin Kuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd10643070b0b467e486ff28f516590f672f1bdb.1573532188.git.akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.