actions/lint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-12-03 03:21:01 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 25
lint/.automation/test
History
Lucas Gravley 059754c8b3 super nasty bug fix
2020-06-17 09:36:57 -05:00
..
ansible adding them docs 2020-02-05 09:23:47 -06:00
coffeescript adding them docs 2020-02-05 09:23:47 -06:00
docker adding them docs 2020-02-05 09:23:47 -06:00
golang tabs v spaces 2020-02-28 10:29:43 -06:00
javascript adding them docs 2020-02-05 09:23:47 -06:00
json adding them docs 2020-02-05 09:23:47 -06:00
markdown adding them docs 2020-02-05 09:23:47 -06:00
perl adding them docs 2020-02-05 09:23:47 -06:00
python adding them docs 2020-02-05 09:23:47 -06:00
ruby super nasty bug fix 2020-06-17 09:36:57 -05:00
shell adding them docs 2020-02-05 09:23:47 -06: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