sapling/tests/test-run-tests.t

Simple commands:

  $ echo foo
  foo
  $ printf 'oh no'
  oh no (no-eol)
  $ printf 'bar\nbaz\n' | cat
  bar
  baz

Multi-line command:

  $ foo() {
  >     echo bar
  > }
  $ foo
  bar

Regular expressions:

  $ echo foobarbaz
  foobar.* (re)
  $ echo barbazquux
  .*quux.* (re)

Globs:

  $ printf '* \\foobarbaz {10}\n'
  \* \\fo?bar* {10} (glob)

Literal match ending in " (re)":

  $ echo 'foo (re)'
  foo (re)

Exit code:

  $ (exit 1) 
  [1]
tests: require regexes in unified tests to be marked with " (re)" Consider this test: $ hg glog --template '{rev}:{node\|short} "{desc}"\n' @ 2:20c4f79fd7ac "3" \| \| o 1:38f24201dcab "2" \|/ o 0:2a18120dc1c9 "1" Because each line beginning with "\|" can be compiled as a regular expression (equivalent to ".*\|"), they will match any output. Similarly: $ echo foo The blank output line can be compiled as a regular expression and will also match any output. With this patch, none of the above output lines will be matched as regular expressions. A line must end in " (re)" in order to be matched as one. Lines are still matched literally first, so the following will pass: $ echo 'foo (re)' foo (re) 2010-09-23 01:06:00 +04:00			`Simple commands:`

			`$ echo foo`
			`foo`
tests: (no-eol) markup for command output without trailing LF Output chunks without a trailing LF will now work but get (no-eol) appended. This change mostly moves code around so we can handle that an output line starts with data from previous command, followed by salt and the next command. 2010-11-08 03:35:40 +03:00			`$ printf 'oh no'`
			`oh no (no-eol)`
tests: various fixes for new unified test pattern format 2010-09-23 03:20:47 +04:00			`$ printf 'bar\nbaz\n' \| cat`
tests: require regexes in unified tests to be marked with " (re)" Consider this test: $ hg glog --template '{rev}:{node\|short} "{desc}"\n' @ 2:20c4f79fd7ac "3" \| \| o 1:38f24201dcab "2" \|/ o 0:2a18120dc1c9 "1" Because each line beginning with "\|" can be compiled as a regular expression (equivalent to ".*\|"), they will match any output. Similarly: $ echo foo The blank output line can be compiled as a regular expression and will also match any output. With this patch, none of the above output lines will be matched as regular expressions. A line must end in " (re)" in order to be matched as one. Lines are still matched literally first, so the following will pass: $ echo 'foo (re)' foo (re) 2010-09-23 01:06:00 +04:00			`bar`
			`baz`

			`Multi-line command:`

			`$ foo() {`
			`> echo bar`
			`> }`
			`$ foo`
			`bar`

			`Regular expressions:`

			`$ echo foobarbaz`
			`foobar.* (re)`
			`$ echo barbazquux`
			`.quux. (re)`

tests: add glob matching for unified tests This adds a " (glob)" marker that works like a simpler version of (re): "" is converted to ".", and "?" is converted to ".". Both special characters can be escaped using "\", and the backslash itself can be escaped as well. Other glob-style syntax, like "**", "[chars]", or "[!chars]", isn't supported. 2010-09-23 01:06:02 +04:00			`Globs:`

tests: various fixes for new unified test pattern format 2010-09-23 03:20:47 +04:00			`$ printf '* \\foobarbaz {10}\n'`
tests: add glob matching for unified tests This adds a " (glob)" marker that works like a simpler version of (re): "" is converted to ".", and "?" is converted to ".". Both special characters can be escaped using "\", and the backslash itself can be escaped as well. Other glob-style syntax, like "**", "[chars]", or "[!chars]", isn't supported. 2010-09-23 01:06:02 +04:00			`\* \\fo?bar* {10} (glob)`

tests: require regexes in unified tests to be marked with " (re)" Consider this test: $ hg glog --template '{rev}:{node\|short} "{desc}"\n' @ 2:20c4f79fd7ac "3" \| \| o 1:38f24201dcab "2" \|/ o 0:2a18120dc1c9 "1" Because each line beginning with "\|" can be compiled as a regular expression (equivalent to ".*\|"), they will match any output. Similarly: $ echo foo The blank output line can be compiled as a regular expression and will also match any output. With this patch, none of the above output lines will be matched as regular expressions. A line must end in " (re)" in order to be matched as one. Lines are still matched literally first, so the following will pass: $ echo 'foo (re)' foo (re) 2010-09-23 01:06:00 +04:00			`Literal match ending in " (re)":`

			`$ echo 'foo (re)'`
			`foo (re)`

			`Exit code:`

tests: avoid checking the exitcode of false Solaris false returns 255 instead of 1, so we remove one unneeded instance and replaces another with (exit 1) as suggested by Brodie Rao. 2010-09-25 23:52:17 +04:00			`$ (exit 1)`
tests: require regexes in unified tests to be marked with " (re)" Consider this test: $ hg glog --template '{rev}:{node\|short} "{desc}"\n' @ 2:20c4f79fd7ac "3" \| \| o 1:38f24201dcab "2" \|/ o 0:2a18120dc1c9 "1" Because each line beginning with "\|" can be compiled as a regular expression (equivalent to ".*\|"), they will match any output. Similarly: $ echo foo The blank output line can be compiled as a regular expression and will also match any output. With this patch, none of the above output lines will be matched as regular expressions. A line must end in " (re)" in order to be matched as one. Lines are still matched literally first, so the following will pass: $ echo 'foo (re)' foo (re) 2010-09-23 01:06:00 +04:00			`[1]`