goldenscript 0.8.0

A scriptable, data-driven test framework using golden masters
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102

# Multi-line output should work fine.
command
command arg
---
Command {
    name: "command",
    args: [],
    context: Context {
        prefix: None,
        tags: {},
        silent: false,
        fail: false,
        line_number: 2,
    },
}
Command {
    name: "command",
    args: [
        Positional(
            "arg",
        ),
    ],
    context: Context {
        prefix: None,
        tags: {},
        silent: false,
        fail: false,
        line_number: 3,
    },
}

# Output that contains empty lines should automatically be prefixed with >.
# This should be the case for empty lines at the start and end of the output,
# as well as multiple empty lines.
_echo "foo\n\n"
---
> foo
> 

_echo "\nfoo"
---
> 
> foo

_echo "foo\n\n\nbar"
---
> foo
> 
> 
> bar

# Empty output blocks should default to "ok", but only once, and only if none of
# the commands produce any output.
_echo ""
---
ok

(command)
(command)
(command)
---
ok

(command)
command
(command)
---
Command {
    name: "command",
    args: [],
    context: Context {
        prefix: None,
        tags: {},
        silent: false,
        fail: false,
        line_number: 65,
    },
}

# Prefixes should handle empty output and output ending with a newline properly.
prefix: _echo ""
---
ok

prefix: _echo "\n"
---
prefix: 

prefix: _echo "\n\n"
---
prefix: 
prefix: 

# Lines only containing whitespace are not considered empty, and not prefixed.
# The output parser also handles them correctly when parsing this file.
_echo " "
_echo "  "
_echo "\t"
---