[
http://jira.jboss.com/jira/browse/JBAOP-416?page=comments#action_12365301 ]
Kabir Khan commented on JBAOP-416:
----------------------------------
We probably need to do something like pass in a system property to the test containing the
version (A) we are testing against, and to have something at the start of each test
mentioning the version (B) the tested feature exists from. If B > A then ignore the
test or just return
Exclude tests testing new functionality from
---------------------------------------------
Key: JBAOP-416
URL:
http://jira.jboss.com/jira/browse/JBAOP-416
Project: JBoss AOP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Kabir Khan
Assigned To: Kabir Khan
Fix For: 1.5.6.GA, 2.0.0.alpha6
Once that is done, can you do me a favour?
Kabir says:
build.sh -f build-test-jdk50.xml clean-tests compile-test-classes
precompiled-compatibility-tests
Kabir says:
It weaves with aop 1.5.5.GA and runs with AOP 2.0
Kabir says:
some tests will fail, but most should pass
Flávia says:
Sure
Kabir says:
The tests that fail will hopefully be tests where we added some functionality in AOP 2.0
that does not exist in AOP 1.5.5.GA
Kabir says:
Ideally we need some way to exclude tests that are newer functionality than exists in the
old version
Kabir says:
I'll add a JIRA for that
Kabir says:
since it would be good to get these automated
Kabir says:
I only remembered this since I spoke to Jason Green earlier about backward compatibility
Flávia says:
Yes. After all, we don't have a way of making new functionality work in JBAOP1.5
Kabir says:
Thanks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira