On completing my test sessions, I started to write bug reports into the tracker. I had this thought coming up again in me: "Should I keep all these problems under one bug report or have a separate one for each?".
- When we have the test with SRP (Single Responsibility Principle) and KISS (Keep it Simple and Straight), why not the bug reports?
- What's wrong if each symptom (consequence problems due to the root problem) has an individual bug report but linked to the root problem report?
At times, I'm said to include all symptoms in one bug report along with the root cause.
- I have witnessed the symptoms of a bug do not get fixed if it is mentioned collectively in one bug report.
- Also, the linked bug reports (i.e. symptoms of the root cause) do not get fixed when the root is fixed. It will be marked as Resolved and Fixed as the root is fixed and resolved.
Hardly I have seen the symptoms as well fixed along with the root cause.
That leaves with the questions:
- Just one bug report or separate bug reports?
- When a test has to be specific with individual responsibility and objective, why not the bug report?
- If the root cause is fixed does it resolve the symptoms?
- And, if the symptoms are resolved does it also resolve the root cause?
I look up to my consciousness should it be the separate bug reports or just in one bug report. I see, I can apply the SRP and KISS to the bug report effectively.
Looking at the number of bugs is not a wise strategy. But looking at the number of problems that one root problem opens and tracing them, is useful in the engineering of a product.
No comments:
Post a Comment
Please, do write your comment on the read information. Thank you.