> First, many thanks to Tim, Eli and those who helped them during PyCon 
> for making those improvements to our testing infrastructure.

I want to make sure Shane also gets a mention on the shortlist, he spent
a good chunk of the sprint on multi-db testing as well.

> My goal was to finalize the Windows support...[snip]

Thanks for that.  Windows testing at the sprints was notoriously
difficult because nobody was running it on hardware (and nobody with a
VM really wanted to install the dependencies, me included).

> Among other things, we now have the possibility to run the functional 
> tests without having the svn bindings installed. That was especially 
> important for me when testing 0.11-stable for Python 2.3 on Windows, 
> where the svn bindings are not readily available.

In case anyone is interested in reading more about this, check
doc/testing/*.rst.  We're trying to get all the test code
self-contained, so you can just "make test" or "make coverage".  It's
not quite there yet (in particular, we need to generate a
figleaf-exclude that includes distro-specific paths from the reports).

> I also verified that the functional tests still work on Linux with 
> PostgreSQL, but I couldn't test with MySQL - I hope this still works as 
> well.

Appears to work on Linux with Postgres 8.3 and Mysql 5, according to the
unofficial rework-testing buildbot we set up at the sprints since I
don't have Bitten admin access.
http://pacopablo.com:4200/waterfall?num_events=20

> On the branch itself, I see some remaining work to do:
>  - finalize http://trac.edgewall.org/ticket/8169 (Ability to run 
> functional tests on non-sqlite).

Agreed, the ability to destroy the db when the environment is
missing/not created is important.

>  - use the alternate database backends for the unit-tests as well.
>    Has someone already started to work on that?

No, and this would be a bit more difficult because IIRC they're not
designed to be pluggable.  I wouldn't consider that a blocker for the
branch being finally merged.

> I'd also be interested to know if there were further changes planned on 
> that branch.

1. The plugin testing api needs to be finalized.  I've gotten Noah's
permission to add tests to a few of his more popular plugins to get the
api straightened out.  We can start a separate plugin-testing thread if
anyone is interested in having a say in this.

2. We need to at least update the testing docs regarding that Genshi
ticket that's causing most of the functional suite to fail when run
against genshi-trunk instead of advanced-i18n
http://genshi.edgewall.org/ticket/291

3. Any remaining bits of TESTING-README need to be pulled into the
sphinxdocs and that file removed.

Tim

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to