summaryrefslogtreecommitdiff
path: root/git/test
Commit message (Collapse)AuthorAgeFilesLines
* Fixed submodule related issues once again - is it ever going to end ?Sebastian Thiel2011-07-072-5/+7
|
* Added default performance tests - these should help to measure something at ↵Sebastian Thiel2011-07-072-0/+12
| | | | least, which implicitly includes pack handling. For the pack specific tests to work, one would need a pack interface though, which is currently not planned to be specifically exposed
* Initial version of the DulwichType inheritance. For now, it inherits ↵Sebastian Thiel2011-07-074-7/+36
| | | | | | everything from the existing implementation, but one by one things can be reimplmented to use dulwich. It also shows that py 2.6 is quite plagued from its new feature, which is actually a bug, as objects inability to accept any args makes mixins hard to use ...
* removed now superfluous InstanceDecorator, as it was just complicating ↵Sebastian Thiel2011-07-071-41/+17
| | | | things after all
* Added auto-skip mixin metacls, some serious brainfuck, if the required ↵Sebastian Thiel2011-07-073-14/+123
| | | | module was not found. Its actually a nice mix between decorators which are class types, and a mixin as a metaclass, which applies said decorator. The InstanceDecorator wouldn't actually be needed, but it adds flexibility. Maybe it should be removed ...
* Added basis for initial dulwich integration. Many basic issues should ↵Sebastian Thiel2011-07-064-2/+33
| | | | surface while integrating this
* Implemented GIT_PYTHON_GIT_EXECUTABLE including test and docsSebastian Thiel2011-07-051-0/+10
|
* util: pick the type of memory manager based on the python version, to have ↵Sebastian Thiel2011-07-051-4/+3
| | | | | | | optimal results in all cases (at least the ones I can test) pack: now works properly with a sliding memory manager test_packedodb_pure: fixed very memory hungry implementation by using an iterator. This will of course reduce the measured performance a bit, but 750MB of memory is just a little bit too much for an ordinary test. Maybe it would be alright to just reduce the number of items ... but performance isn't a strength of python after all
* Fetch info can now deal much better with non-default ref specs, see #23, ↵Sebastian Thiel2011-07-042-4/+63
| | | | #24, #25
* refs: added constructor flag to allow refs to be instatiated from any path, ↵Sebastian Thiel2011-07-041-0/+5
| | | | including simple test
* fixed submodule test to work on windowsSebastian Thiel2011-06-131-2/+3
|
* test_submodule: Will now load everything into memory if smmap is present, to ↵Sebastian Thiel2011-06-131-0/+14
| | | | help the submodule test to work even on windows
* root submodule: Added parent_commit parameter for convenience. Fixed ↵Sebastian Thiel2011-06-131-4/+6
| | | | submodule tests to run
* Fixed submodule tests to go with either the old or the new version of gitdbSebastian Thiel2011-06-131-5/+6
|
* Fixed critical issue that would cause a string to be passed to methods that ↵Sebastian Thiel2011-06-081-3/+1
| | | | expect a stream
* symbolic reference handles different types for comparison more gracefully. ↵Sebastian Thiel2011-06-081-1/+9
| | | | Fixed possible issue in test_refs, which occurred in 0.3 previously
* util: Added test for iterable list, and implemented __contains__ and __del__ ↵Sebastian Thiel2011-06-081-1/+58
| | | | functionality
* pre-emptively moved all reference related tests into own package, to ↵Sebastian Thiel2011-06-084-0/+1
| | | | | | resemble their actual location a little more. Renamed test_git to test_cmd as it tests the git cmd located in git.cmd (not in git.git)
* Improved debug assertion to provide proper path on which to run a git daemonSebastian Thiel2011-06-081-2/+4
|
* Added additional opcodes to remote progress to make it compatible to newer ↵Sebastian Thiel2011-06-071-1/+1
| | | | git versions. This bug existed for quite a while but didn't show up as progress wasn't sent most of the time. All methods that could use a progress will only activate it if a progress is actually given
* Greatly improved robustness of config parser - it can now take pretty much ↵Sebastian Thiel2011-06-072-7/+15
| | | | everything. Includes an updated config file which includes all the new additions
* Submodule tests are fully back and workingSebastian Thiel2011-06-071-18/+28
|
* Submodule tests are nearly working. Only root module needs more attentionSebastian Thiel2011-06-071-9/+27
|
* First run in order to fix the remote handling. Cleaned up interfaces and ↵Sebastian Thiel2011-06-072-425/+428
| | | | figured out that the implementation really should be specific to the git command. This leaves the interface open for other implemntations which use a different way to provide feedback (as we do not make assumptions about the format of a feedback line)
* Added version_info property to git commandSebastian Thiel2011-06-071-0/+7
|
* Improved pack writing test to show that the pack generation can be lightning ↵Sebastian Thiel2011-06-061-21/+28
| | | | fast with nearly now overhead if the data streams in fast enough (~30 MB/s when writing a pack). This shows that there is huge potential for sending packs, considering that we are actually recompressing them (without deltification). To be faster in future, we could probably just send ref-deltas or full objects as found in the pack without doing any recompression.
* Fixed performance pack writing tests. As they are actually depent on the ↵Sebastian Thiel2011-06-062-80/+76
| | | | database (as streams have to be decompressed, it should be redesigned to have multiple database implementations)
* Moved performance commit object test into the respective subfolder to ↵Sebastian Thiel2011-06-062-1/+2
| | | | indicate what it tests
* Fixed performance commit object testingSebastian Thiel2011-06-063-8/+10
|
* Added loose object writing and reading performance tessts, in pure and ↵Sebastian Thiel2011-06-064-296/+149
| | | | command implementations. The previous performance test was truncated a bit as it compared directly with the git hash_object write performance. This is out, and if we wanted it we could implement it , but its actually slower for us
* Added PackedDB test with generalized type to allows other implementations to ↵Sebastian Thiel2011-06-063-7/+21
| | | | be tested as well at some point
* Fixed packed ODB test, in preparation for separating the type to allow ↵Sebastian Thiel2011-06-063-6/+21
| | | | future implementations to use the test as well
* Fixed odb performance testsSebastian Thiel2011-06-068-94/+102
|
* Fixed symref tests to work on osxSebastian Thiel2011-06-011-3/+2
|
* Fixed ref-log related issue in the test suite to assure it will not give ↵Sebastian Thiel2011-06-011-2/+9
| | | | false positives in repositories that are freshly checked out
* Fixed remaining tests as good as possible. remote/fetch/pull and submodule ↵Sebastian Thiel2011-05-3017-136/+190
| | | | tests need some more work. Also, the tests need to be reorganized and move closer to their actual location within gitpython. Hence the refs tests go to git.test.refs, etc
* Fixed all of the object tests, except for the submodule handling which needs ↵Sebastian Thiel2011-05-305-14/+39
| | | | more work as the amount of submodules changed in fact. Maybe I should just generate a test repository with gitpython as submodule to get the recursion depth required to satisfy the test
* Fixed all remaining python repository testsSebastian Thiel2011-05-309-64/+77
|
* Fixed test_loose.pySebastian Thiel2011-05-301-3/+5
|
* Fixed test_git.pySebastian Thiel2011-05-301-8/+12
|
* git cmd implementation of repository appears to work, at least this is what ↵Sebastian Thiel2011-05-309-31/+47
| | | | the test suggests. Pure python implementation still has some trouble, but this should be very fixable
* Fixed tests far enough to allow basic repository tests to be applied to any ↵Sebastian Thiel2011-05-309-36/+98
| | | | of the new database types. This reduces code duplication to the mere minimum, but allows custom tests to be added on top easily and flexibly
* Intermediate commit with quite some progress in order to put all extra ↵Sebastian Thiel2011-05-291-2/+2
| | | | methods on the default Repo implementation into interfaces or something that can be abstracted. It shows that it would indeed be good to keep the differentiation between Repositories which contain an object database as it is clearly easier to setup any combination of repositories that use git and those that do not, with just the addition of one more level of indirection. Lets see how it will end up
* Made repository paths methods a property to be compatible with the existing ↵Sebastian Thiel2011-05-102-7/+34
| | | | repo interface. Added submodule interface ... goal is to provide all of the extra repo functionality in custom interfaces
* Started to fix imports - tests still have no chance to work as database ↵Sebastian Thiel2011-05-0621-37/+45
| | | | changed drastically. Now the actual work begins
* replaced all gitdb strings with gitSebastian Thiel2011-05-0626-83/+87
|
* Added all code from gitdb to gitpython. Next is to make it generally work. ↵Sebastian Thiel2011-05-0527-37/+1750
| | | | Then the tests will need some work
* Updated objects to use the ones defined in gitdb as basis. Only the ↵Sebastian Thiel2011-04-075-36/+0
| | | | submodule implementation is left in git-python as it requires some advanced features. No tests where run yet
* Removed all parts of the reference implementation which doesn't require the ↵Sebastian Thiel2011-04-071-10/+5
| | | | git command. everything else was moved to GitDB. None of the tests is yet expected to run, although git-python should have less trouble getting the tests back up running than GitDB. plenty of code needs to be de-duplicated though in case of the tests, which will be some work
* Fixed incorrect handling of rev_parse if it was fed with branches that ↵Sebastian Thiel2011-02-231-1/+6
| | | | looked like hexshas. Thanks to Ning (frostyplanet) who pointed this issue out