|
[
Permalink
| « Hide
]
Alejandro Scandroli added a comment - 25/Jun/07 01:33 PM
Following Tapestry's foot steps: Should we move from jUnit to TestNG?
I don't think we should/need to. I fail to see any tangible benefits of TestNG over JUnit 4.0, and there's just too many JUnit-derived frameworks that'll be that much more complex to use as TestNG test. The only major benefit would be to use tapestry-test base classes, but we already have our own.
Ok, I will just borrow some code from there, then.
The tap4.1.2 branch is ready for a test drive:
upgrades:
also added jmock: 2.1.0 I think we we might want to still delay collapsing it to the trunk because there's some hope to get the OGNL #this problem resolved first (http://jira.opensymphony.com/browse/OGNL-97
Working in trunk. A few OGNL issues still remaining, but works ok with the fixed OGNL 2.7.1 SNAPSHOT
|
|||||||||||||||||||||||||||||||||||||||||