summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* blob: identify binary contentethomson/blob_data_is_binaryEdward Thomson2021-12-101-0/+16
| | | | | Introduce `git_blob_data_is_binary` to examine a blob's data, instead of the blob itself. A replacement for `git_buf_is_binary`.
* object: introduce a raw content validation functionethomson/object_validationEdward Thomson2021-11-301-0/+50
| | | | | Users may want to validate raw object content; provide them a function to do so.
* Merge pull request #6122 from libgit2/ethomson/cleanupEdward Thomson2021-11-309-20/+21
|\ | | | | Minor code cleanups
| * cmake: use CMAKE_SOURCE_DIR and CMAKE_BINARY_DIRethomson/cleanupEdward Thomson2021-11-221-3/+3
| | | | | | | | | | | | Instead of using the project-specific `libgit2_SOURCE_DIR` and `libgit2_BINARY_DIR` variables, use `CMAKE_SOURCE_DIR` and `CMAKE_BINARY_DIR`.
| * sha1: tests should use hashes, not oid computationEdward Thomson2021-11-221-11/+17
| | | | | | | | | | | | The tests that examine sha1 behavior (including collision detection) should test against the hash functionality directly, not indirectly using the oid functions.
| * util: don't include unnecessary system librariesEdward Thomson2021-11-226-6/+0
| | | | | | | | Remove some unnecessary includes from utility code.
| * utf8: include `utf8.h` in testsEdward Thomson2021-11-191-0/+1
| |
* | Merge pull request #6106 from ammgws/fixtemplateerrEdward Thomson2021-11-221-0/+10
|\ \ | |/ |/| Fix repo init when template dir is non-existent
| * tests: try to init with non-existent template pathJason Nader2021-11-121-0/+10
| |
* | date: rfc2822 formatting uses a `git_buf` instead of a static stringethomson/dateEdward Thomson2021-11-191-17/+14
| |
* | date: make it a proper `git_date` utility classEdward Thomson2021-11-182-8/+8
| | | | | | | | Instead of `git__date`, just use `git_date`.
* | cmake: enable testing at the top levelEdward Thomson2021-11-171-2/+0
| | | | | | | | | | | | | | Ensure that we `enable_testing()` at the top-level CMakeLists.txt or else we'll need to navigate within the build directory to the correct place in the hierarchy to run `ctest`. Now we can `ctest` at the top-level again.
* | cmake: better explain why headertests existsEdward Thomson2021-11-161-3/+8
| |
* | Make enum in src,tests and examples C90 compliant by removing trailing comma.Peter Pettersson2021-11-151-3/+3
| |
* | Add target for testing libgit2 headersPeter Pettersson2021-11-152-1/+26
| |
* | cmake: refactor global variablesEdward Thomson2021-11-141-7/+5
| | | | | | | | | | Update the global variables `LIBGIT2_OBJECTS` to `LIBGIT2_DEPENDENCY_OBJECTS` for clarity and consistency.
* | tests: include function declarationsEdward Thomson2021-11-115-4/+13
| |
* | test: correct test namesEdward Thomson2021-11-113-3/+3
| |
* | tests: declare functions statically where appropriateEdward Thomson2021-11-1134-60/+442
| |
* | clar: declare summary functions as staticEdward Thomson2021-11-111-5/+5
| |
* | tests: declare trace handler as staticEdward Thomson2021-11-111-1/+1
| |
* | tests: include test declarations for old gccEdward Thomson2021-11-111-1/+9
| | | | | | | | | | | | | | Older versions of gcc do not believe that we've adequately declared our test functions. Include `clar_suite.h` conditionally for those old versions. Do not do this on newer compilers to avoid unnecessary recompilation of the entire suite when we add or remove a test function.
* | clar: emit `clar_suite.h` with test declarationsEdward Thomson2021-11-111-13/+62
| | | | | | | | | | | | | | We may want to have test function declarations; produce a header file with (only) the test declarations. Update clar to avoid overwriting the file unnecessarily to avoid bumping timestamps and potentially recompiling unnecessarily.
* | cmake: move test enablement into test cmakeEdward Thomson2021-11-111-0/+2
| |
* | Merge pull request #6104 from libgit2/ethomson/pathEdward Thomson2021-11-1178-955/+1002
|\ \ | | | | | | path: refactor utility path functions
| * | path: length validation respecting core.longpathsEdward Thomson2021-11-091-18/+19
| | | | | | | | | | | | | | | Teach `git_path_is_valid` to respect `core.longpaths`. Add helper methods to validate length and set the error message appropriately.
| * | path: introduce `git_path_str_is_valid`Edward Thomson2021-11-091-7/+7
| | | | | | | | | | | | | | | Add a `git_str` based validity check; the existing `git_path_is_valid` defers to it.
| * | fs_path: make empty component validation optionalEdward Thomson2021-11-091-13/+30
| | |
| * | fs_path: introduce `str_is_valid`Edward Thomson2021-11-091-0/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Provide a mechanism for users to limit the number of characters that are examined; `git_fs_path_str_is_valid` and friends will only examine up to `str->size` bytes. `git_fs_path_is_valid` delegates to these new functions by passing `SIZE_MAX` (instead of doing a `strlen`), which is a sentinel value meaning "look for a NUL terminator".
| * | path: `validate` -> `is_valid`Edward Thomson2021-11-091-68/+68
| | | | | | | | | | | | | | | Since we're returning a boolean about validation, the name is more properly "is valid".
| * | fs_path: `validate` -> `is_valid`Edward Thomson2021-11-091-133/+133
| | | | | | | | | | | | | | | Since we're returning a boolean about validation, the name is more properly "is valid".
| * | path: separate git-specific path functions from utilEdward Thomson2021-11-0978-952/+954
| |/ | | | | | | | | | | Introduce `git_fs_path`, which operates on generic filesystem paths. `git_path` will be kept for only git-specific path functionality (for example, checking for `.git` in a path).
* | Add tests for ODB refreshJosh Triplett2021-11-086-7/+198
|/ | | | | Add optional refreshing in the fake backend, and count the number of refresh calls if enabled.
* libgit2_clar is now libgit2_testsMartin Kühl2021-10-282-5/+5
| | | | | | in #6083 the test runner was renamed to libgit2_tests, but not all references to the old name were updated. this change changes all of them to use the new name.
* cmake: stylistic refactoringEdward Thomson2021-10-181-49/+49
| | | | | Ensure that we always use lowercase function names, and that we do not have spaces preceding open parentheses, for consistency.
* cmake: BUILD_CLAR is now BUILD_TESTSethomson/clar_no_moreEdward Thomson2021-10-172-12/+12
| | | | | Nobody knows what CLAR is. The test building option should be `BUILD_TESTS`.
* str: introduce `git_str` for internal, `git_buf` is externalethomson/gitstrEdward Thomson2021-10-17192-2483/+2487
| | | | | | | | | | | | | | | | | | | | | | | | | | | libgit2 has two distinct requirements that were previously solved by `git_buf`. We require: 1. A general purpose string class that provides a number of utility APIs for manipulating data (eg, concatenating, truncating, etc). 2. A structure that we can use to return strings to callers that they can take ownership of. By using a single class (`git_buf`) for both of these purposes, we have confused the API to the point that refactorings are difficult and reasoning about correctness is also difficult. Move the utility class `git_buf` to be called `git_str`: this represents its general purpose, as an internal string buffer class. The name also is an homage to Junio Hamano ("gitstr"). The public API remains `git_buf`, and has a much smaller footprint. It is generally only used as an "out" param with strict requirements that follow the documentation. (Exceptions exist for some legacy APIs to avoid breaking callers unnecessarily.) Utility functions exist to convert a user-specified `git_buf` to a `git_str` so that we can call internal functions, then converting it back again.
* hash: hash functions operate on byte arrays not git_oidsEdward Thomson2021-10-025-9/+9
| | | | | | Separate the concerns of the hash functions from the git_oid functions. The git_oid structure will need to understand either SHA1 or SHA256; the hash functions should only deal with the appropriate one of these.
* hash: accept the algorithm in inputsEdward Thomson2021-10-015-7/+7
|
* Merge pull request #6076 from libgit2/ethomson/oidarray_disposeEdward Thomson2021-09-271-37/+37
|\ | | | | oidarray: introduce `git_oidarray_dispose`
| * oidarray: introduce `git_oidarray_dispose`ethomson/oidarray_disposeEdward Thomson2021-09-261-37/+37
| | | | | | | | | | | | Since users are disposing the _contents_ of the oidarray, not freeing the oidarray itself, the proper cleanup function is `git_oidarray_dispose`. Deprecate `git_oidarray_free`.
* | Merge pull request #6075 from libgit2/ethomson/attr_longpathsEdward Thomson2021-09-271-3/+3
|\ \
| * | attr_file: don't take the `repo` as an argethomson/attr_longpathsEdward Thomson2021-09-261-3/+3
| |/ | | | | | | The `repo` argument is now unnecessary. Remove it.
* | Merge pull request #6073 from libgit2/ethomson/attr_lookupsEdward Thomson2021-09-271-1/+88
|\ \
| * | repository: improve `hashfile` for absolute pathsEdward Thomson2021-09-251-1/+88
| |/ | | | | | | | | | | | | | | | | | | | | | | | | When `git_repository_hashfile` is handed an absolute path, it determines whether the path is within the repository's working directory or not. This is necessary when there is no `as_path` specified. If the path is within the working directory, then the given path should be used for attribute lookups (it is the effective `as_path`). If it is not within the working directory, then it is _not_ eligible. Importantly, now we will _never_ pass an absolute path down to attribute lookup functions.
* | buf: common_prefix takes a string arrayethomson/strarrayEdward Thomson2021-09-261-22/+7
|/ | | | | | `git_strarray` is a public-facing type. Change `git_buf_text_common_prefix` to not use it, and just take an array of strings instead.
* Merge pull request #6067 from libgit2/ethomson/filter_commit_idEdward Thomson2021-09-211-8/+2
|\ | | | | filter: use a `git_oid` in filter options, not a pointer
| * filter: use a `git_oid` in filter options, not a pointerethomson/filter_commit_idEdward Thomson2021-09-211-8/+2
| | | | | | | | | | | | | | Using a `git_oid *` in filter options was a mistake; it is a deviation from our typical pattern, and callers in some languages that GC may need very special treatment in order to pass both an options structure and a pointer outside of it.
* | rebase: fix (deprecated) signing testethomson/deprecationEdward Thomson2021-09-211-7/+7
|/
* Merge pull request #6061 from libgit2/ethomson/emailEdward Thomson2021-09-202-1/+383
|\ | | | | Introduce `git_email_create`; deprecate `git_diff_format_email`