Comments for Teknologika - The software testing blog of Bruce McLeod http://www.teknologika.com/blog Saving the world, one testcase at a time Mon, 19 Sep 2011 05:03:58 +0000 hourly 1 http://wordpress.org/?v=3.2.1 Comment on The problems with software testing by Halperinko - Kobi Halperinhttp://www.teknologika.com/blog/the-problems-with-software-testing/comment-page-1/#comment-32612 Halperinko - Kobi Halperin Mon, 19 Sep 2011 05:03:58 +0000 http://www.teknologika.com/blog/?p=639#comment-32612 <p>Upfront Test Cases are valuable in verifying that testers organize in parallel to requirement & design process, and are the best tools to give feedback to these activities. As we know, the earlier we find the faults the lower the cost - so Upfront Test Cases are of great value. With that said, it does not mean one has to document procedures to finest details, nor that these test cases are final - they should be taken as guidelines to build above. Anyhow - my take is that any tests written for a new product should be put aside right after they pass, and be replaced with tests written for regression (complicated scenarios covering a lot of ground, vs. atomic test cases which are required in early unstable stages)</p> Upfront Test Cases are valuable in verifying that testers organize in parallel to requirement & design process, and are the best tools to give feedback to these activities. As we know, the earlier we find the faults the lower the cost – so Upfront Test Cases are of great value. With that said, it does not mean one has to document procedures to finest details, nor that these test cases are final – they should be taken as guidelines to build above. Anyhow – my take is that any tests written for a new product should be put aside right after they pass, and be replaced with tests written for regression (complicated scenarios covering a lot of ground, vs. atomic test cases which are required in early unstable stages)

]]> Comment on The tester is dead! Long live the SDE/T by Brucehttp://www.teknologika.com/blog/the-tester-is-dead-long-live-the-sdet/comment-page-1/#comment-31905 Bruce Tue, 06 Sep 2011 20:58:32 +0000 http://www.teknologika.com/blog/TheTesterIsDeadLongLiveTheSDET.aspx#comment-31905 <p>Jose. I it is how the programming knowledge is applied that is important, and being able to code, talk to developers and be a great tester do not preclude you from being a customer advocate.</p><p>If you think that I have said "if you cannot program you cannot test, then you have mis understood the meaning behind the post.</p> Jose. I it is how the programming knowledge is applied that is important, and being able to code, talk to developers and be a great tester do not preclude you from being a customer advocate.

If you think that I have said “if you cannot program you cannot test, then you have mis understood the meaning behind the post.

]]> Comment on The tester is dead! Long live the SDE/T by Josehttp://www.teknologika.com/blog/the-tester-is-dead-long-live-the-sdet/comment-page-1/#comment-31887 Jose Tue, 06 Sep 2011 15:46:04 +0000 http://www.teknologika.com/blog/TheTesterIsDeadLongLiveTheSDET.aspx#comment-31887 <p>If you can programm you cannot test. Ying and yang. Positive and negative. Create and destroy. Shiva and Visnu. A 'technical tester' is a 'contradictio in terminis' (latin adagio). Like a "honorable prostitute".</p><p>The tester is the user (read 'the client'). Not a developer, not a manager, not a technical consultant, not... .Just the final customer. Period. The only thing is that he is experienced in techniques to find out in a short period of time, how things could go wrong in the tool. And point them clear and positive.</p><p>This is a bad web, because it brings confusion. I thought you were a tester. You are not. So you should put this "The tester is dead! Long live the SDE/T" in the vey begining of your site, so every tester can read it first, and don't waste anymore time. Time, for testers, is precious. But you cannot understand it, honorable.</p> If you can programm you cannot test. Ying and yang. Positive and negative. Create and destroy. Shiva and Visnu. A ‘technical tester’ is a ‘contradictio in terminis’ (latin adagio). Like a “honorable prostitute”.

The tester is the user (read ‘the client’). Not a developer, not a manager, not a technical consultant, not… .Just the final customer. Period. The only thing is that he is experienced in techniques to find out in a short period of time, how things could go wrong in the tool. And point them clear and positive.

