Hi, Team,
Sorry for the spam. I forgot to mention that these changes include a new plug-in
org.eclipse.papyrusrt.junit
that you will have to import into your workspace in order for the Core and Tooling JUnit test projects that you already have in your workspace to build. Some of the test fixtures (JUnit test rules and Hamcrest matchers) required by the tests have been factored out into this bundle. Of course, I encourage the team to contribute reusable test fixtures in here at every opportunity to help stream-line the development of tests.
If you use the Oomph developer setup model, you will get this new project in a “Papyrus-RT JUnit Framework” working set when next you run the setup. Note that this is all on the master branch only.
On 29 April, 2016 at 16:43:51, Christian Damus (give.a.damus@xxxxxxxxx) wrote:
These changes are merged and published in the wiki.
Thanks,
Christian
On 29 April, 2016 at 09:50:36, Christian
Damus (give.a.damus@xxxxxxxxx)
wrote:
Hi, Team,
I have a Gerrit 71612 in review
that changes the execution of JUnit tests in the Profile, Core, and
Tooling components, in particular switching from the
AllTests suite approach to the automatic discovery of
tests. I also propose guidelines aligned with this approach in a
new Wiki
page.
I would like to commit this work soon if there aren’t
objections, but I do want to solicit feed-back from the team before
I complete it. So please, if you have questions or concerns, do
comment here, in the Gerrit, and/or in the Wiki.
Thanks,
Christian
|
