tag:blogger.com,1999:blog-9421494.post1845546734360444684..comments2024-03-27T06:18:38.214-04:00Comments on Lessons Learned by a Software Tester: The Price of ClarityPaulhttp://www.blogger.com/profile/16826575269870573990noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-9421494.post-71128539761766387862009-11-04T04:42:09.167-05:002009-11-04T04:42:09.167-05:00Hi,
Interesting post. Hopefully, we're all pr...Hi,<br /><br />Interesting post. Hopefully, we're all professionals in the development cycle (my utopian wish...), so handing over the status and facts as observed shouldn't be taken as anything more than that.<br /><br />The receiver/s might not like the observations but they can work with you to try and make some meaning of the data (if it's looking at what got missed, why a certain fault appeared or whatever).<br /><br />This analysis should be seen as a two-way communication. It's good feedback to help future design and it helps the testers learning process about the product/system under test (maybe prompting new test ideas or follow-up activities.)<br /><br />BTW, I like your motto - very good to have in mind when reading specs before even getting near the product.Simon Morleyhttps://www.blogger.com/profile/10629592766073538811noreply@blogger.com