You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a Bash tool bats but I feel that the spline way with yaml would be more comfortable. That's why to considere following new yaml format for testing Bash code:
suite:
"Verifying that a == b":
test: |
echo "hello"
test 2 == 3
verify: |
assert {{ test.output }} == "hello"
assert {{ test.exit_code }} == 0
Following features:
each test (script) is Bash code
each verification (script) is Python code
is capable to generate TAP report (useful for Jenkins)
tests can be filtered (substr search in title: --filter)
individual file or files in a path (recursively) with pattern test*.yaml (and test*.yml) will be fetched
running tests randomly by default (adjustable seed supported)
should be part of spline and so installed with spline
support for model as done for spline yaml
support for Jinja2 templating (model and env)
tests can run in parallell (--parallel)
The text was updated successfully, but these errors were encountered:
There's a Bash tool bats but I feel that the spline way with yaml would be more comfortable. That's why to considere following new yaml format for testing Bash code:
Following features:
The text was updated successfully, but these errors were encountered: