- Apr 22, 2014
-
-
Gregory Szorc authored
Upcoming patches will move the execution of tests to separate processes. To facilitate this, it makes sense to move logic out of Test. Furthermore, test filtering is logically the domain of the test runner, not the test itself. This patch interrupts our mini series of factoring options into named arguments because filtering consults many options and it is easier to move this logic out of Test sooner so we don't have to introduce arguments at all.
-
Gregory Szorc authored
We no longer access any attributes on TestRunner besides options, so we stop passing a TestRunner to Test.__init__ and now pass the options data structure instead. Subsequent patches will move accessed options attributes into named arguments.
-
Gregory Szorc authored
-
Gregory Szorc authored
This patch starts a mini series of moving arguments to Test.__init__ from semi-complex data structures (such as the command options) to named arguments. This will allow Test instances to be more easily instantiated from other contexts. This improves the ability to run Mercurial tests in new and different environments.
-
- Mar 07, 2013
-
-
Stephen Lee authored
When updating to a bookmark, mention that the bookmark is now active. This is a reminder that update does not move the current bookmark if an explicit target is given - instead it activates that target.
-
- Apr 22, 2014
-
-
Gregory Szorc authored
Previously, a Test's path came from the base directory of all tests and a filename leaf. There is not a strong reason why an absolute test path can not be specified. This change isn't strictly necessary. But it does enable scenarios such as more easily running tests from multiple, non-sibling directories.
-
- Apr 21, 2014
-
-
Gregory Szorc authored
refpath is a side-effect of the test type. We therefore move it to the Test class implementations.
-
Gregory Szorc authored
Exceptions are all handled in Test.run(). This code was redundant since the unittest test wrapper class was merged into Test.
-
Gregory Szorc authored
We were only utilizing 2 parts of options. These have been converted to named arguments.
-
- May 16, 2014
-
-
Mads Kiilerich authored
Mercurial tags can be local (tag -l, stored in .hg/localtags) or global (normal tags, tracked in .hgtags) ... or extensions can add other kind of tags. Convert would take all tags (except "tip"), not just the ones from .hgtags, and put them into .hgtags. Instead, convert only the global tags that come from .hgtags.
-
- Apr 21, 2014
-
-
Gregory Szorc authored
We no longer need cleanup() because setUp() and tearDown() cover it. We move tempdir creation into setUp() and always delete in tearDown()
-
Gregory Szorc authored
-
Gregory Szorc authored
TestResult has facilities for recording when tests start and stop. It makes sense to move execution time recording into TestResult. In addition, output generation is being moved into TestResult, a class that has a concept of an output buffer (and a lock).
-
Gregory Szorc authored
The unittest runner now does all the printing. Move outputtimes() there.
-
Gregory Szorc authored
We now record times in Test.run(), which is a more appropriate place for it.
-
Gregory Szorc authored
The result of test execution is now reported on a TestResult. We no longer need to store a tuple of the result.
-
Gregory Szorc authored
-
Gregory Szorc authored
All the result functions now raise an Exception. We no longer need these functions and we can inline the raise.
-
Gregory Szorc authored
unittest handles all results now. We no longer need to manually keep track of results.
-
Gregory Szorc authored
Now that we execute all tests via unittest, the MercurialTest wrapper is not necessary. This patches moves the logic from MercurialTest into Test and makes Test a child of unittest.TestCase.
-
- May 17, 2014
-
-
Steven Brown authored
The check-code tool now expects the "desc" keyword to be followed by the "websub" filter, with the following exceptions: a) It has no filters at all, e.g. a changeset description in the raw style templates or the repository description in the summary page. b) It is followed by the "firstline" filter, e.g. the first line of the changeset description is displayed as a summary or title.
-
Steven Brown authored
For example, this is useful for linking from the feed reader to a bug tracker. This follows the existing pattern used within the hgweb templates. With the exception of the raw style, all usages of the changeset "desc" keyword are now followed by either the "firstline" filter or the "websub" filter. When "websub" is used, it always follows the "escape" filter.
-
Steven Brown authored
To improve the readability.
-
Steven Brown authored
This matches the existing tests for the atom feeds.
-
- Apr 23, 2014
-
-
Sean Farley authored
Now that we have the machinery in place, we call the context method for changing the match object in the case of comparing the working directory with its parent. This removes the last of the hard-coded workingctx knowledge in localrepo paving the way for us to remove localrepo.status completely.
-
- Apr 24, 2014
-
-
Sean Farley authored
This patch encapsulate the logic for changing the match.bad function when comparing against the working directory's parent. Future patches will remove more of the 'if ... else' blocks in localrepo.status that test for this working directory parent case.
-
- Apr 23, 2014
-
-
Sean Farley authored
This patch paves the way to allow a workingctx to override the match object with a custom 'bad' method for cases where status is sent a directory pattern.
-
- Apr 24, 2014
-
-
Sean Farley authored
This patch maintains the fast path for workingctx which is to not build a manifest if the working directory is being compared to its parent since, in this case, we can just copy the parent manifest.
-
- Apr 23, 2014
-
-
Sean Farley authored
This unpacking is unneeded now because previous patches have removed the need for this method to modify each of these variables in favor of passing the whole set around to pre/post hook methods of the corresponding context object.
-
- Apr 22, 2014
-
-
Sean Farley authored
-
Sean Farley authored
With this patch, we are one step closer to removing 'if ... else' logic in localrepo.status for testing if the context is the working directory or not. Future patches will replace those blocks of code with a call to the context's _poststatus hook so that each context object will do the right thing depending on the situation.
-
Sean Farley authored
This patch adds a private _poststatus method so that certain contexts, such as workingctx, can add custom post-processing to status.
-
Sean Farley authored
-
Sean Farley authored
With this patch, we are one step closer to removing 'if ... else' logic in localrepo.status for testing if the context is the working directory or not. Future patches will replace those blocks of code with a call to the context's _prestatus hook so that each context object will do the right thing depending on the situation.
-
Sean Farley authored
This patch adds a private _prestatus method so that certain contexts, such as workingctx, can add custom pre-processing to status.
-
Sean Farley authored
-
Sean Farley authored
This method is a copy of localstatus.status's core logic. Later patches will clean up some of the dense coditionals in the for loop.
-
Sean Farley authored
-
Sean Farley authored
This movement is a small step in getting rid of the 'if ... else' logic for testing the current working directory with its parent. Previously, the deleted, unknown, and ignored variables were set in a combination of before an 'if ... else' block and within the block. This moves the variables to be set outside the loop in one common place.
-
- Apr 15, 2014
-
-
Sean Farley authored
-