| Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Re: Hudson with @Ignore |
|
Hi, That would be a new job. But we won’t configure a new Buckminster-based Job, as we should be moving to Tycho/CBI soon, and we’d need to reconfigure it just
a few weeks later. We may even need to request a dedicated Hudson Instance (HIPP), if a new branching workflow is to be adopted (And many jobs need to be created). So, for now, it is recommended to use these annotations (Instead of @Ignore), but the Jobs will
come later. The details of the future Hudson configuration for Papyrus are not known yet, so it is too early to request a new Job. We definitely need 2 (or more) separate test jobs, to clearly separate regressions from other failures. Regards, __________________________ 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 If a new or updated Hudson plug-in is required to improve the presentation of test results, then that requires (I think) a request (in the form of a bugzilla) to the Foundation's Webmaster team. Otherwise, if it's just a plug-in configuration parameter on the build job, then any committer with permission to modify our Hudson project can do that. Cheers, Christian On Mar 24, 2014, at 10:59 AM, GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx> wrote:
Question: do we know whom is to be contacted to satisfy our need of test job configuration? De : LETAVERNIER
Camille Hi Benoit, hi all, To properly visualize the test results, you can import the raw XML data into the Eclipse/JUnit view (Build artifacts -> Papyrus-TestResults.zip). The ignored
tests will (should?) be properly displayed. AFAIK, this information is not displayed on Hudson. Also, to improve the clarity of test results, we have recently implemented new JUnit annotation: 430023: [Papyrus Tests] Papyrus shall propose different levels of testing, to allow test-driven development They can either fail or ignore the test, depending on the job configuration (However, there currently isn’t any way to “configure” the test job for these annotations,
so they are currently ignored). The idea would be to replace all @Ignore annotations with more specific and configurable annotations, to have more accurate results. In this case, the annotation would be @InvalidTest (Which is ignored in the default test configuration).
See Bug 430023 for more details on these annotations. Regards, __________________________ 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 MAGGI Benoit Intérimaire Hi everyone, I was wondering why some tests didn’t failed for this bug: It’s a simple copy/paste launching an exception only for linux/mac platform. I was pretty confident with this Hudson report : <image001.jpg> But when I looked in the TestCopyGraphicallyPasteBlock class,
I found an @Ignore on each test. @Ignore("The test implementation is not compatible with Eclipse 4.2") Here are my questions : - Is
there a way to show skipped tests in yellow in Hudson/Jenkins ? (I tried to update Ant to the last version but it’s not working) - If
not, maybe it’s best to comment tests instead of @Ignore to avoid misleading information ? Regards Benoit Maggi _______________________________________________ |