- Apr 15, 2014
-
-
Sean Farley authored
-
- Mar 11, 2014
-
-
Sean Farley authored
-
- Apr 24, 2014
-
-
Sean Farley authored
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.
-
- Mar 11, 2014
-
-
Sean Farley authored
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.
-
- Apr 20, 2014
-
-
Gregory Szorc authored
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.
-
- Apr 22, 2014
-
-
Gregory Szorc authored
unittest sometimes does a str(test) and the default implementation doesn't do the right thing. So we override it.
-
- Apr 21, 2014
-
-
Gregory Szorc authored
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.
-
- Apr 20, 2014
-
-
Gregory Szorc authored
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.
-
Gregory Szorc authored
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.
-
Gregory Szorc authored
Our unittest TextTestRunner now prints output similar to the output from the default execution mode - the output people expect from run-tests.py.
-
Gregory Szorc authored
A subsequent patch will have unittest print tests for us. Don't perform old-style printing when in unittest mode.
-
Gregory Szorc authored
-
Gregory Szorc authored
-
- Apr 21, 2014
-
-
Gregory Szorc authored
-
- Apr 20, 2014
-
-
Gregory Szorc authored
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.
-
Gregory Szorc authored
As code is being moved between functions, we need a member variable to hold skipped state.
-
Gregory Szorc authored
-
Gregory Szorc authored
Subsequent patches move post-test actions into tearDown(). This requires tearDown() to have access to the last result.
-
Gregory Szorc authored
-
Gregory Szorc authored
A subsequent patch that will introduce tearDown() requires test execution state be stored in the instance.
-
Gregory Szorc authored
This brings run() more compatible with unittest.TestCase.run()
-
Gregory Szorc authored
This patch starts a mini series of moving functionality into the newly-established setUp() and tearDown() methods.
-
Gregory Szorc authored
unittest.TestCase.run() calls setUp() and tearDown() during run(). We emulate that implementation.
-
Gregory Szorc authored
When in unittest mode, Test.run() will now raise for all non-success cases. This makes it behave like TestCase.run().
-
Gregory Szorc authored
We continue the conversion of recording test results by raising exceptions.
-
Gregory Szorc authored
-
Gregory Szorc authored
The unittest way of recording a skipped test is to raise an exception (at least with modern unittest implementation). We change Test to raise a SkipTest when operating in unittest mode. This does prevent some "tear down" activities from running in unittest mode. This will be fixed in subsequent patches. Since unittest mode is experimental, this should be OK.
-
Gregory Szorc authored
Simply wrapping TestCase.run() is not sufficient for robust results reporting because unittest in Python 2.4 does not know about things like skipped tests and reports them as success or failures instead of skips. We will reimplement TestCase.run() with knowledge and semantics present in modern Python releases.
-
Gregory Szorc authored
unittest does its own printing of progress indicators as part of TestResult. So, there is no need to print them when running in unittest mode. This will fix the double output of progress indicators that had been occurring in unittest mode.
-
Gregory Szorc authored
We now have a custom unittest.TestSuite implementation that uses _executetests() and thus knows how to execute tests concurrently. Running tests in --unittest mode will use this TestSuite. Since the TestSuite handles concurrency, the warnings around --jobs and --loop have been removed.
-
Gregory Szorc authored
If the result is passed, we execute tests in the unittest way. A subsequent patch will actually do this.
-
Gregory Szorc authored
Test instances (not paths) are passed into _executetests(). This means the logic for instantiating Test instances has been moved outside of _executetests(). This was done because an upcoming patch will reuse the logic in _executetests(). As part of this change, test counts are no longer managed by _executetests().
-
- May 17, 2014
-
-
Gregory Szorc authored
We need a cleanup() on our unittest TestCase class to conform with the execution API. This will eventually be replaced by tearDown().
-
- Apr 20, 2014
-
-
Gregory Szorc authored
A lot of the attributes in Test could probably be renamed. This one is needed for an upcoming patch.
-
Gregory Szorc authored
Tests executing in unittest mode behave a little differently. For example, they report their results to a TestResult rather than just printing. This patch paves the way for better integration of Test into the unittest framework.
-
Gregory Szorc authored
-
Gregory Szorc authored
-
Gregory Szorc authored
-
Gregory Szorc authored
-
Gregory Szorc authored
We need to teach unittest about some custom result types. This will require some custom classes. This patch creates a skeleton for them.
-