| [mdt-papyrus.dev] Test Jobs |
|
Hi all, I’ve pushed a few new Annotations for the JUnit tests, as well as an improved Test Runner: 430023: [Papyrus Tests] Papyrus shall propose different levels of testing, to allow test-driven development https://bugs.eclipse.org/bugs/show_bug.cgi?id=430023 They can be used to have more control over which tests should be executed. The idea is to Ignore all tests which are known to be failing (For whatever reason), to finally have a Green build, so that the actual regressions are not lost between
tens of failing tests. Unlike the JUnit @Ignore, these annotations are excluded only under certain conditions (e.g. depending on the Test Suite configuration or launch config...). Thus, we can have different test jobs for different purposes: -
A non-regression test job, which excludes the tests which have been failing for months (And cannot be fixed easily, e.g. because they test something which is not yet implemented) -
A full-test job, which includes everything -
A light test job, which runs a small subset of high level tests -
... Currently, some Annotations are available, and the Job is running using a default configuration (Which ignores all tests annotated by these new annotations). We’ll add new test jobs (Full, light, etc.) in the near future. See the Bugzilla task for more details, and information regarding how to use the annotations. As a result, Papyrus-trunk-extra-nightly-tests is now green (Or Blue :) ), and monitoring regressions will be much easier. Recent regressions on the trunk-nightly-tests job prevent us from doing the same thing on the main test job (yet). 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 |