~mdw
/
stgit
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
stgit.el: Garbage collect selected patches on reload
[stgit]
/
t
/
README
diff --git
a/t/README
b/t/README
index
d88bad2
..
1e9510b
100644
(file)
--- a/
t/README
+++ b/
t/README
@@
-22,11
+22,11
@@
The easiest way to run tests is to say "make -C t". This runs all
the tests.
*** t0000-basic.sh ***
the tests.
*** t0000-basic.sh ***
- * ok 1: .git/objects should be empty after git
-init-db
in an empty repo.
+ * ok 1: .git/objects should be empty after git
init
in an empty repo.
* ok 2: .git/objects should have 256 subdirectories.
* ok 2: .git/objects should have 256 subdirectories.
- * ok 3: git
-
update-index without --add should fail adding.
+ * ok 3: git
update-index without --add should fail adding.
...
...
- * ok 23: no diff after checkout and git
-
update-index --refresh.
+ * ok 23: no diff after checkout and git
update-index --refresh.
* passed all 23 test(s)
*** t0100-environment-names.sh ***
* ok 1: using old names should issue warnings.
* passed all 23 test(s)
*** t0100-environment-names.sh ***
* ok 1: using old names should issue warnings.
@@
-37,9
+37,9
@@
Or you can run each test individually from command line, like
this:
$ sh ./t3001-ls-files-killed.sh
this:
$ sh ./t3001-ls-files-killed.sh
- * ok 1: git
-
update-index --add to add various paths.
- * ok 2: git
-
ls-files -k to show killed files.
- * ok 3: validate git
-
ls-files -k output.
+ * ok 1: git
update-index --add to add various paths.
+ * ok 2: git
ls-files -k to show killed files.
+ * ok 3: validate git
ls-files -k output.
* passed all 3 test(s)
You can pass --verbose (or -v), --debug (or -d), and --immediate
* passed all 3 test(s)
You can pass --verbose (or -v), --debug (or -d), and --immediate
@@
-105,7
+105,7
@@
assignment to variable 'test_description', like this:
test_description='xxx test (option --frotz)
This test registers the following structure in the cache
test_description='xxx test (option --frotz)
This test registers the following structure in the cache
- and tries to run git
-
ls-files with option --frotz.'
+ and tries to run git
ls-files with option --frotz.'
Source 'test-lib.sh'
Source 'test-lib.sh'
@@
-154,19
+154,18
@@
library for your script to use.
Example:
test_expect_success \
Example:
test_expect_success \
- 'git
-
write-tree should be able to write an empty tree.' \
- 'tree=$(git
-
write-tree)'
+ 'git
write-tree should be able to write an empty tree.' \
+ 'tree=$(git
write-tree)'
- test_expect_failure <message> <script>
This is the opposite of test_expect_success. If <script>
yields success, test is considered a failure.
- test_expect_failure <message> <script>
This is the opposite of test_expect_success. If <script>
yields success, test is considered a failure.
- Example:
-
- test_expect_failure \
- 'git-update-index without --add should fail adding.' \
- 'git-update-index should-be-empty'
+ This should _not_ be used for tests that succeed when their
+ commands fail -- use test_expect_success and one of general_error,
+ command_error, and conflict for that. test_expect_failure is for
+ cases when a test is known to be broken.
- test_debug <script>
- test_debug <script>