Fix features/contractEditorSections.feature to account for "unfilled example" dialog#3544
Conversation
There was a problem hiding this comment.
- Should we just configure the contract editor to disable examples before we press "modalEditorClose"?
- Does this modal animate on close, and/or should we use "And I close the dialog" for this step as well? (It should apply to anything with an x-close button)
- Could these scenarios ever fail to show that pop-up, as they seemed to do on my local machine? Should we fail in that case?
There was a problem hiding this comment.
Re: 1, I like that idea for these, I believe there is a toggle that can be set after initialization
Re: 2, I don't think it should animate like the instructions dialog.
Re: 3, could it be that your local apps or blockly-core code is out of date?
|
Looks like we should also add this change to contractEditor.feature to fix the eyes tests. |
Test started failing because the level changed out from under it. Copied a version of the level from a few days ago (a passing one) into the allthethings script so it won't change in the future. Updated the test to pass (doesn't need the cancel button presses anymore). Aliased involved blocks so when it _does_ break again, it will be easier to read what it was trying to do.
|
Hm, so I think I like this PR's approach overall better than the somewhat confusing-feeling on/off switching in #3545 The one thing we do lose with the level no-examples change is eyes coverage of example block layout, but there's decent coverage of the eyes But I think that'd be better to add as an explicit separate test later. 🚢 it! |
|
👍 |
Fix features/contractEditorSections.feature to account for "unfilled example" dialog
#3501 added example checking on close of the contract editor. Some of our tests had empty examples which lead to an unfilled example dialog showing up.
This dismisses the dialog in the tests where this resulted in failures.
Before
Popup
Test output
After