On 3/1/07, James Abley <james.abley@...> wrote:
> Hi all,
> 1. JUnit / TestNG / ANOther isn't used - just CPython tests. How well
> do people find that works with regard to refactoring?
Personally, I prefer unittest to Java-based unit testing. I think
that making the CPython unit tests better for cross-implementation
testing is a place where we (the Jython development community) can
really make a contribution back to CPython.
> 2. At least for unicodedata, the existing 2.3 CPython tests aren't
> quite what I'd like. CPython 2.3 and 2.4 unicodedata contains at
> least one bug, which has been confirmed by via private email
> discussion with one of the CPython developers (Martin von L=F6wis).
> Apparently, they aren't interested in fixing the issue in the older
> releases, since 2.5 is the current good release. Obviously, I don't
> intend to create the same bug in any implementation I provide, but
> that means that the 2.3 CPython tests won't pass. So, I would like to
> change those tests for three reasons.
> a) They aren't sufficiently granular.
> b) They are wrong.
> c) I'd prefer to use unittest anyway, rather than the custom framework
> that test_unicodedata.py currently uses.
I have no problem with pulling the 2.5 test in early (although not for
the 2.2 release) -- especially since we are going to up our target for
the next release to either 2.4 or 2.5. As AMK points out any
improvements we make to the CPython unittests can and should be