anoma/juvix
1
1
Fork 0
mirror of https://github.com/anoma/juvix.git synced 2024-12-12 14:28:08 +03:00
Code Issues Projects Releases Wiki Activity
0ef464668d
juvix/tests/smoke/Commands/html.smoke.yaml

147 lines
4.3 KiB
YAML
Raw Normal View History

Use Smoke instead of shelltestrunner (#1710) This PR adds smoke tests using [Smoke tool](https://github.com/SamirTalwar/smoke) for all the shell tests we have. One reason for adopting Smoke instead of the previous tool, `shelltestrunner`, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax. To add a new smoke test, create a file with the suffix ".smoke.yaml" in the `tests/smoke` folder. In such a folder, you can also find examples of how to test the CLI.
2023-01-10 14:49:56 +03:00
working-directory: ./../../../examples/
tests:
- name: html-stdout
command:
shell:
- bash
script: |
cd milestone/ValidityPredicates
Refactor `html` command with extra options (#1725) This PR redefines the `html` command unifying our previous subcommands for the HTML backend. You should use the command in the following way to obtain the same results as before: - `juvix html src.juvix` -> `juvix html src.juvix --only-source` - `juvix dev doc src.juvix` -> `juvix html src.juvix` - Other fixes here include the flag `--non-recursive`, which replaces the previous behavior in that we now generate all the HTML recursively by default. - The flag `--no-print-metadata` is now called `--no-footer` - Also, another change introduced by this PR is asset handling; for example, with our canonical Juvix program, the new output is organized as follows. ``` juvix html HelloWorld.juvix --only-source && tree html/ Copying assets files to test/html/assets Writing HelloWorld.html html/ ├── assets │ ├── css │ │ ├── linuwial.css │ │ ├── source-ayu-light.css │ │ └── source-nord.css │ ├── images │ │ ├── tara-magicien.png │ │ ├── tara-seating.svg │ │ ├── tara-smiling.png │ │ ├── tara-smiling.svg │ │ ├── tara-teaching.png │ │ └── tara-teaching.svg │ └── js │ ├── highlight.js │ └── tex-chtml.js └── HelloWorld.html ├── Stdlib.Data.Bool.html ├── Stdlib.Data.List.html ├── Stdlib.Data.Maybe.html ├── Stdlib.Data.Nat.html ├── Stdlib.Data.Ord.html ├── Stdlib.Data.Product.html ├── Stdlib.Data.String.html ├── Stdlib.Function.html ├── Stdlib.Prelude.html └── Stdlib.System.IO.html ``` In addition, for the vscode-plugin, this PR adds two flags, `--prefix-assets` and `--prefix-url`, for which one provides input to help vscode find resource locations and Juvix files. PS. Make sure to run `make clean` the first time you run `make install` for the first time.
2023-01-17 20:11:59 +03:00
juvix html SimpleFungibleToken.juvix --only-source
Use Smoke instead of shelltestrunner (#1710) This PR adds smoke tests using [Smoke tool](https://github.com/SamirTalwar/smoke) for all the shell tests we have. One reason for adopting Smoke instead of the previous tool, `shelltestrunner`, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax. To add a new smoke test, create a file with the suffix ".smoke.yaml" in the `tests/smoke` folder. In such a folder, you can also find examples of how to test the CLI.
2023-01-10 14:49:56 +03:00
cat html/SimpleFungibleToken.html
Refactor `html` command with extra options (#1725) This PR redefines the `html` command unifying our previous subcommands for the HTML backend. You should use the command in the following way to obtain the same results as before: - `juvix html src.juvix` -> `juvix html src.juvix --only-source` - `juvix dev doc src.juvix` -> `juvix html src.juvix` - Other fixes here include the flag `--non-recursive`, which replaces the previous behavior in that we now generate all the HTML recursively by default. - The flag `--no-print-metadata` is now called `--no-footer` - Also, another change introduced by this PR is asset handling; for example, with our canonical Juvix program, the new output is organized as follows. ``` juvix html HelloWorld.juvix --only-source && tree html/ Copying assets files to test/html/assets Writing HelloWorld.html html/ ├── assets │ ├── css │ │ ├── linuwial.css │ │ ├── source-ayu-light.css │ │ └── source-nord.css │ ├── images │ │ ├── tara-magicien.png │ │ ├── tara-seating.svg │ │ ├── tara-smiling.png │ │ ├── tara-smiling.svg │ │ ├── tara-teaching.png │ │ └── tara-teaching.svg │ └── js │ ├── highlight.js │ └── tex-chtml.js └── HelloWorld.html ├── Stdlib.Data.Bool.html ├── Stdlib.Data.List.html ├── Stdlib.Data.Maybe.html ├── Stdlib.Data.Nat.html ├── Stdlib.Data.Ord.html ├── Stdlib.Data.Product.html ├── Stdlib.Data.String.html ├── Stdlib.Function.html ├── Stdlib.Prelude.html └── Stdlib.System.IO.html ``` In addition, for the vscode-plugin, this PR adds two flags, `--prefix-assets` and `--prefix-url`, for which one provides input to help vscode find resource locations and Juvix files. PS. Make sure to run `make clean` the first time you run `make install` for the first time.
2023-01-17 20:11:59 +03:00
stdout:
Use Smoke instead of shelltestrunner (#1710) This PR adds smoke tests using [Smoke tool](https://github.com/SamirTalwar/smoke) for all the shell tests we have. One reason for adopting Smoke instead of the previous tool, `shelltestrunner`, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax. To add a new smoke test, create a file with the suffix ".smoke.yaml" in the `tests/smoke` folder. In such a folder, you can also find examples of how to test the CLI.
2023-01-10 14:49:56 +03:00
contains:
<!DOCTYPE HTML>
exit-status: 0
- name: output-dir
command:
shell:
- bash
script: |
rm -rf html
Refactor `html` command with extra options (#1725) This PR redefines the `html` command unifying our previous subcommands for the HTML backend. You should use the command in the following way to obtain the same results as before: - `juvix html src.juvix` -> `juvix html src.juvix --only-source` - `juvix dev doc src.juvix` -> `juvix html src.juvix` - Other fixes here include the flag `--non-recursive`, which replaces the previous behavior in that we now generate all the HTML recursively by default. - The flag `--no-print-metadata` is now called `--no-footer` - Also, another change introduced by this PR is asset handling; for example, with our canonical Juvix program, the new output is organized as follows. ``` juvix html HelloWorld.juvix --only-source && tree html/ Copying assets files to test/html/assets Writing HelloWorld.html html/ ├── assets │ ├── css │ │ ├── linuwial.css │ │ ├── source-ayu-light.css │ │ └── source-nord.css │ ├── images │ │ ├── tara-magicien.png │ │ ├── tara-seating.svg │ │ ├── tara-smiling.png │ │ ├── tara-smiling.svg │ │ ├── tara-teaching.png │ │ └── tara-teaching.svg │ └── js │ ├── highlight.js │ └── tex-chtml.js └── HelloWorld.html ├── Stdlib.Data.Bool.html ├── Stdlib.Data.List.html ├── Stdlib.Data.Maybe.html ├── Stdlib.Data.Nat.html ├── Stdlib.Data.Ord.html ├── Stdlib.Data.Product.html ├── Stdlib.Data.String.html ├── Stdlib.Function.html ├── Stdlib.Prelude.html └── Stdlib.System.IO.html ``` In addition, for the vscode-plugin, this PR adds two flags, `--prefix-assets` and `--prefix-url`, for which one provides input to help vscode find resource locations and Juvix files. PS. Make sure to run `make clean` the first time you run `make install` for the first time.
2023-01-17 20:11:59 +03:00
juvix html milestone/ValidityPredicates/SimpleFungibleToken.juvix --only-source --output-dir=html --non-recursive
Use Smoke instead of shelltestrunner (#1710) This PR adds smoke tests using [Smoke tool](https://github.com/SamirTalwar/smoke) for all the shell tests we have. One reason for adopting Smoke instead of the previous tool, `shelltestrunner`, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax. To add a new smoke test, create a file with the suffix ".smoke.yaml" in the `tests/smoke` folder. In such a folder, you can also find examples of how to test the CLI.
2023-01-10 14:49:56 +03:00
[ -d html/assets ]
[ -f html/SimpleFungibleToken.html ]
Refactor `html` command with extra options (#1725) This PR redefines the `html` command unifying our previous subcommands for the HTML backend. You should use the command in the following way to obtain the same results as before: - `juvix html src.juvix` -> `juvix html src.juvix --only-source` - `juvix dev doc src.juvix` -> `juvix html src.juvix` - Other fixes here include the flag `--non-recursive`, which replaces the previous behavior in that we now generate all the HTML recursively by default. - The flag `--no-print-metadata` is now called `--no-footer` - Also, another change introduced by this PR is asset handling; for example, with our canonical Juvix program, the new output is organized as follows. ``` juvix html HelloWorld.juvix --only-source && tree html/ Copying assets files to test/html/assets Writing HelloWorld.html html/ ├── assets │ ├── css │ │ ├── linuwial.css │ │ ├── source-ayu-light.css │ │ └── source-nord.css │ ├── images │ │ ├── tara-magicien.png │ │ ├── tara-seating.svg │ │ ├── tara-smiling.png │ │ ├── tara-smiling.svg │ │ ├── tara-teaching.png │ │ └── tara-teaching.svg │ └── js │ ├── highlight.js │ └── tex-chtml.js └── HelloWorld.html ├── Stdlib.Data.Bool.html ├── Stdlib.Data.List.html ├── Stdlib.Data.Maybe.html ├── Stdlib.Data.Nat.html ├── Stdlib.Data.Ord.html ├── Stdlib.Data.Product.html ├── Stdlib.Data.String.html ├── Stdlib.Function.html ├── Stdlib.Prelude.html └── Stdlib.System.IO.html ``` In addition, for the vscode-plugin, this PR adds two flags, `--prefix-assets` and `--prefix-url`, for which one provides input to help vscode find resource locations and Juvix files. PS. Make sure to run `make clean` the first time you run `make install` for the first time.
2023-01-17 20:11:59 +03:00
stdout:
matches: |
Copying assets files to .*
Writing .*SimpleFungibleToken.html
Use Smoke instead of shelltestrunner (#1710) This PR adds smoke tests using [Smoke tool](https://github.com/SamirTalwar/smoke) for all the shell tests we have. One reason for adopting Smoke instead of the previous tool, `shelltestrunner`, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax. To add a new smoke test, create a file with the suffix ".smoke.yaml" in the `tests/smoke` folder. In such a folder, you can also find examples of how to test the CLI.
2023-01-10 14:49:56 +03:00
exit-status: 0
- name: recursive-generation
command:
shell:
- bash
script: |
rm -rf html
Refactor `html` command with extra options (#1725) This PR redefines the `html` command unifying our previous subcommands for the HTML backend. You should use the command in the following way to obtain the same results as before: - `juvix html src.juvix` -> `juvix html src.juvix --only-source` - `juvix dev doc src.juvix` -> `juvix html src.juvix` - Other fixes here include the flag `--non-recursive`, which replaces the previous behavior in that we now generate all the HTML recursively by default. - The flag `--no-print-metadata` is now called `--no-footer` - Also, another change introduced by this PR is asset handling; for example, with our canonical Juvix program, the new output is organized as follows. ``` juvix html HelloWorld.juvix --only-source && tree html/ Copying assets files to test/html/assets Writing HelloWorld.html html/ ├── assets │ ├── css │ │ ├── linuwial.css │ │ ├── source-ayu-light.css │ │ └── source-nord.css │ ├── images │ │ ├── tara-magicien.png │ │ ├── tara-seating.svg │ │ ├── tara-smiling.png │ │ ├── tara-smiling.svg │ │ ├── tara-teaching.png │ │ └── tara-teaching.svg │ └── js │ ├── highlight.js │ └── tex-chtml.js └── HelloWorld.html ├── Stdlib.Data.Bool.html ├── Stdlib.Data.List.html ├── Stdlib.Data.Maybe.html ├── Stdlib.Data.Nat.html ├── Stdlib.Data.Ord.html ├── Stdlib.Data.Product.html ├── Stdlib.Data.String.html ├── Stdlib.Function.html ├── Stdlib.Prelude.html └── Stdlib.System.IO.html ``` In addition, for the vscode-plugin, this PR adds two flags, `--prefix-assets` and `--prefix-url`, for which one provides input to help vscode find resource locations and Juvix files. PS. Make sure to run `make clean` the first time you run `make install` for the first time.
2023-01-17 20:11:59 +03:00
juvix html milestone/ValidityPredicates/SimpleFungibleToken.juvix --only-source --output-dir=html
(ls html | wc -l)
cd html
[ -f Stdlib.Data.Ord.html ]
[ -f Stdlib.Data.String.html ]
[ -f Stdlib.Data.Nat.html ]
[ -f Stdlib.System.IO.html ]
[ -f Stdlib.Function.html ]
[ -f Stdlib.Data.List.html ]
[ -f Stdlib.Data.String.Ord.html ]
[ -f Stdlib.Data.Product.html ]
[ -f Data.Int.Ops.html ]
[ -f Stdlib.Data.Maybe.html ]
[ -f Data.Int.html ]
[ -f Stdlib.Data.Bool.html ]
[ -f Stdlib.Prelude.html ]
[ -f Anoma.Base.html ]
[ -f SimpleFungibleToken.html ]
[ -f assets/css/source-ayu-light.css ]
[ -f assets/css/source-nord.css ]
[ -f assets/images/tara-magicien.png ]
[ -f assets/images/tara-seating.svg ]
[ -f assets/images/tara-smiling.png ]
[ -f assets/images/tara-smiling.svg ]
[ -f assets/images/tara-teaching.png ]
[ -f assets/images/tara-teaching.svg ]
[ -f assets/js/highlight.js ]
[ -f assets/js/tex-chtml.js ]
stdout:
contains: |
SimpleFungibleToken.html
exit-status: 0
- name: judoc-assets
command:
shell:
- bash
script: |
rm -rf html
juvix html milestone/ValidityPredicates/SimpleFungibleToken.juvix --output-dir=html
Use Smoke instead of shelltestrunner (#1710) This PR adds smoke tests using [Smoke tool](https://github.com/SamirTalwar/smoke) for all the shell tests we have. One reason for adopting Smoke instead of the previous tool, `shelltestrunner`, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax. To add a new smoke test, create a file with the suffix ".smoke.yaml" in the `tests/smoke` folder. In such a folder, you can also find examples of how to test the CLI.
2023-01-10 14:49:56 +03:00
(ls html | wc -l)
cd html
[ -f Stdlib.Data.Ord.html ]
[ -f Stdlib.Data.String.html ]
[ -f Stdlib.Data.Nat.html ]
[ -f Stdlib.System.IO.html ]
[ -f Stdlib.Function.html ]
[ -f Stdlib.Data.List.html ]
[ -f Stdlib.Data.String.Ord.html ]
[ -f Stdlib.Data.Product.html ]
[ -f Data.Int.Ops.html ]
[ -f Stdlib.Data.Maybe.html ]
[ -f Data.Int.html ]
[ -f Stdlib.Data.Bool.html ]
[ -f Stdlib.Prelude.html ]
[ -f Anoma.Base.html ]
[ -f SimpleFungibleToken.html ]
Refactor `html` command with extra options (#1725) This PR redefines the `html` command unifying our previous subcommands for the HTML backend. You should use the command in the following way to obtain the same results as before: - `juvix html src.juvix` -> `juvix html src.juvix --only-source` - `juvix dev doc src.juvix` -> `juvix html src.juvix` - Other fixes here include the flag `--non-recursive`, which replaces the previous behavior in that we now generate all the HTML recursively by default. - The flag `--no-print-metadata` is now called `--no-footer` - Also, another change introduced by this PR is asset handling; for example, with our canonical Juvix program, the new output is organized as follows. ``` juvix html HelloWorld.juvix --only-source && tree html/ Copying assets files to test/html/assets Writing HelloWorld.html html/ ├── assets │ ├── css │ │ ├── linuwial.css │ │ ├── source-ayu-light.css │ │ └── source-nord.css │ ├── images │ │ ├── tara-magicien.png │ │ ├── tara-seating.svg │ │ ├── tara-smiling.png │ │ ├── tara-smiling.svg │ │ ├── tara-teaching.png │ │ └── tara-teaching.svg │ └── js │ ├── highlight.js │ └── tex-chtml.js └── HelloWorld.html ├── Stdlib.Data.Bool.html ├── Stdlib.Data.List.html ├── Stdlib.Data.Maybe.html ├── Stdlib.Data.Nat.html ├── Stdlib.Data.Ord.html ├── Stdlib.Data.Product.html ├── Stdlib.Data.String.html ├── Stdlib.Function.html ├── Stdlib.Prelude.html └── Stdlib.System.IO.html ``` In addition, for the vscode-plugin, this PR adds two flags, `--prefix-assets` and `--prefix-url`, for which one provides input to help vscode find resource locations and Juvix files. PS. Make sure to run `make clean` the first time you run `make install` for the first time.
2023-01-17 20:11:59 +03:00
[ -f assets/css/source-ayu-light.css ]
[ -f assets/css/source-nord.css ]
[ -f assets/css/linuwial.css ]
[ -f assets/images/tara-magicien.png ]
[ -f assets/images/tara-seating.svg ]
[ -f assets/images/tara-smiling.png ]
[ -f assets/images/tara-smiling.svg ]
[ -f assets/images/tara-teaching.png ]
[ -f assets/images/tara-teaching.svg ]
[ -f assets/js/highlight.js ]
[ -f assets/js/tex-chtml.js ]
stdout:
Use Smoke instead of shelltestrunner (#1710) This PR adds smoke tests using [Smoke tool](https://github.com/SamirTalwar/smoke) for all the shell tests we have. One reason for adopting Smoke instead of the previous tool, `shelltestrunner`, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax. To add a new smoke test, create a file with the suffix ".smoke.yaml" in the `tests/smoke` folder. In such a folder, you can also find examples of how to test the CLI.
2023-01-10 14:49:56 +03:00
contains: |
Refactor `html` command with extra options (#1725) This PR redefines the `html` command unifying our previous subcommands for the HTML backend. You should use the command in the following way to obtain the same results as before: - `juvix html src.juvix` -> `juvix html src.juvix --only-source` - `juvix dev doc src.juvix` -> `juvix html src.juvix` - Other fixes here include the flag `--non-recursive`, which replaces the previous behavior in that we now generate all the HTML recursively by default. - The flag `--no-print-metadata` is now called `--no-footer` - Also, another change introduced by this PR is asset handling; for example, with our canonical Juvix program, the new output is organized as follows. ``` juvix html HelloWorld.juvix --only-source && tree html/ Copying assets files to test/html/assets Writing HelloWorld.html html/ ├── assets │ ├── css │ │ ├── linuwial.css │ │ ├── source-ayu-light.css │ │ └── source-nord.css │ ├── images │ │ ├── tara-magicien.png │ │ ├── tara-seating.svg │ │ ├── tara-smiling.png │ │ ├── tara-smiling.svg │ │ ├── tara-teaching.png │ │ └── tara-teaching.svg │ └── js │ ├── highlight.js │ └── tex-chtml.js └── HelloWorld.html ├── Stdlib.Data.Bool.html ├── Stdlib.Data.List.html ├── Stdlib.Data.Maybe.html ├── Stdlib.Data.Nat.html ├── Stdlib.Data.Ord.html ├── Stdlib.Data.Product.html ├── Stdlib.Data.String.html ├── Stdlib.Function.html ├── Stdlib.Prelude.html └── Stdlib.System.IO.html ``` In addition, for the vscode-plugin, this PR adds two flags, `--prefix-assets` and `--prefix-url`, for which one provides input to help vscode find resource locations and Juvix files. PS. Make sure to run `make clean` the first time you run `make install` for the first time.
2023-01-17 20:11:59 +03:00
SimpleFungibleToken.html
exit-status: 0
- name: non-recursive-generation
command:
shell:
- bash
script: |
rm -rf html
juvix html milestone/ValidityPredicates/SimpleFungibleToken.juvix --output-dir=html --non-recursive
(ls html | wc -l)
cd html
[ -d assets ]
[ -f SimpleFungibleToken.html ]
stdout:
matches: |
Copying assets files to .*
Writing .*SimpleFungibleToken.html
Update CI to install Smoke, Github actions, and Makefile fixes (#1735) This PR adds some maintenance at different levels to the CI config, the Make file, and formatting. - Most of the actions used by the CI related to haskell, ormolu, hlint and pre-commit have been updated because Github requires NodeJS 16. This change removes all the old warnings related to nodeJs. In the case of ormolu, the new version makes us format some files that were not formatted before, similarly with hlint. - The CI has been updated to use the latest version of the Smoke testing framework, which introduced installation of the dependencies for Linux (libicu66) and macOS (icu4c) in the CI. In the case of macOS, the CI uses a binary for smoke. For Linux, we use stack to build smoke from the source. The source here is in a fork of [the official Smoke repo](https://github.com/SamirTalwar/smoke). Such includes some features/changes that are not yet in the official repo. - The Makefile runs the ormolu and hlint targets using as a path for the binaries the environment variables ORMOLU and HLINT. Thus, export those variables in your environment before running `make check,` `make format` or `make hlint`. Otherwise, the Makefile will use the binaries provided by `stack`. Co-authored-by: Paul Cadman <git@paulcadman.dev>
2023-01-24 13:50:23 +03:00
\s*4
Refactor `html` command with extra options (#1725) This PR redefines the `html` command unifying our previous subcommands for the HTML backend. You should use the command in the following way to obtain the same results as before: - `juvix html src.juvix` -> `juvix html src.juvix --only-source` - `juvix dev doc src.juvix` -> `juvix html src.juvix` - Other fixes here include the flag `--non-recursive`, which replaces the previous behavior in that we now generate all the HTML recursively by default. - The flag `--no-print-metadata` is now called `--no-footer` - Also, another change introduced by this PR is asset handling; for example, with our canonical Juvix program, the new output is organized as follows. ``` juvix html HelloWorld.juvix --only-source && tree html/ Copying assets files to test/html/assets Writing HelloWorld.html html/ ├── assets │ ├── css │ │ ├── linuwial.css │ │ ├── source-ayu-light.css │ │ └── source-nord.css │ ├── images │ │ ├── tara-magicien.png │ │ ├── tara-seating.svg │ │ ├── tara-smiling.png │ │ ├── tara-smiling.svg │ │ ├── tara-teaching.png │ │ └── tara-teaching.svg │ └── js │ ├── highlight.js │ └── tex-chtml.js └── HelloWorld.html ├── Stdlib.Data.Bool.html ├── Stdlib.Data.List.html ├── Stdlib.Data.Maybe.html ├── Stdlib.Data.Nat.html ├── Stdlib.Data.Ord.html ├── Stdlib.Data.Product.html ├── Stdlib.Data.String.html ├── Stdlib.Function.html ├── Stdlib.Prelude.html └── Stdlib.System.IO.html ``` In addition, for the vscode-plugin, this PR adds two flags, `--prefix-assets` and `--prefix-url`, for which one provides input to help vscode find resource locations and Juvix files. PS. Make sure to run `make clean` the first time you run `make install` for the first time.
2023-01-17 20:11:59 +03:00
exit-status: 0
- name: non-recursive-generation-only-source
command:
shell:
- bash
script: |
rm -rf html
juvix html milestone/ValidityPredicates/SimpleFungibleToken.juvix --output-dir=html --non-recursive --only-source
(ls html | wc -l)
cd html
[ -d assets/ ]
[ -f SimpleFungibleToken.html ]
stdout:
matches: |
Copying assets files to .*
Writing .*SimpleFungibleToken.html
Update CI to install Smoke, Github actions, and Makefile fixes (#1735) This PR adds some maintenance at different levels to the CI config, the Make file, and formatting. - Most of the actions used by the CI related to haskell, ormolu, hlint and pre-commit have been updated because Github requires NodeJS 16. This change removes all the old warnings related to nodeJs. In the case of ormolu, the new version makes us format some files that were not formatted before, similarly with hlint. - The CI has been updated to use the latest version of the Smoke testing framework, which introduced installation of the dependencies for Linux (libicu66) and macOS (icu4c) in the CI. In the case of macOS, the CI uses a binary for smoke. For Linux, we use stack to build smoke from the source. The source here is in a fork of [the official Smoke repo](https://github.com/SamirTalwar/smoke). Such includes some features/changes that are not yet in the official repo. - The Makefile runs the ormolu and hlint targets using as a path for the binaries the environment variables ORMOLU and HLINT. Thus, export those variables in your environment before running `make check,` `make format` or `make hlint`. Otherwise, the Makefile will use the binaries provided by `stack`. Co-authored-by: Paul Cadman <git@paulcadman.dev>
2023-01-24 13:50:23 +03:00
\s*2
Use Smoke instead of shelltestrunner (#1710) This PR adds smoke tests using [Smoke tool](https://github.com/SamirTalwar/smoke) for all the shell tests we have. One reason for adopting Smoke instead of the previous tool, `shelltestrunner`, is that tests are declared cleanly and simply using Smoke Yaml syntax compared to shelltestrunner's syntax. To add a new smoke test, create a file with the suffix ".smoke.yaml" in the `tests/smoke` folder. In such a folder, you can also find examples of how to test the CLI.
2023-01-10 14:49:56 +03:00
exit-status: 0
Reference in New Issue Copy Permalink