Re: [mdt-papyrus.dev] Questions about JUnit test execution

[LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx>]

Hi Christian,

 

Ø  who else on the team develops and tests on Mac and what is your experience compared to other platforms?  

 

We only have Windows and Linux developers, so currently, nobody’s testing Papyrus on Mac (Except yourself)

 

Regarding the GMFDiag Commands tests, I just noticed that a few test features are not included to the build (The features exist and reference the tests plug-ins, but they are not referenced by the main test feature). That’s why a few test fragments were never executed (And because we use reflexive code invocation for test fragments, this didn’t break the build; they were just ignored).

I’m fixing that immediately.

 

Regards,
Camille

__________________________

Camille Letavernier

+33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx

CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE)

Papyrus : http://www.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : dimanche 23 février 2014 22:59
À : Papyrus Project list
Objet : [mdt-papyrus.dev] Questions about JUnit test execution

 

Hi, Team,

 

When I run the "Papyrus ALL Tests" launch configuration locally on my Mac, I get more test failures (and a few errors) than what the nightly builds on Hudson (at Eclipse) report, for the same Git commit on master.  Also, locally I am running more test cases than the build:  my test execution includes the oep.infra.gmfdiag.commands.tests suite, but the test execution on Hudson does not.

 

So, two questions:

 

• who else on the team develops and tests on Mac and what is your experience compared to other platforms?  I suspect that the additional failures I see are caused by stuff that doesn't work on Mac.  Other issues that I have seen on Mac, that I could imagine aren't a problem on other platforms, include:

• a second context (right-moust-click) menu always appears in the diagram editors after dismissing the first menu (either by clicking away or invoking some menu action).  The second menu has a small subset of the first menu, plus a few items that aren't in the first menu
• drag-and-drop elements from Model Explorer onto table editors doesn't work at all on Mac

• why would the oep.infra.gmfdiag.commands.tests suite not be included in JUnit execution on Hudson?  I added this test fragment recently on master and I think I integrated it into all of the necessary places (the tests feature, the master oep.tests.AllTests suite, etc.)

 

Thanks for your help,

 

Christian