Wed, 23 Apr 2014 20:52:10 -0500 basectx: add _manifestmatches method
Sean Farley <sean.michael.farley@gmail.com> [Wed, 23 Apr 2014 20:52:10 -0500] rev 21466
basectx: add _manifestmatches method This method is a duplicate of localrepo.mfmatches and sets the stage for factoring localrepo.status into a context method that will be customizable based on inheritance and object type.
Tue, 11 Mar 2014 18:35:39 -0500 localrepo: always set the variable r in status method
Sean Farley <sean.michael.farley@gmail.com> [Tue, 11 Mar 2014 18:35:39 -0500] rev 21465
localrepo: always set the variable r in status method This is a small patch to help streamline keeping tracking of the list of files for status in a variable already called 'r' ('s' is for subrepos in this method). We now move the setting of it out of an 'if' block so that we can later refactor more code into the context objects.
Sun, 20 Apr 2014 16:44:45 -0700 run-tests: execute tests via unittest
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 16:44:45 -0700] rev 21464
run-tests: execute tests via unittest Now that unittest mode is functionally equivalent to the default mode, we switch the default execution mode to unittest and remove the choice of different execution modes.
Tue, 22 Apr 2014 13:37:27 -0700 run-tests: implement Test.__str__
Gregory Szorc <gregory.szorc@gmail.com> [Tue, 22 Apr 2014 13:37:27 -0700] rev 21463
run-tests: implement Test.__str__ unittest sometimes does a str(test) and the default implementation doesn't do the right thing. So we override it.
Mon, 21 Apr 2014 12:15:55 -0700 run-tests: make failure reporting in unittest mode equivalent to default
Gregory Szorc <gregory.szorc@gmail.com> [Mon, 21 Apr 2014 12:15:55 -0700] rev 21462
run-tests: make failure reporting in unittest mode equivalent to default Unlike unittest's defaults, our result formatter does not print stack traces. Here, we change TestResult.addFailure() to be compatible with the existing/default execution mode.
Sun, 20 Apr 2014 16:54:51 -0700 run-tests: ignore failures from rmtree
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 16:54:51 -0700] rev 21461
run-tests: ignore failures from rmtree rmtree() may fail under certain conditions. We ignore failures at the individual test level because they can interfere with test execution. Furthermore, we'll reattempt deletion in the high-level test runner after all tests have finished. Note that this patch is not a code refactor like most of the patches before it. This change logically makes sense given the execution behavior of the tests.
Sun, 20 Apr 2014 16:53:49 -0700 run-tests: abort tests after first failure in unittest mode
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 16:53:49 -0700] rev 21460
run-tests: abort tests after first failure in unittest mode There is an execution mode on run-tests.py that stops after the first failure. unittest mode was previously not obeying this option. This patch fixes that.
Sun, 20 Apr 2014 16:39:05 -0700 run-tests: print compatible output from TextTestRunner
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 16:39:05 -0700] rev 21459
run-tests: print compatible output from TextTestRunner Our unittest TextTestRunner now prints output similar to the output from the default execution mode - the output people expect from run-tests.py.
Sun, 20 Apr 2014 16:17:18 -0700 run-tests: don't print results in unittest mode
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 16:17:18 -0700] rev 21458
run-tests: don't print results in unittest mode A subsequent patch will have unittest print tests for us. Don't perform old-style printing when in unittest mode.
Sun, 20 Apr 2014 15:53:25 -0700 run-tests: move errpath deletion to setUp()
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 15:53:25 -0700] rev 21457
run-tests: move errpath deletion to setUp()
Sun, 20 Apr 2014 15:46:34 -0700 run-tests: kill daemons during tearDown()
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 15:46:34 -0700] rev 21456
run-tests: kill daemons during tearDown()
Mon, 21 Apr 2014 09:30:11 -0700 run-tests: move err file writing to tearDown()
Gregory Szorc <gregory.szorc@gmail.com> [Mon, 21 Apr 2014 09:30:11 -0700] rev 21455
run-tests: move err file writing to tearDown()
Sun, 20 Apr 2014 15:40:22 -0700 run-tests: refactor testtmp
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 15:40:22 -0700] rev 21454
run-tests: refactor testtmp testtmp is now a member variable of our test class. It's value is computed during instance creation and the directory is managed via the lifetime of the test object.
Sun, 20 Apr 2014 15:19:21 -0700 run-tests: store skipped state on Test
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 15:19:21 -0700] rev 21453
run-tests: store skipped state on Test As code is being moved between functions, we need a member variable to hold skipped state.
Sun, 20 Apr 2014 15:16:29 -0700 run-tests: move some functionality to Test.tearDown()
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 15:16:29 -0700] rev 21452
run-tests: move some functionality to Test.tearDown()
Sun, 20 Apr 2014 15:08:05 -0700 run-tests: store last result in Test._result
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 15:08:05 -0700] rev 21451
run-tests: store last result in Test._result Subsequent patches move post-test actions into tearDown(). This requires tearDown() to have access to the last result.
Sun, 20 Apr 2014 15:00:13 -0700 run-tests: report test duration in Test.tearDown()
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 15:00:13 -0700] rev 21450
run-tests: report test duration in Test.tearDown()
Sun, 20 Apr 2014 14:58:36 -0700 run-tests: store test return code and output in Test instance
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 14:58:36 -0700] rev 21449
run-tests: store test return code and output in Test instance A subsequent patch that will introduce tearDown() requires test execution state be stored in the instance.
Sun, 20 Apr 2014 14:55:33 -0700 run-tests: keep track of test start and stop in MercurialTest.run()
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 14:55:33 -0700] rev 21448
run-tests: keep track of test start and stop in MercurialTest.run() This brings run() more compatible with unittest.TestCase.run()
Sun, 20 Apr 2014 14:52:57 -0700 run-tests: keep track of test execution state in Test
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 14:52:57 -0700] rev 21447
run-tests: keep track of test execution state in Test This patch starts a mini series of moving functionality into the newly-established setUp() and tearDown() methods.
Sun, 20 Apr 2014 14:41:11 -0700 run-tests: support setUp() and tearDown() in TestCase wrapper
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 14:41:11 -0700] rev 21446
run-tests: support setUp() and tearDown() in TestCase wrapper unittest.TestCase.run() calls setUp() and tearDown() during run(). We emulate that implementation.
Sun, 20 Apr 2014 14:34:03 -0700 run-tests: fail tests by raising an exception
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 14:34:03 -0700] rev 21445
run-tests: fail tests by raising an exception When in unittest mode, Test.run() will now raise for all non-success cases. This makes it behave like TestCase.run().
Sun, 20 Apr 2014 14:32:03 -0700 run-tests: record warnings by raising WarnTest
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 14:32:03 -0700] rev 21444
run-tests: record warnings by raising WarnTest We continue the conversion of recording test results by raising exceptions.
Sun, 20 Apr 2014 14:28:29 -0700 run-tests: record ignored tests by raising IgnoreTest
Gregory Szorc <gregory.szorc@gmail.com> [Sun, 20 Apr 2014 14:28:29 -0700] rev 21443
run-tests: record ignored tests by raising IgnoreTest
(0) -10000 -3000 -1000 -300 -100 -50 -24 +24 +50 +100 +300 +1000 +3000 +10000 +30000 tip