b8ae2249a4
Some debugging tests relied on the following anti-pattern:
let exception = false;
try {
/* ... some code that may throw on test failure ... */
} catch (e) {
exception = e;
}
assertFalse(exception);
This may be problematic if a falseish value is thrown.
Change-Id: I02eace4cc656fc9581928a90ac53cda4dc72b30c
Reviewed-on: https://chromium-review.googlesource.com/972822
Reviewed-by: Georg Neis <neis@chromium.org>
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#52105}
|
||
|---|---|---|
| .. | ||
| bugs/harmony | ||
| debug | ||
| protocol | ||
| regress | ||
| wrapper | ||
| debugger.isolate | ||
| debugger.status | ||
| test-api.js | ||
| testcfg.py | ||