-
Notifications
You must be signed in to change notification settings - Fork 248
We should also run the test in non-checked mode #1103
Comments
+1 |
I'm working on it |
Do you think testing non-checked mode for Dart only is OK? Or should we cover both Dart and Dart2JS? |
Once you compile dart into JavaScript there's no more checked mode. Checked
|
@markovuksanovic you are right that after compilation there is no more checked mode. But you can still include/omit runtime assertions when compiling a Dart program to JS, which somewhat corresponds to running your program in checked/non-checked mode. And it looks like right when running Angular specs we always include those assertions. |
As discussed with Victor, testing Dart only seems a good option:
But if we expect the majority of users to use the JS version, it might also be a good idea to test it... |
Please run the tests in JS too. I've been fighting with #1097 (comment) for a day until I found this. After 2 months of experience with dart + angulardart, we've found that we constantly need to test the JS version because from time to time there are differences, crashes mostly. BTW, another hard one was this: |
We do run tests in JS. Tests are run in dart and JS for both stable and dev
|
We run quite some code in
assert()
sIt would be better to also the tests in non-checked to make sure everything is also fine.
See #1097 (comment) for an example of a non-checked mode failure only
The text was updated successfully, but these errors were encountered: