Max Power
My feedback
-
0 votesunder review · 2 comments · Silk Test Feature Request » Silk Test Workbench · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment -
3 votes
Silk Central Connect implements tighter connection with Silk Central and Silk test – will review to extend to wider integrations
Max Power
shared this idea
·
-
3 votes
will re-review –
audit requirements from organisations typically require a change in test result to be linked with comment to support reason for change.An error occurred while saving the comment Max Power
commented
Yeah we don't do it that way... after running it through Silk Central and finding all the failed tests we run each script manually through Silk Test to figure out why it failed (data, screen wrong, timing, or bad code). I bet would more then 50% of the time when we re-run a failed script its just bad data, or the screen had problems so it didn't work. So we just update the results to reflect or more to keep track, which ones actually failed because of bad code. (not just bad data or bad timing on the screen).
So once we know it works, i don't need to know why it worked.Thanks for reviewing it.
An error occurred while saving the comment Max Power
commented
My Co-Worked said
"yeah, that's kind of dumb that they require that, when pass is the relevant comment "An error occurred while saving the comment Max Power
commented
One more thing... I guess I can see it being required if you are changing it from Pass state to a Failed state... you probably want to know why it failed. But a comment is not needed when you are chaning from a Failed state to a Passed state. I can't think of any real useful info to put in the comment section.
"I ran it again so it worked"
"I updated the data so it worked"I shouldn't need to explain why something worked, only why something didn't work.
Max Power
shared this idea
·
-
6 votes
An error occurred while saving the comment Max Power
commented
Sean you are correct that On error Goto does work, but this is only for going to a label in the current script not calling another function.
But after I thought about this more, I realize this should probably be more added into Silk Central. I'm sure there are some tweaks to the Silk Test code, but really where you need to know if something fails is when you are running the code remotely which is happen through Silk Central. If you are running something through Silk Test you probably can see what is happening and why it failed.
Max Power
shared this idea
·
This is fixed in the newest Silk Test 15.5 The problem is the only way to turn this off (that I know of) is through the dialog box that shows up before you click Play/Run. The problem is you can hide that box to not show up.
So if the person already has this hidden, they still get the Local Variables showing up during playback. I assume there is a way to bring back the dialog box, then I can click to not show them????
Its on the right track, but wasn't thought out completely.