Test run status change
Could we make a request to remove the option of providing a comment when a test run status has been changed. Or please make this optional.
I agree that it is helpful to put in a comment. But If the comment is just that the script now passed, thats a useless comment. (I already know that) So I shouldn't be forced to to put in a comment when all we are typing in, is "it passed" or "it worked" which we already know. It should be optional, then if people want to do the "best practice" they can, but shouldn't be forced to. In QA Directory it wasn't required.
Point being we only have One guy run regression through Silk Central, it does no good for me to put in a comment on every script that failed. This adds work that serves no purpose for our company. Thus it shouldn't be required.
will re-review –
audit requirements from organisations typically require a change in test result to be linked with comment to support reason for change.
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.
Requirement for best practice from many organisations is that when a test is moved from a failed to a test then this is done as part of rerunning the test and as such a new execution.
The change test status for a completed test is there to change a status as a override which organisations indicated should require a reason / justification from a audit purpose.
Will review your feedback to see if further options available
My Co-Worked said
"yeah, that's kind of dumb that they require that, when pass is the relevant comment "
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.