1
0
mirror of git://git.code.sf.net/p/zsh/code synced 2024-11-15 13:34:18 +01:00
zsh/Test
..
.cvsignore
.distfiles
A01grammar.ztst
A02alias.ztst
A03quoting.ztst
A04redirect.ztst
A05execution.ztst
A06assign.ztst
B01cd.ztst
B02typeset.ztst
B03print.ztst
B04read.ztst
C01arith.ztst
C02cond.ztst
C03traps.ztst
C04funcdef.ztst
comptest
D01prompt.ztst
D02glob.ztst
D03procsubst.ztst
D04parameter.ztst
D05array.ztst
D06subscript.ztst
D07multibyte.ztst
D08cmdsubst.ztst
E01options.ztst
E02xtrace.ztst
Makefile.in
README
runtests.zsh
V01zmodload.ztst
V02zregexparse.ztst
V03mathfunc.ztst
V04features.ztst
V05styles.ztst
Y01completion.ztst
Y02compmatch.ztst
Y03arguments.ztst
ztst.zsh

There are now different sections, expressed by the first letter in the
scripts names:

 A: basic command parsing and execution
 B: builtins
 C: shell commands with special syntax
 D: substititution
 E: options
 V: modules
 W: builtin interactive commands and constructs
 X: line editing
 Y: completion
 Z: separate systems and user contributions

You will need to run these by using `make test' in the Test subdirectory of
the build area for your system (which may or may not be the same as the
Test subdirectory of the source tree), or the directory above.  You can get
more information about the tests being performed with
  ZTST_verbose=1 make check
(`test' is equivalent to `check') or change 1 to 2 for even more detail.

Individual or groups of tests can be performed with
  make TESTNUM=C02 check
or
  make TESTNUM=C check
to perform just the test beginning C02, or all tests beginning C,
respectively.

Instructions on how to write tests are given in B01cd.ztst, which acts as a
model.