| Re: [e4-dev] Project naming convention for junit test projects? |
At a previous project, tests were
1) Always in fragments extending the bundle under test.
2) The fragments were named the same as the bundle, with "test." prepended. Ie: test.org.eclipse.ui.
3) This made it easy to write a master TestSuite that looked through the workspace for anything starting with test and automatically running all tests found therein. No more manually maintaining TestSuite classes. :-)
Just a thought...
-Dave Orme
On Dec 9, 2008 1:52 PM, "Kevin McGuire" <Kevin_McGuire@xxxxxxxxxx> wrote:
Hi all,
I added a junit test suite and single test for the CSS work (it's a start!). As an aside, it's a great use of test-first programming, since it's helping to prioritize and make concrete the remaining methods that need to be filled into the CSS support.
Anyhoo the naming I ended up with was:
org.eclipse.e4.ui.tests.css.swt
which to my mind matches what we did before, like:
org.eclipse.ui.tests.*
However, I notice we have:
org.eclipse.e4.ui.compatibility.tests
which I think should be:
org.eclipse.e4.ui.tests.compatibility
or maybe more specific while we're at it,
org.eclipse.e4.ui.tests.workbench.compatibility
Thoughts?
Kevin
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev