selftest performance: landing our code faster and developing quicker.

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...
> We could do so in the short term, but long term, we'd better
> handle these edge cases explicitly in the test suite if only
> because everybody will then check them at a lower cost (neither
> the locale nor these extensions tests requires the *whole* test
> suite).
> 
> I think we did a pretty good job lately to ensure that python and
> pyrex versions receive the same unit tests, I don't think we
> encountered bugs due to lack of coverage there but even if we
> did, that's bumps on the road but this road is the good one.

I think we are good at making sure pyrex and python versions have the
same direct coverage. We *have* found a small handful of bugs from
integration tests when we forgot to build the extensions. We've also
found a few bugs when users forget to build extensions, which I don't
know whether or not it would have been caught by the test suite.

I know that both _groupcompress_py.py and _knowngraph_py.py have had
bugs that were encountered fairly randomly. And then I updated the
direct unit tests to cover those cases.

> 
> We still can have such a specific run without building the
> extensions, just to reassure ourselves that we're doing good, but
> once a week say, should be enough.
> 
>      Vincent
> 

What is the benefit? fairly low. What is the cost? seems even lower... I
don't think we need to run it across all platforms and all versions of
python, and ... But I think it would be good to have it as one of the CI
test beds.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqb/zgACgkQJdeBCYSNAAPBWACghjUwCjEP0EUZyfPK8bilkQNm
C/gAnjGtk/zSkEFR1Es6K3anUM3xMzLi
=4Wv+
-----END PGP SIGNATURE-----