I think Alex figured out another way of doing this? If so, probably close this bug?

Hi Jessica,
The test we intend to do is using a UI recognition tool, but I would like to have also a more confident platform using JUnit like I specified, so I would like to ask you to leave this one open for the current time.

Thanks,
Alex.

Alex,

I'm assigning this to you since I think some intern is working on this?

Jessica,
I am making this an umbrella bug since more work may be done on this.
THe two areas that I am thinking is:
1. Have UI testing and validating as much as possible of the weekly tests (work in progress): https://bugzilla.yoctoproject.org/show_bug.cgi?id=5417
2. Have some kind of a plugin that mimics what the user is doing from the UI (Ioana tried something but didn't get to any result so far).

Just adding few comments here.
The initial idea of the testing framework is the following, and we may continue the discussions based on it:

WHAT WE TEST RIGHT NOW?
- we test basic functionalities, like building C apps and delpoy
- create new BB commander projects
- create new yocto-bsp layers
- test the TOOLS (powertop, systemtap, etc)

WHAT WE WANT TO ACHIEVE?
- Yocto supports many arches, like ARM, PPC, x86 (and x86_64), MIPS. To test all the toolchains and their integration with Eclipse, a plugin may be created that mimics the UI interactions from the Developer and Eclipse. This is the coverage goal. The plugin should know what toolchains are installed on the host (from a config file), and should be able to interact with the current eclipse-plugin and create various types of projects (GTK, Hello world), compile them, and even deploy and debug them on target (QEMU or real HW).
- Another objective would be to cover the other eclipse-plugin functionalities like creating the BB commander projects, using the Yocto-bsp plugin and using the tools

Obsoleted by bug 5417.

Verified according to the previous comment.

closing