[Checkins] [zopefoundation/z3c.testsetup] f2bbd3: Replace old nozopeapptesting.txt with unittest.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/zopefoundation/z3c.testsetup
  Commit: f2bbd38cf4b3fee460616c49517280b01ecd97fc
      https://github.com/zopefoundation/z3c.testsetup/commit/f2bbd38cf4b3fee460616c49517280b01ecd97fc
  Author: ulif <uli at gnufix.de>
  Date:   2015-05-13 (Wed, 13 May 2015)

  Changed paths:
    R src/z3c/testsetup/nozopeapptesting.txt
    A src/z3c/testsetup/tests/test_nozopeapptesting.py
    M src/z3c/testsetup/tests/test_testsetup.py

  Log Message:
  -----------
  Replace old nozopeapptesting.txt with unittest.

The testing of functionality based on modules being available
(like zope.app.testing) has many sideeffects and messing around with
sys.modules and sys.path like in the removed test made that clear.

As this one blocked other efforts (become py3 compatible, etc.), I
decided to reduce the tested functionality so that during tests
no modules are artificially added, disabled, or removed.

I would gladly appreciate hints that show how to disable certain
modules during certain tests properly.


  Commit: a3adf24e16f4f7e76061bb48e5e956aa8fc88952
      https://github.com/zopefoundation/z3c.testsetup/commit/a3adf24e16f4f7e76061bb48e5e956aa8fc88952
  Author: ulif <uli at gnufix.de>
  Date:   2015-05-13 (Wed, 13 May 2015)

  Changed paths:
    M src/z3c/testsetup/tests/test_testsetup.py

  Log Message:
  -----------
  Remove over-complicated test-context.

Execute all doctests in a single test suite that avoids sys.modules
magic.


Compare: https://github.com/zopefoundation/z3c.testsetup/compare/3b487094a516...a3adf24e16f4