[issue3979] Doctest failing when it should pass

New submission from J. Pablo Fernández <[EMAIL PROTECTED]>: The attached file contains a function and two tests for it which are essentially the same. One is a doctest and the other is a TestCase. The doctest fails and I believe it shouldn't. Here's what I get: $ python f

[issue3615] Expect methods for testing.

New submission from J. Pablo Fernández <[EMAIL PROTECTED]>: I'm attaching a patch that adds expect methods to TestCase. They are like fail methods, but they don't fail immediately. They are useful when you want to catch more than one error at a time. I included some tests. Ther

[issue2821] unittest.py sys.exit error

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Shouldn't this be closed now? or is there anything pending to be solved? -- nosy: +pupeno ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.

[issue1034053] unittest.py patch: add skipped test functionality

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Oh, I forgot to upgrade versions to include Python 3.0 and to mention that I have to fix some other tests to work with the new TestCase. It's nothing serious, just doctests that where too dependent on the output of the TextTes

[issue1034053] unittest.py patch: add skipped test functionality

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Hello, The attached patch adds the skip functionality and tests to a very recent (yesterday) Python 3. It took me a few hours to apply the patch, change to Python 3 style, merge the tests into the current set of tests not doing

[issue2578] Figure out what to do with unittest's redundant APIs

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Is there anything that can be done now about this issue? like renaming the API and leaving the old names as aliases? If so, let me know and I'll try to work on it. -- nosy: +pupeno ___

[issue3379] Option to not-exit on test

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: What about always returning the results. Granted, when sys.exit is run there will be no results returned, but then nothing to get the results. If we divided in two functions, would one be unittest.main and the

[issue2674] unittest.TestProgram uses sys.exit()

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: I was bothered by this 'bug' ages ago, and I was work-arounding it. So now I've spent some time in 'fixing' it with the patches on issue #3379. -- nosy: +pupeno ___

[issue3379] Option to not-exit on test

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Added tests. Added file: http://bugs.python.org/file10929/add_avoid_exit_option.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3379] Option to not-exit on test

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Added some documentation. Added file: http://bugs.python.org/file10909/add_avoid_exit_option.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3379] Option to not-exit on test

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Indeed this patch can be considered a fix for #2674, but, it should be documented appropriately. Should that be in http://docs.python.org/dev/3.0/library/unittest.html ? ___ Python tracker &

[issue3379] Option to not-exit on test

Changes by J. Pablo Fernández <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10906/add_avoid_exit_option.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3379] Option to not-exit on test

Changes by J. Pablo Fernández <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10908/add_avoid_exit_option.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3379] Option to not-exit on test

New submission from J. Pablo Fernández <[EMAIL PROTECTED]>: Added an option, called exit, that when set to false, will make the tests not exit at the end. This is useful when you are doing Lisp-like development having a REPL (interpreter/prompt) opened in Emacs and running the tests ov