Skip to content

Conversation

@serhiy-storchaka
Copy link
Member

@serhiy-storchaka serhiy-storchaka commented Aug 30, 2021

…est. (GH-28006)

  • Functions registered with addModuleCleanup() were not called unless
    the user defines tearDownModule() in their test module.
  • Functions registered with addClassCleanup() were not called if
    tearDownClass is set to None.
  • Buffering in TestResult did not work with functions registered
    with addClassCleanup() and addModuleCleanup().
  • Errors in functions registered with addClassCleanup() and
    addModuleCleanup() were not handled correctly in buffered and
    debug modes.
  • Errors in setUpModule() and functions registered with
    addModuleCleanup() were reported in wrong order.
  • And several lesser bugs..
    (cherry picked from commit 08d9e59)

Co-authored-by: Serhiy Storchaka storchaka@gmail.com

https://bugs.python.org/issue43913

…est. (pythonGH-28006) * Functions registered with addModuleCleanup() were not called unless the user defines tearDownModule() in their test module. * Functions registered with addClassCleanup() were not called if tearDownClass is set to None. * Buffering in TestResult did not work with functions registered with addClassCleanup() and addModuleCleanup(). * Errors in functions registered with addClassCleanup() and addModuleCleanup() were not handled correctly in buffered and debug modes. * Errors in setUpModule() and functions registered with addModuleCleanup() were reported in wrong order. * And several lesser bugs.. (cherry picked from commit 08d9e59) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type-bug An unexpected behavior, bug, or error

4 participants