actions/superlint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-09-19 19:07:13 -04:00
Code Issues Projects Releases Packages Wiki Activity
superlint/.automation/test
History
Lukas Gravley c03ad1866e
Merge branch 'master' into stateLinter
2020-07-21 14:21:05 -05:00
..
ansible Variable braces 2020-07-21 12:23:27 -05:00
arm Format Markdown 2020-07-21 12:08:05 -05:00
cfn Format Markdown 2020-07-21 12:08:05 -05:00
clojure Format Markdown 2020-07-21 12:08:05 -05:00
coffeescript Format Markdown 2020-07-21 12:08:05 -05:00
css Format Markdown 2020-07-21 12:08:05 -05:00
dart Format Markdown 2020-07-21 12:08:05 -05:00
docker Format Markdown 2020-07-21 12:08:05 -05:00
editorconfig-checker Format Markdown 2020-07-21 12:08:05 -05:00
env Format Markdown 2020-07-21 12:08:05 -05:00
golang Format Markdown 2020-07-21 12:08:05 -05:00
html Format Markdown 2020-07-21 12:08:05 -05:00
javascript Format Markdown 2020-07-21 12:08:05 -05:00
json Format Markdown 2020-07-21 12:08:05 -05:00
kotlin Format Markdown 2020-07-21 12:08:05 -05:00
markdown Format Markdown 2020-07-21 12:08:05 -05:00
openapi Format Markdown 2020-07-21 12:08:05 -05:00
perl Format Markdown 2020-07-21 12:08:05 -05:00
php Format Markdown 2020-07-21 12:08:05 -05:00
powershell Format Markdown 2020-07-21 12:08:05 -05:00
protobuf Add more expected reports validations 2020-07-19 20:38:18 +01:00
python Format Markdown 2020-07-21 12:08:05 -05:00
raku Format Markdown 2020-07-21 12:08:05 -05:00
ruby Format Markdown 2020-07-21 12:08:05 -05:00
shell Variable braces 2020-07-21 12:23:27 -05:00
states Adding states linter 2020-07-21 13:50:04 -05:00
terraform Add more expected reports validations 2020-07-19 20:38:18 +01:00
typescript Format Markdown 2020-07-21 12:08:05 -05:00
xml Format Markdown 2020-07-21 12:08:05 -05:00
yml Format Markdown 2020-07-21 12:08:05 -05:00
README.md Format Markdown 2020-07-21 12:08:05 -05:00

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 )
    • 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 )
  • Script to run test cases and validate the sanity of Super-Linter