2c02b110da
Add several test functions to make working with various hash-related values easier. Add test_oid_init, which loads common hash-related constants and placeholder object IDs from the newly added files in t/oid-info. Provide values for these constants for both SHA-1 and SHA-256. Add test_oid_cache, which accepts data on standard input in the form of hash-specific key-value pairs that can be looked up later, using the same format as the files in t/oid-info. Document this format in a t/oid-info/README directory so that it's easier to use in the future. Add test_oid, which is used to specify look up a per-hash value (produced on standard output) based on the key specified as its argument. Usually the data to be looked up will be a hash-related constant (such as the size of the hash in binary or hexadecimal), a well-known or placeholder object ID (such as the all-zeros object ID or one consisting of "deadbeef" repeated), or something similar. For these reasons, test_oid will usually be used within a command substitution. Consequently, redirect the error output to standard error, since otherwise it will not be displayed. Add test_detect_hash, which currently only detects SHA-1, and test_set_hash, which can be used to set a different hash algorithm for test purposes. In the future, test_detect_hash will learn to actually detect the hash depending on how the testsuite is to be run. Use the local keyword within these functions to avoid overwriting other shell variables. We have had a test balloon in place for a couple of releases to catch shells that don't have this keyword and have not received any reports of failure. Note that the varying usages of local used here are supported by all common open-source shells supporting the local keyword. Test these new functions as part of t0000, which also serves to demonstrate basic usage of them. In addition, add documentation on how to format the lookup data and how to use the test functions. Implement two basic lookup charts, one for common invalid or synthesized object IDs, and one for various facts about the hash function in use. Provide versions of the data for both SHA-1 and SHA-256. Since we use shell variables for storage, names used for lookup can currently consist only of shell identifier characters. If this is a problem in the future, we can hash the names before use. Improved-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
20 lines
817 B
Plaintext
20 lines
817 B
Plaintext
This directory contains various per-hash values that are used in the testsuite.
|
|
|
|
Each file contains lines containing a key-value pair; blank lines and lines
|
|
starting with `#` are ignored. The key and value are separated by whitespace
|
|
(specifically, those whitespace in the default `$IFS`). The key consists only
|
|
of shell identifier characters, and the value consists of a hash algorithm,
|
|
colon, and value. The hash algorithm also consists only of shell identifier
|
|
characters; it should match the value in sha1-file.c.
|
|
|
|
For example, the following lines map the key "rawsz" to "20" if SHA-1 is in use
|
|
and to "32" if SHA-256 is in use:
|
|
|
|
----
|
|
rawsz sha1:20
|
|
rawsz sha256:32
|
|
----
|
|
|
|
The keys and values used here are loaded by `test_oid_init` (see the README file
|
|
in the "t" directory) and are used by calling `test_oid`.
|