We need to integrate eclipse plugin testing into AB/buildbot, Current work at, http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=vhangan/eclipse-framework
Hi Anibal, Can you add a bug for the Fedora only testing issue?
Re-assigning to Edwin.
This makes sense for a Linux only plugin, but since it depends on pygobject and GNOME-python it won't work on the Windows and Mac clients we are trying to add. It's great that it uses python for the tests, but requiring GNOME is a deal breaker for the larger picture. Hopefully, in the not too distant future, the Eclipse EASE project will allow us to return to using python for the test scripts (http://www.eclipse.org/ease/). Many Eclipse plugins use SWTBot for UI testing (http://www.eclipse.org/swtbot/). The newest player in the Eclipse testing world is RCPTT (http://www.eclipse.org/rcptt/), but the C/C++ Development Tools (CDT) project has found debugging of RCPTT tests themselves to be difficult. Since most of what we are providing is CDT related, for now it makes the most sense to stick with SWTBot ("swat-bot"). Very preliminary testing using SWTBot is available in the following branch: http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-contrib/log/?h=timo/neon-master-ui-tests-wip For now, the tests can be run in the IDE, semi-automatically (the IDE has to be launched manually, but the test suite runs automatically). Using Xvnc and metacity the tests can be run fully automatically and "headless", and many Eclipse projects do this on Hudson CI (http://wiki.eclipse.org/SWTBot/Automate_test_execution). The test cases themselves are (unfortunately) written in Java and require knowledge of the underlying SWT widgets, but the learning curve is not too steep. SWTBot provides a Recorder/Generator that can help with creating new test cases (http://wiki.eclipse.org/SWTBot/Generator), although it is limited to the UI thread in which it is launched. This means, for instance, that dialog boxes become difficult to generate test cases for. It is possible that the RCPTT UI tools may be able to help bridge the gap (helping to capture events from multiple UI threads), but this has not yet been tested. The test suite results from SWTBot can be output to XUnit format and should therefore be "easy" to consume into a larger scoped QA report.
This enhancement wont be ready for M3, and M4 is just for bugs. Moving to 2.3M1.
As in bug 9140, Benjamin needs to figure out current status.
RCPTT (Rich Client Platform Testing Tool) is Java/Eclipse based and therefore does not care about the distro or even platform (Mac/Windows/Linux). BZ#9597 The current in-process implementation uses a Docker container to run the tests. The container can be run on the AB, but the launcher script for the Docker container can be run bare-metal/natively as well. It does require some setup for QEMU in the background.
The direction here is to collaborate with Tim on the RCPTT
Reassigning back to José so he can choose someone from QA To work on this.
Assign it to Humberto as he is teh current owner of QA of Eclipse Plugin
Still waiting for 9597 to be done. Moving to M3.
Depends on a different bug and it doesn't look like it will be ready on time.
Moving to 2.5, due to limited resources.
Returning version to 2.1
eclipse has been dropped.
closing