Add some additional test cases for ArcanistXHPASTLinterRule implementations and alo break down existing test cases into smaller test cases. Depends on D14010.
Details
Details
Diff Detail
Diff Detail
- Repository
- rARC Arcanist
- Branch
- master
- Lint
Lint Errors Severity Location Code Message Error src/lint/linter/xhpast/rules/__tests__/array-index-spacing/append.lint-test:7 TXT2 Tab Literal Error src/lint/linter/xhpast/rules/__tests__/array-index-spacing/index.lint-test:7 TXT2 Tab Literal Warning src/lint/linter/xhpast/ArcanistXHPASTLinterRule.php:212 TXT3 Line Too Long - Unit
Test Failures - Build Status
Buildable 8883 Build 10396: Run Core Tests Build 10395: arc lint + arc unit
Event Timeline
Comment Actions
That build failure looks accurate, see inline.
I'm not really sure that it's valuable to split tests like the define() test apart? I feel like when a test breaks, I often need to look at both positive and negative test cases to fix it. This seems to spread relevant information out without providing an obvious benefit -- it's not like this is breaking 1000-line ultra-tests apart, just splitting tiny tests of the same code (which already produce tailored, relevant errors on failure) apart? That said, I don't have particularly strong feelings either way.
src/lint/linter/xhpast/rules/__tests__/dynamic-define/static.lint-test | ||
---|---|---|
4 | Test failure on this seems correct? |