scenario testing of Unix command line tools
Log | Files | Refs | README | LICENSE

commit efa27bf25c5e20e6b8c7bf07fae001ba23baae2c
parent 6aa577238c2023223aff7c97be917b03457e9a49
Author: Richard Ipsum <richardipsum@vx21.xyz>
Date:   Thu,  4 Jun 2020 15:36:45 +0100

manpage: fix lint errors

Mtyarn.1 | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/tyarn.1 b/tyarn.1 @@ -1,4 +1,4 @@ -\.TH tyarn 1 +\.TH TYARN 1 2020-06-04 .SH NAME tyarn \- scenario testing of Unix command line tools .SH SYNOPSIS @@ -14,9 +14,9 @@ SCENARIO copy a file GIVEN a file F WHEN the file F is copied to G THEN the file G exists +.RE .fi .PP -.RE The scenario above describes a simple test for a copy utility, the SCENARIO line contains the name of the scenario (which must be unique). .PP @@ -72,8 +72,8 @@ cp "$MATCH_1" "$MATCH_2" IMPLEMENTS THEN the file ([A-Za-z0-9]+) exists test -e "$MATCH_1" .fi -.PP .RE +.PP For each capture an environment variable MATCH_N is defined, where N is the nth capture. Written this way the implementations may be used for any scenario