tag:blogger.com,1999:blog-8951904624959546499.post6802412120999644907..comments2024-02-22T05:36:59.121-05:00Comments on Test This Blog - Eric Jacobson's Software Testing Blog: Would You Bother Testing This?Eric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-8951904624959546499.post-5358312366558132852011-03-03T03:00:33.793-05:002011-03-03T03:00:33.793-05:00Anonymous Anonymous said...
A key mistake I h...Anonymous Anonymous said...<br /><br /> A key mistake I have noticed in a few companies is that a user reports a fault found within the target environment, while developers try to recreate the in the development environment. Not the same. I would certainly confirm the spelling mistake was corrected, but annotate the report the Bug 100 could not be recreated. Also request the user provide more information.<br /><br /> February 18, 2011 1:42 PM<br /><br /><br />I do this (test in development environment to check if we just missed the bug in the first place)Adminhttps://www.blogger.com/profile/16985058058881135660noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-65356423490738974772011-02-23T19:46:17.759-05:002011-02-23T19:46:17.759-05:00Like Richard, I would want to see the fixed messag...Like Richard, I would want to see the fixed message in the source code before I verified this as fixed. <br /><br />At the end of the day, the retest does not involve actually triggering the error, but simply verifying the spelling of the dialog.JenBnoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-5678566640184228172011-02-18T13:42:07.970-05:002011-02-18T13:42:07.970-05:00A key mistake I have noticed in a few companies is...A key mistake I have noticed in a few companies is that a user reports a fault found within the target environment, while developers try to recreate the in the development environment. Not the same. I would certainly confirm the spelling mistake was corrected, but annotate the report the Bug 100 could not be recreated. Also request the user provide more information.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-45622379296990618112011-02-17T16:32:35.644-05:002011-02-17T16:32:35.644-05:00Still you should automate to avoid future errors.
...Still you should automate to avoid future errors.<br />Just make sure the string is in a resource and write automated tests that spellcheck all string resources.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-54091654728890819302011-02-17T15:31:31.923-05:002011-02-17T15:31:31.923-05:00If I couldn't reproduce the "Larger Issue...If I couldn't reproduce the "Larger Issue", I would mark it as resolved after I took a look at the source code to see if the spelling mistake was corrected.<br /><br />And perhaps I would write a unit test for for the issue if that was possible (or encourage the developer to write the test, depending on the ownership of unit tests on the project).Richard Siemenshttps://www.blogger.com/profile/03080233621640330710noreply@blogger.com