This is a bad web, because it brings confusion. I thought you were a tester. You are not. So you should put this “The tester is dead! Long live the SDE/T” in the vey begining of your site, so every tester can read it first, and don’t waste anymore time. Time, for testers, is precious. But you cannot understand it, honorable.

]]> Comment on The problems with software testing by Lisa Davidsonhttp://www.teknologika.com/blog/the-problems-with-software-testing/comment-page-1/#comment-31570 Lisa Davidson Fri, 02 Sep 2011 06:50:40 +0000 http://www.teknologika.com/blog/?p=639#comment-31570 <p>Well, In my view QA Testing is a way to ensure that your product or application are meeting the required criteria and good enough to reach the target audience. It requires expertise, an eye to detail, if testing goes wrong then there is a big issue but then QA testing can only go wrong if it is in wrong hands. It is always advisable to have an independent software testing partner to ensure things proceed in the right directions.</p> Well, In my view QA Testing is a way to ensure that your product or application are meeting the required criteria and good enough to reach the target audience. It requires expertise, an eye to detail, if testing goes wrong then there is a big issue but then QA testing can only go wrong if it is in wrong hands. It is always advisable to have an independent software testing partner to ensure things proceed in the right directions.

]]> Comment on Testing Stax – Parkcalc sample is now available by Brucehttp://www.teknologika.com/blog/testing-stax-parkcalc-sample-is-now-available/comment-page-1/#comment-30468 Bruce Wed, 17 Aug 2011 11:32:53 +0000 http://www.teknologika.com/blog/?p=619#comment-30468 <p>Sorry but I don't know of a similar framework that has been built in Java. A java port to use selenium 2 instead of WatiN is something that I might do at some point in the future if the need arises at work, but at this stage I don't think so.</p><p>Regards,</p><p>Bruce</p> Sorry but I don’t know of a similar framework that has been built in Java. A java port to use selenium 2 instead of WatiN is something that I might do at some point in the future if the need arises at work, but at this stage I don’t think so.

Regards,

Bruce

]]> Comment on Testing Stax – Parkcalc sample is now available by Junior Testerhttp://www.teknologika.com/blog/testing-stax-parkcalc-sample-is-now-available/comment-page-1/#comment-30467 Junior Tester Wed, 17 Aug 2011 11:28:48 +0000 http://www.teknologika.com/blog/?p=619#comment-30467 <p>Hi Bruce. Just wondering, do you happen to know of a framework similar to STAX but implemented in JAVA instead of C# .Net?</p> Hi Bruce. Just wondering, do you happen to know of a framework similar to STAX but implemented in JAVA instead of C# .Net?

]]> Comment on Walking the test documentation tightrope. by Show #2 – Automation Evolution | Testcast is a software testing podcast with Bruce Mcleod and Trish Khoohttp://www.teknologika.com/blog/walking-the-test-documentation-tightrope/comment-page-1/#comment-25354 Show #2 – Automation Evolution | Testcast is a software testing podcast with Bruce Mcleod and Trish Khoo Thu, 09 Jun 2011 13:10:41 +0000 http://www.teknologika.com/blog/WalkingTheTestDocumentationTightrope.aspx#comment-25354 <p>[...] Some test case design smarts by Bruce: Walking the test documentation tightrope [...]</p> [...] Some test case design smarts by Bruce: Walking the test documentation tightrope [...]

]]> Comment on The 5 stages of the developer-test relationship by Infographic: The Five Stages of the Developer-Tester Relationship | Software Testing Bloghttp://www.teknologika.com/blog/the-5-stages-of-the-developer-test-relationship/comment-page-1/#comment-23408 Infographic: The Five Stages of the Developer-Tester Relationship | Software Testing Blog Fri, 13 May 2011 15:47:44 +0000 http://www.teknologika.com/blog/The5StagesOfTheDevelopertestRelationship.aspx#comment-23408 <p>[...] and developers. It was created by Bruce McLeod, author of  the Teknologika blog. He also wrote an accompanying blog post explaining this image in more [...]</p> [...] and developers. It was created by Bruce McLeod, author of  the Teknologika blog. He also wrote an accompanying blog post explaining this image in more [...]

]]> Comment on The 5 stages of the developer tester relationship infographic by Michael Hadjigeorgiouhttp://www.teknologika.com/blog/the-5-stages-of-the-developer-tester-relationship-infographic/comment-page-1/#comment-23290 Michael Hadjigeorgiou Thu, 12 May 2011 02:16:17 +0000 http://www.teknologika.com/blog/?p=611#comment-23290 <p>Great Wall Feature Bruce :)</p> Great Wall Feature Bruce :)

]]> Comment on Using Monte Carlo simulation and bug fix rates to calculate when the product will ship by Vanithahttp://www.teknologika.com/blog/using-monte-carlo-simulation-and-bug-fix-rates-to-calculate-when-the-product-will-ship/comment-page-1/#comment-18300 Vanitha Tue, 08 Feb 2011 18:29:21 +0000 http://www.teknologika.com/blog/?p=481#comment-18300 <p>I am confused with the if and as well as using count if function. Can you please share the excel spreadsheet?</p><p>Thanks</p> I am confused with the if and as well as using count if function. Can you please share the excel spreadsheet?

Thanks

]]>