New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP Control Flow v2 #280
WIP Control Flow v2 #280
Conversation
…syntax validation) and process (generating the linked list) test groups. Processing is still WIP.
dependency between Command and CommandStackHandler.
…n after storing them. Updated tests to use the return value instead of relying on the variable name since the implementation could change.
…eprocessStack into stack and work with just stack.
…preprocess for each Command.
…et of mutation functions (names TBD) called from within CommandStackHandler. Also swapped out Object.assign for the spread operator when creating array copies.
…which is for public vs. internal use.
… file/directory structure outside of __test__
… commands itself. Also refactored checks against the command name into functions, and renamed the mutation methods into something more descriptive.
…Moved it to the root of the IO directory, updated tests accordingly, and removed unnecessary files and folders. Also added additional isCommandType style functions and refactored all command type checks to use them.
…es a push down automata and finished implementing the currently written test cases.
…ct command references and removed this check from the other command node tests. Also added test coverage and implementation for some additional cases.
…e to use the correct getter (e.g., command instead of name)
…into its own file
…ds) and added a generic 'verify' command to accompany the 'assert' command added yesterday.
…andNode#execute`.
…nstead of by name). Updated the serialize command tests for control flow to use ControlFlowCommandNames. Cleaned up control flow commands in models/Command by removing type and fixed the word wrap on some error text in playback (to be consistent with what's done in other files).
…un would hang (and couldn't abort gracefully) when a variable name wasn't provided
…s the last one (assumes usage outside of control flow commands).
…ecute script test and move the remaining one into the smoke suite.
… passes the result object back, with the next node included.
… a simple object. Kept `startingCommandNode` and removed `currentCommandNode` since this differentiation is no longer needed. Updated its usage accordingly.
…eleniumCommand` and `doPluginCommand` into `doCommand`. Also updated part of `doPluginCommand` for better readibility.
…anifest accordingly
}; | ||
|
||
Selenium.prototype.doEvaluateConditional = function(condition) { | ||
return !!(this.eval(condition, undefined, true)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not scoped?
In WebDriver it'll be scoped.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can make it explicit, but isn't it already scoped if it's undefined
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forgot it has a default value true
, make it true anyway for clarification that it is required.
I put the default one, so that if it gets called from something internal that I'm not aware of, that it'll be scoped by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay.
… block in the playback `executionLoop`, pushing its execution into `doSeleniumCommand`
X
in the preceding checkbox, I verify that I have signed the Contributor License Agreement