[Proposal] Baseline Test strategy #78
Description
Currently jedi has hand written tests. They are typically hard to made. And thus, in fact, tests are not frequently updated enough.
One test approach is baseline maintenance: for every input test case, the emitted output, called baseline, is maintained in source repository. When compiler code is updated, tests will run against these input files and outputs are compared with those in source repository. If there is difference then tests fail. Maintainer will need to update changed outputs, so tests will pass again.
The main benefit for baseline tests is the ease of adding test cases. Many popular transpiler projects use this strategy, For example, babel's babylon
IMHO, more tests will make jedi more robust.