When Executing Tests - Is it necessary to comment every step?
Or is marking it as "passed" good enough?
I'm asking because at my company I was told I have to write a comment after every step. Even if the comment is just "As expected" to say the step is as expected. I find this redundant because clicking "pass" is the same as saying "As expected". I think the comment field should be used for additional comments beyond saying just "as expected".
Does anyone have an opinion on this or have they been asked to do such a thing? I'm waiting to hear back what the logic is behind this but in the meantime thought i'd ask if anyone else see's value in this.
I think all good software development processes should include a weekly or bi-weekly retrospective. The retrospective should aim to provide a forum for team members to safely voice their concerns and come up with action items to improve the process.
If you can't challenge silly or unproductive things in the process.. Then it's probably a not a good work culture to stay in. Doesn't mean you will always get your way, but no process is 100% perfect for their business. All business/process need to adapt for the conditions, people, and situations that come up.