| Re: [papyrus-rt-dev] Many JUnit tests aren't running in the build |
Hi Christian,
Maybe one of these Maven/Tycho conventions? I think the Papyrus-RT build doesn’t use explicit test suites, but rather lets Tycho find each test class. And Tycho only knows about “*Test”?
Camille
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Christian Damus
Envoyé : mercredi 27 avril 2016 17:01
À : papyrus-rt-dev@xxxxxxxxxxx
Objet : [papyrus-rt-dev] Many JUnit tests aren't running in the build_______________________________________________
Hi, Team,
In trying to figure out why tests are failing in an experimental TP-based build, I went to compare the test results against what I see in my development environment on the master branch. The result was surprising.
The Maven build on Hudson is only executing some fraction of our tests. Is this deliberate? It only execute tests in classes named “*Test". We have many test classes named “*Tests" (plural), which are simply ignored. None of those tests run. Included among them are the CreateConnectorTests suite of some dozen cases that fails to initialize the entire suite when executed in my development environment. The build should have been failing on this for quite some while, now.
Cheers,
Christian
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev