4 Plan for new Addons Validator

Matthew Riley MacPherson редактировал(а) эту страницу 2015-09-18 16:11:58 +01:00

Содержание

• Things we still need to know:
• Our plan thus far:
• Next Steps
• Coding Standards

Things we still need to know:

• A complete list of all the validations we need to perform
• A (short) list of any manual checks we could easily automate or that would provide great benefits to human reviewers

Our plan thus far:

1. Move over all tests from Python to JS (using simple assert-type tests with chai/mocha for easy porting). We may drop some tests if there are features we don't need to support.
2. Get "feature parity" with the Python validator (by passing all tests).
3. Ship a CLI tool to allow offline validation
4. Run the JS validator alongside the Python one on the server; see if any bugs crop up, compare performance, etc.
5. Switch over to only the JS validator on the server
6. Make an add-on/Firefox build/etc. that allows in-browser validation (will talk to an external node module, installed on the user's computer)

Next Steps

• Find out how we need to write code to allow it to possibly run inside Firefox instead of an add-on? This is going to get messy and it makes more sense to build the add-on to interface with the CLI tool.
• Ask Jorge/John-Galt/mstriemer/add-ons team about features we can easily remove Waiting for reply on this :-)
• See what kinds of add-ons we even need to support (can we ditch XUL?)
• File bugs in GitHub

Coding Standards

We're going to ship on Node 4 to get ES6 features.