[
https://issues.jboss.org/browse/JBIDE-22460?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-22460:
------------------------------------------
I agree, there are benefits even though not huge ones I can spot so far:
* avoid the split-package pitfall when trying to have test classes in the same package as
the classes under test.
* Access to non-public classes/methods (?) - Even if this is true given OSGI access rules
one can also hide classes from 3rd party consumers, even though it's not as
fine-grained as what you can do with java access rules.
* What else?
The drawbacks:
* Multiply test fragments.
* Bugs in the Eclipse JUnit view ("does not allow you to double-click on a test case
to open the class" etc -
http://www.modumind.com/2007/06/20/unit-testing-plug-ins-with-fragments/)
* Caveats with the maven surefire plugin to take care of:
**
http://stackoverflow.com/questions/25476595/tycho-cannot-resolve-dependen...
**
http://tonnymadsen.blogspot.fr/2013/04/tycho-test-trouble-expectations-an...
* What else?
Test classes should be in the same package as the class(es) under
test
-----------------------------------------------------------------------
Key: JBIDE-22460
URL:
https://issues.jboss.org/browse/JBIDE-22460
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.0.Alpha2
Reporter: Jeff MAURY
Priority: Minor
Labels: test
Fix For: 4.4.x
Test classes should be in the same package as the class(es) under test as it is a
generally admitted pattern and as it allows to use package protected classes/methods
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)