actions/superlint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-11-07 01:35:53 -05:00
Code Issues Projects Releases Packages Wiki Activity
superlint/.automation/test
History
Eric Nemchik ff21bbf79c Always end with NC
2020-07-01 15:47:24 -05:00
..
ansible Always end with NC 2020-07-01 15:47:24 -05:00
cfn Add final yaml test cases 2020-06-26 22:06:35 +02:00
clojure Remove unused binding from good Clojure test file 2020-06-25 20:06:44 +12:00
coffeescript Add check spelling workflow 2020-06-23 16:42:22 -05:00
css Add check spelling workflow 2020-06-23 16:42:22 -05:00
docker adding them docs 2020-02-05 09:23:47 -06:00
env Add dotenv-linter support to super-linter (#173) 2020-06-19 20:32:07 +03:00
golang tabs v spaces 2020-02-28 10:29:43 -06:00
javascript spelling: visible 2020-06-21 00:02:45 -04:00
json adding them docs 2020-02-05 09:23:47 -06:00
kotlin Add kotlin support to super-linter 2020-06-21 17:49:34 +09:00
markdown Fixing grammar 2020-06-23 16:48:01 -05:00
openapi Fix OpenAPI tests being run by JSON & YAML 2020-06-25 11:49:09 +02:00
perl Add check spelling workflow 2020-06-23 16:42:22 -05:00
php removing hard coded errors 2020-06-22 14:42:49 -05:00
powershell adding more test cases 2020-06-22 08:40:09 -05:00
protobuf Add protolint support to super-linter 2020-06-28 20:17:08 +09:00
python Minor brand wording change 2020-06-19 07:44:26 +02:00
ruby adding them docs 2020-02-05 09:23:47 -06:00
shell Use portable shebang 2020-06-23 11:02:45 -05:00
terraform make good dir 2020-04-02 13:04:23 -04:00
typescript add bad code 2020-04-02 13:35:11 -05:00
xml adding them docs 2020-02-05 09:23:47 -06:00
yml adding them docs 2020-02-05 09:23:47 -06:00
README.md adding them docs 2020-02-05 09:23:47 -06: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