| Re: [papyrus-rt-dev] Many JUnit tests aren't running in the build |
|
Hi, I discovered also that issue while working on the system protocol identification. I think indeed this is due to Maven conventions. On one of my patches, I am renaming some of the tests to follow the maven conventions, removing some of the ‘s’ at the end of the classes. But in fact, lot of
tests are failing, I wanted to investigate today or tomorrow the cause of these failures (as the Connector Tests) Regards, Rémi ------------------------------------------------------- Rémi SCHNEKENBURGER +33 (0)1 69 08 48 48 CEA Saclay Nano-INNOV Institut CARNOT CEA LIST De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Christian Damus 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 |
