You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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('state2')" line. However, on Jacob's
computer, the expectStateNamesToBe(['state1', 'state2', 'END']) call
consistently failed: the state names observed by protractor were ['', '', ''].
On Sean's computer, though, it consistently passed.
In order to get integration tests passing on Jacob's computer, these two lines
were switched. However, this is essentially a hack, so if you run into any
further issues with this or similar tests, please add information to this issue
so we can figure out what is actually going on.
So far, we have tried removing the moveToState() line altogether, and adding a
waitForSystem() call, but none of these work.
Original issue reported on code.google.com by jacobdav...@gmail.com on 27 Apr 2015 at 3:14
The text was updated successfully, but these errors were encountered:
Note: this refers to the second expectStateNamesToBe() call (the one that
happens before discardChanges()) in the following test:
describe('Full exploration editor', function() {
it('should handle discarding changes, navigation, deleting states, ' +
'changing the first state, displaying content, deleting rules and ' +
'switching to preview mode', function() {
Original comment by s...@seanlip.org on 27 Apr 2015 at 3:17
Original issue reported on code.google.com by
jacobdav...@gmail.com
on 27 Apr 2015 at 3:14The text was updated successfully, but these errors were encountered: