canmove, Confirmed users
1,448
edits
User:Clouserw/AMO/Validator:v2: Difference between revisions
Jump to navigation
Jump to search
→Idea List
m (Created page with 'Version 1 of our add-on validator has been a great success and really proven the value of an automated validation system. This year we need to take it to the next level with som…') |
|||
| Line 17: | Line 17: | ||
* Better L10n support (there are a couple old bugs about this, and we need to update the external) | * Better L10n support (there are a couple old bugs about this, and we need to update the external) | ||
* Add-ons for unit tests can be built on the fly. Jbalogh has a short script that this can be based on. | * Add-ons for unit tests can be built on the fly. Jbalogh has a short script that this can be based on. | ||
'''Jorge suggests:''' | |||
* Be smart about caching: only clear validation results cache when the file is modified or the validator is modified. Maybe clearing the validation cache could be added as a step for production pushes. | |||
* Give priority to add-on uploads (by authors) in the validation queue. | |||
* Give severity weight to warnings and sort them by severity. | |||
* Recognize common validation patterns and make it easier to add them. For example: | |||
** [ file mask (*.js), what to look for (/eval/), severity (high), grouping ]. | |||
** (the grouping would be for grouping similar results together and showing the link to the validation page) | |||
* Easy to download and distribute (to developers). | |||
* Smarter JS library recognition. Use common internal patterns instead of just file names. | |||