mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-26 16:10:58 -05:00
00c70f4b2c
* Update snakefmt to 0.3.0 and black to 20.3 (now suppored by snakefmt). * Update pipfile for ansible 5.0 * Align pipfile python with Docker alpine image * Explicitly pin python minor version in dockerfile * Ansible updates * Add missing cryptography dependencies * Eliminate deprecated ansible syntax * Update expected output for ansible * Try to add regex to handle test run length * Yaml doc syntax fixes * Flailing attempt at tap wildcard * Catch dynamic output from ansible-lint * Update regex * Fix regex statement * Fix tap output * Update go error message (issue from master branch) * Fix regex * Ansible strikes back * Fix tap output * Fix json tap * Update r tap |
||
---|---|---|
.. | ||
ansible | ||
arm | ||
bash | ||
bash_exec | ||
clojure | ||
cloudformation | ||
coffeescript | ||
csharp | ||
css | ||
dart | ||
dockerfile | ||
dockerfile_hadolint | ||
editorconfig | ||
env | ||
gherkin | ||
go | ||
groovy | ||
html | ||
java | ||
javascript_es | ||
javascript_prettier | ||
javascript_standard | ||
jscpd | ||
json | ||
jsx | ||
kotlin | ||
kubernetes_kubeval | ||
latex | ||
lua | ||
markdown | ||
openapi | ||
perl | ||
php_builtin | ||
php_phpcs | ||
php_phpstan | ||
php_psalm | ||
powershell | ||
protobuf | ||
python_black | ||
python_flake8 | ||
python_isort | ||
python_pylint | ||
r | ||
raku | ||
ruby | ||
shell_shfmt | ||
snakemake_lint | ||
snakemake_snakefmt | ||
sql | ||
states | ||
tekton | ||
terraform | ||
terraform_terrascan | ||
terragrunt | ||
tsx | ||
typescript_es | ||
typescript_standard | ||
xml | ||
yaml | ||
README.md |
Test Cases
This folder holds test cases
that are used to validate the sanity of the Super-Linter.
The format:
- Each Super-Linter language should have its own folder
- Folder(s) containing test cases for each language supported
- Passing test case(s) per language denoted in naming scheme
- FORMAT:
LANGUAGE_(TYPE)_FILE.EXTENSION
- Example:
markdown_good_5.md
- Note: This allows the process to understand if linting of the file should pass or fail\
- Note: (good=Standard linting should be successful bad=standard linting should fail )
- FORMAT:
- Failing test case(s) per language denoted in naming scheme
- FORMAT:
LANGUAGE_(TYPE)_FILE.EXTENSION
- Example:
markdown_bad_5.md
- Note: (good=Standard linting should be successful bad=standard linting should fail )
- FORMAT:
- Script to run test cases and validate the sanity of Super-Linter