Commits

Bill_Barry committed c4f70f7

update tests because all really are passing

  • Participants
  • Parent commits ed3988f

Comments (0)

Files changed (7)

File runtests.bat

 pushd tests
 
 if "%1" == "-v" set verbose=1
+if "%1" == "-u" set update=1
 
 set /A numtests= 0
 set /A numfails= 0
 :run
 set /A numtests += 1
 call %1.bat > testoutput 2>&1
+if "%update%" == "1" call %1.bat > %1.out 2>&1
 diff -u %1.out testoutput > diffresults.txt 
 for %%R in ("diffresults.txt") do call :checksize %%~zR %1 
 erase testoutput

File tests/test-display.out

  adding a.txt
 adding b.txt
-### hg attic
+### hg attic
    a
  C b
 

File tests/test-finish.out

  adding a.txt
 A a.txt
-### hg ci -m "commit message"
-### hg log --template "{rev} {desc} {files}\n"
+### hg ci -m "commit message"
+### hg log --template "{rev} {desc} {files}\n"
 0 commit message a.txt
-### hg ci
-### hg log --template "{rev} {desc} {files}\n"
+### hg ci
+### hg log --template "{rev} {desc} {files}\n"
 1 commit message 3 a.txt
 0 commit message a.txt
-### hg ci -m "commit message 5"
-### hg log --template "{rev} {desc} {files}\n"
+### hg ci -m "commit message 5"
+### hg log --template "{rev} {desc} {files}\n"
 2 commit message 5 a.txt
 1 commit message 3 a.txt
 0 commit message a.txt

File tests/test-hgattic.out

 As applied patches are just changes in the working copy they are not part of
 the project history but can, of course, be commited if desired.
 
-Having all known patches in the .hg/attic directory allows you to easily
-share patch sets between repositories and even control version them.
+Having all known patches in the .hg/attic directory allows you to easily share
+patch sets between repositories and even control version them.
 
 Common tasks (use 'hg help command' for more details):
 
 attic-shelve (shelve):
-    store the current working copy changes in a patch in the attic and
-    prepare to work on something else unapplying those changes
-
+    store the current working copy changes in a patch in the attic and prepare
+    to work on something else unapplying those changes
 attic-display (attic, ls):
     list the patches in the attic
-
 attic-unshelve (unshelve):
     activate a patch to work on and merge its changes into the working copy
 
  attic-shelve     move changes from working copy to the attic
  attic-unshelve   applies a patch from the attic to the working copy
 
-enabled extensions:
-
- hgattic   patch management and development
-
 use "hg -v help hgattic" to show aliases and global options

File tests/test-shelve-subdir.out

- ### echo a > a.txt
-### mkdir b
-### echo b > b\b.txt
-### call hg addrem
+ ### echo a > a.txt
+### mkdir b
+### echo b > b\b.txt
+### call hg addrem
 adding a.txt
 adding b/b.txt
-### call hg st
+### call hg st
 A a.txt
 A b\b.txt
-### call hg shelve -r --git -q a
-### cd b
-### call hg shelve --git -q -f b
-### cd ..
-### diff .hg\attic\a .hg\attic\b
-### cd b
-### call hg unshelve
+### call hg shelve -r --git -q a
+### cd b
+### call hg shelve --git -q -f b
+### cd ..
+### diff .hg\attic\a .hg\attic\b
+### cd b
+### call hg unshelve
 patch b unshelved
-### call hg st
+### call hg st
 A a.txt
 A b\b.txt

File tests/test-shelve2.out

- ### echo a > a.txt
-### call hg addrem
+ ### echo a > a.txt
+### call hg addrem
 adding a.txt
-### call hg shelve a
+### call hg shelve a
 patch a shelved
-### echo b > b.txt
-### call hg addrem
+### echo b > b.txt
+### call hg addrem
 adding b.txt
-### call hg shelve a (should fail)
+### call hg shelve a (should fail)
 abort: attempting to overwrite existing patch
-### call hg attic
+### call hg attic
  C a
 

File tests/test-unshelve.out

 A a.txt
 A b.txt
 ### current applied patch
-b### hg shelve c (should fail)
+b
+### hg shelve c (should fail)
 abort: a different patch is active
 ### hg shelve -f c (should pass)
 patch c shelved