Couple of questions on debugging, and what is the best way to handle these like any IDEs as these things would save more time.
While a script is running, getting error as couldn’t find a text - How I can just skip this step and go to next step?
While a script is running, getting error as couldn’t find a text - Here, I am closing that error dialog, try to update some variable value using the command box, so if I run the same step again should pass. But the update is not working here if I do like put “newvalue” into myVar --or set myVar to “newvalue”
I don’t want to stop the script entirely and execute again.
Created a schedule and added 5 tests. How I can set something like if first test executed without any errors or passed, then execute 2nd. Otherwise, just stop.
Yes, I agree with all your inputs. But all my questions are not generic to the scripting instead only with respect to the Eggplant IDE and the options it offers to debug.
For ex.
For Q1 - I am expecting a skip or step out kind of debug feature (current step out just trying to execute the lines before coming out of the current scope method)
For Q2 - Seems like there is some bug in updating that while in pause mode after an error… But I just saw another way which is working it seems - Just double click the variable, then edit/save in the below display/edit area
For Q3 - I expect an option like what to do for each test which I have added in the Eggplant Schedule like Execute only if Previous Test is Success or so on. Otherwise, I can’t use Schedule or I have to write my own master execution script.
Still, I didn’t started to use Eggplant Manager, not sure if that has this execution related conditioning.
For Q1 - There is no mechanism in the debugger for skipping past code without executing it. You would need to add a conditional in your script to do that.
For Q2 - When your script is paused, you can execute commands like put “newvalue” into myVar in the Do box to change the value in a variable (or do it through the variable-watcher interface, as you discovered). But of course that will only affect later lines in the script - you can’t back the script up to re-run code that has already been run.
For Q3 - You can click the
button to indent one test under another. Then the indented test will only be run if the first one succeeds.
Thanks Doug.
I have tried to indent the scripts’, but I couldn’t uncheck/check a script now. I can see all the sub scripts’ checkboxes are disabled (which makes sense) when the parent is OFF, but the issue is I can’t even turn ON or OFF the root parent script (but the checkbox button is enabled).
I did close the tool and reopen but no luck.
