tag:blogger.com,1999:blog-6156777091769109824.post1496959926489399614..comments2024-02-22T07:21:56.298+02:00Comments on The Adventures of a Space Monkey: Test Planning - GranularitySami Söderblomhttp://www.blogger.com/profile/06690577772285551526noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6156777091769109824.post-74050170088440947512017-03-24T08:36:28.468+02:002017-03-24T08:36:28.468+02:00nice blog about testing planning
how to read pro...nice blog about testing planning <br /><a href="http://www.readmebro.com/how-to-read-product-dimensions/" rel="nofollow"> how to read product dimensions </a>Mary Klipyardhttps://www.blogger.com/profile/11728260987250797366noreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-78430036729460891492011-06-20T16:01:21.088+03:002011-06-20T16:01:21.088+03:00Hi Juha,
I have nothing against test cases, but I...Hi Juha,<br /><br />I have nothing against test cases, but I consider the term to be dangerous as such. They represent scripted testing where specific means to find bugs are written to the benefit of testing even though the benefit should be given directly to development, so that those bugs wouldn't happen in the first place.<br /><br />The same goes to unit testing. I consider that purely as development activity, as I do mostly about intergration testing too, and there's a whole different range of rules there. Development needs specific planning a lot more than testing.<br /><br />And again the same goes with customer complaints, pilot and acceptance findings, etc. They all should be built in development regression, automated as much as it is possible/needed, where as in user level regression planning should be on higher level, leaving room for natural variation.<br /><br />SamiSami Söderblomhttps://www.blogger.com/profile/06690577772285551526noreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-25254503923379775192011-06-19T21:26:33.153+03:002011-06-19T21:26:33.153+03:00Your method is good for new products, but what abo...Your method is good for new products, but what about projects that have already been shipped out?<br />Customer complains are often turned into testcases and those test cases are classified as part of regression testing, so that they would never reappear in shipped products.<br />Regression testing as a whole will be resource intensive (regardlress whether you are doing it manually or you have automated it) and rarely find new bugs, but when bugs are found, they probably have to be fixed as well.<br />It is also impossible to do unit testing without testcases. Of course we can question, whether test code alone is valid documentation for testcase, but you must have unique identifier for each unit test so that you know where to start debugging, if/when one of them fails.Juha Ylitalohttps://www.blogger.com/profile/15278995969505164783noreply@blogger.comtag:blogger.com,1999:blog-6156777091769109824.post-60241175901533596482011-06-17T00:40:45.151+03:002011-06-17T00:40:45.151+03:00What about planning for regression testing?
Regres...What about planning for regression testing?<br />Regression testing takes lot of resources and will rarely produce new bug reports, but when you find bugs in regression testing, they are something that must be fixed before next release.<br />AFAIK many companies also have policy, which says that customers' bug reports must be transformed into testcases that will be executed as part of regression testing.Juha Ylitalohttps://www.blogger.com/profile/15278995969505164783noreply@blogger.com