-
Hi!
I've noticed that flashAlert directive uses $timeout to auto-hide alert.
But this cause protractor tests to fail, e.g. when I want to test whether flash is shown, because while the flash is shown…
-
```
In core/tests/protractor/editorAndPlayer.js it used to be the case that the
"editor.expectStateNamesToBe(['state1', 'state2', 'END'])" line came just
before the previous "editor.moveToState('sta…
-
-
The protractor tests specs included in this repo use http://localhost:8080 but as far as I can tell there is no gulp task that sets up a local webserver at port 8080. To run the protractor tests local…
-
I'm not entirely sure if this is related to https://github.com/angular/protractor/issues/4347 or not since my output is slightly different, but I have an occasional failure running my protractor suite…
-
```
In core/tests/protractor/editorAndPlayer.js it used to be the case that the
"editor.expectStateNamesToBe(['state1', 'state2', 'END'])" line came just
before the previous "editor.moveToState('sta…
-
```
In core/tests/protractor/editorAndPlayer.js it used to be the case that the
"editor.expectStateNamesToBe(['state1', 'state2', 'END'])" line came just
before the previous "editor.moveToState('sta…
-
```
In core/tests/protractor/editorAndPlayer.js it used to be the case that the
"editor.expectStateNamesToBe(['state1', 'state2', 'END'])" line came just
before the previous "editor.moveToState('sta…
-
**I'm submitting a ...**
```
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here
```
…
-
```
In core/tests/protractor/editorAndPlayer.js it used to be the case that the
"editor.expectStateNamesToBe(['state1', 'state2', 'END'])" line came just
before the previous "editor.moveToState('sta…