transpiler: Improve transpiler tests

[vicb]

As today we test the transpiler by running the spec in JS and Dart. While this is a good start, there is room for improvement.

Asserting that some code snippets fail (with a given error message) could also really help improving the test suite.

An example could be for the generation of const constructor: in Dart such constructor could not have a body (it can only have an initializer list). Asserting that this case fails with a comprehensible error message would be really helpful.

[tbosch]

For specs that should run only in Dart: use the .dart suffix and write them
in Dart
For specs that should only run in JS: use .es6 suffix

On Monday, September 29, 2014, Victor Berchet notifications@github.com
wrote:

As today we test the transpiler by running the spec in JS and Dart. While
this is a good start, there is room for improvement.

Asserting that some code snippets fail (with a given error message) could
also really help improving the test suite.

An example could be for the generation of const constructor: in Dart such
constructor could not have a body (it can only have an initializer list).
Asserting that this case fails with a comprehensible error message would be
really helpful.

—
Reply to this email directly or view it on GitHub
#25.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}