Ernesto,
I’m only looking at the Core and Tooling tests just now, sorry, as those are what this experimental build is stuck on.
Yes, Camille, I suppose that must be it. I do much prefer executing explicit AllTests suites so that we have a consistent execution in the build and developer environments. I’ll raise us a bug.
cW On 27 April, 2016 at 11:14:25, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
The codegen unit tests are all running, right?
We do have a "ConnectorCreationTest" (not plural), so I'm
guessing you are referring to a different one, right?
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
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.
_______________________________________________
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
_______________________________________________
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
|
