http://blogs.msdn.com/james_whittaker/archive/2008/09/19/the-future-of-software-testing-part-5.aspxVisualization What does software look like? Wouldn’t it be helpful if we had a visualization of software that we could use while the software was being constructed or tested? With a single glance we could see that parts of it remain unfinished. Dependencies,en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/james_whittaker/archive/2008/09/19/the-future-of-software-testing-part-5.aspx#8959316Fri, 19 Sep 2008 22:41:48 GMT91d46819-8472-40ad-a661-2c78acb4018c:8959316 the future of software testing (part 5) : EasyCoded<p>PingBack from <a rel="nofollow" target="_new" href="http://www.easycoded.com/the-future-of-software-testing-part-5/">http://www.easycoded.com/the-future-of-software-testing-part-5/</a></p> http://blogs.msdn.com/james_whittaker/archive/2008/09/19/the-future-of-software-testing-part-5.aspx#8962208Tue, 23 Sep 2008 15:56:57 GMT91d46819-8472-40ad-a661-2c78acb4018c:8962208Team System News<p>James Whittaker on the future of software testing (part 5) AjoyK on Index cards and Team System The...</p> http://blogs.msdn.com/james_whittaker/archive/2008/09/19/the-future-of-software-testing-part-5.aspx#8964990Thu, 25 Sep 2008 16:04:42 GMT91d46819-8472-40ad-a661-2c78acb4018c:8964990bob53050<p>So one thought towards this convergance and engraining of testing into the entire team at least from the design perspective, might be taking design patterns and lining up test patterns right along with them. The two are always discussed separately versus together.</p> <p>Thanks for your blogs and have a great day :)</p> <p>Bob Hanson</p> http://blogs.msdn.com/james_whittaker/archive/2008/09/19/the-future-of-software-testing-part-5.aspx#8992663Thu, 09 Oct 2008 14:26:24 GMT91d46819-8472-40ad-a661-2c78acb4018c:8992663Simon Godfrey<p>James, </p> <p>You’ve got a great knack for posting about issues which are very pertinent to testers at the moment. Virtualisation as a way to display coverage is something which we’re currently starting to look at; primarily because we’re struggling with showing how much coverage we’ve achieved of which areas of a product via any other way. We’re toying with the idea of some kind of graphic map which shows what’s been tested but as you point out, you also need some kind of representation for showing how much testing you’ve done in a particular area and what type of testing that’s been (was it functional, usability, performance etc).</p> <p>I plan to get around to looking into it sometime before Christmas but I hope people read this and reply with ways in which they visualise their testing / coverage because I feel it’s one of the great un-cracked challenges which face testing today.</p> <p>Simon</p> http://blogs.msdn.com/james_whittaker/archive/2008/09/19/the-future-of-software-testing-part-5.aspx#9394618Wed, 04 Feb 2009 08:06:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:9394618Termékinformációk fejlesztőknek<p>[Nacsa S&#225;ndor, 2009. janu&#225;r 13. – febru&#225;r 3.]&amp;#160; A minős&#233;gbiztos&#237;t&#225;s k&#233;rd&#233;sk&#246;re szinte alig ismert</p> http://blogs.msdn.com/james_whittaker/archive/2008/09/19/the-future-of-software-testing-part-5.aspx#9401902Fri, 06 Feb 2009 15:06:23 GMT91d46819-8472-40ad-a661-2c78acb4018c:9401902Termékinformációk fejlesztőknek<p>[ Nacsa S&#225;ndor , 2009. febru&#225;r 6.] Ez a Team System v&#225;ltozat a webalkalmaz&#225;sok &#233;s –szolg&#225;ltat&#225;sok tesztel&#233;s&#233;hez</p>