tag:blogger.com,1999:blog-8951904624959546499.post4107072132612357224..comments2024-02-22T05:36:59.121-05:00Comments on Test This Blog - Eric Jacobson's Software Testing Blog: Sometimes I Feel Good as a TesterEric Jacobsonhttp://www.blogger.com/profile/08216361684596485033noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8951904624959546499.post-52700710436815718622009-07-20T12:45:04.847-04:002009-07-20T12:45:04.847-04:00Michael,
Thanks for catching me on the whole &quo...Michael,<br /><br />Thanks for catching me on the whole "ready for production" thing.<br /><br /><i>There's also a problem with this one: "One (or more) of my tests failed; therefore the product is of low quality." Can you spot it?<br /></i><br /><br />Sure. First, you have to make sure the test itself does not have a bug. Next, it depends on how much the stakeholders value what the test verifys.Eric Jacobsonhttps://www.blogger.com/profile/08216361684596485033noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-41345149467828621742009-07-20T10:05:06.173-04:002009-07-20T10:05:06.173-04:00I think the following would also be a high for the...I think the following would also be a high for the tester.<br />1) Challenging/Outdoing the Business Analyst in terms of how the application functions and demonstrating the knowledge gleaned (through many hours of study/testing) in terms of correct application behaviour. <br />2) Being very organised in terms of information gathered via study, investigation and analysis and bugs logged which is demonstrated by quickly coming up with information on the fly or being able to say relate steps "x" with bug "y". <br />3) The application area previously tested by a tester being voted clean by the customer. <br />4) Customer commending the knowledge / contribution by testing team/tester.Sandeep Maherhttp://bugmaniac.wordpress.com/noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-71002577937257382952009-07-19T10:26:22.811-04:002009-07-19T10:26:22.811-04:00A dev cannot test their own code after integration...<i>A dev cannot test their own code after integration because they don’t understand how the application works in its entirety.</i><br /><br />That on its own is an important test result.<br /><br /><i>The project manager looks at me and asks which parts of the release are ready for prod. I have an answer prepared with tests and bugs to back me up.</i><br /><br />The tests and bugs are really important information, but I would hope that your reply <i>doesn't</i> include an answer as to whether it's ready for production. That's a business decision, to which the test report is information. There's other information to be considered.<br /><br /><i>I write a program that provides valuable feedback, on the quality state of an AUT, after running unattended.</i><br /><br />How do you do that? Quality isn't something that a machine can tell you about, since it's a relationship between the product and some person. In addition, as testers, we must beware of <a rel="nofollow">affirming the consequent</a>. "All my tests pass, therefore the program is of high quality." Can you see the problem in that statement? There's also a problem with this one: "One (or more) of my tests failed; therefore the product is of low quality." Can you spot it?<br /><br />All that said, one thing that makes <i>me</i> happy as a tester is seeing other testers describe how they go about their work. Good on you, Eric!<br /><br />---Michael B.Michael Bolton http://www.developsense.comhttps://www.blogger.com/profile/09027725699187903416noreply@blogger.comtag:blogger.com,1999:blog-8951904624959546499.post-58230941566814279862009-07-17T17:53:43.390-04:002009-07-17T17:53:43.390-04:00When a release goes out and the majority of 'b...When a release goes out and the majority of 'bugs' found are PEBKAC errors or spelling mistakes.dezhttp://iamdez.comnoreply@blogger.com