Hi all,

Chris and I both mentioned some small issues with the test framework in
the last conference call, and I told Chris I'd look into them.  I just
made some fixes that I think are not controversial, so I thought I'd
post them first.  Then we can talk about the right way to do the other
stuff ;)

These patches are all on the 'testfix' branch,

        http://github.com/ctb/pygr/tree/testfix

Pull from:

        git://github.com/ctb/pygr.git

Istvan, Chris, could you review them, please?  They're all small changes.

Here are the individual patches and descriptions:

1. altered runtest to output the test name, rather than doctest
   descriptions, for tests:

  http://github.com/ctb/pygr/commit/32cf3a908b02cd37358d80b8509c5091454ea7b0

2. added tempdir and .DS_Store to .gitignore:

  http://github.com/ctb/pygr/commit/c13af7de6f42adc4e1b4501dd52146c9381fc088

3. put stdout/stderr capture & logging in place for xmlrpc server:

  http://github.com/ctb/pygr/commit/696661fe5593dcc32076dab8be62f374b2e3ac0e

4. number of tests passed now properly reported:

  http://github.com/ctb/pygr/commit/85a568adb85881dac807b620400e805bb63c991e

5. import & start figleaf code coverage (if wanted) *before* first pygr
   import:

  http://github.com/ctb/pygr/commit/0a75ef2f19f36d82ac6554a993777fe9ac981fcf
  http://github.com/ctb/pygr/commit/d6103e5ba8a08890123435ecd45a81f4538f5164

These last changes are required for the metabase review, because
metabase is now imported with the top-level pygr; in order to get proper
code coverage analysis, figleaf has to be started *before* the first
pygr import.  The code is ugly but *shrug* I don't see a cleaner way to
do it.

cheers,
--titus
-- 
C. Titus Brown, c...@msu.edu

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pygr-dev" group.
To post to this group, send email to pygr-dev@googlegroups.com
To unsubscribe from this group, send email to 
pygr-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to