On a good day I view a bug as a curiosity. It indicates a new challenge, how do I isolate it to effectively reproduce, how do I find similar issues?
Other days it is an indicator of failure. When you work at eliminating the amount of testing you do for a given release you're bound to choose incorrectly. My preference is to understand why I eliminated a class of testing which would have caught the issue. My concern is that testing that behavior is expected every release with documentation on pass/fail.
Note automation is used and helpful, but if ever test needs to run every release, and releases don't stop just because you're testing, it leaves no time to reduce time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My role is software testing.
On a good day I view a bug as a curiosity. It indicates a new challenge, how do I isolate it to effectively reproduce, how do I find similar issues?
Other days it is an indicator of failure. When you work at eliminating the amount of testing you do for a given release you're bound to choose incorrectly. My preference is to understand why I eliminated a class of testing which would have caught the issue. My concern is that testing that behavior is expected every release with documentation on pass/fail.
Note automation is used and helpful, but if ever test needs to run every release, and releases don't stop just because you're testing, it leaves no time to reduce time.