Comments on: I Want a Platypus Too http://third-bit.com/blog/archives/1517.html Data is ones and zeroes | Software is ones and zeroes and hard work. Fri, 03 Feb 2012 17:07:30 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jan http://third-bit.com/blog/archives/1517.html#comment-1698 Jan Tue, 06 May 2008 10:18:59 +0000 http://pyre.third-bit.com/blog/archives/1517.html#comment-1698 Testing (beyond Unit Testing) really goes hand in hand with deployment. To test a system it needs to be running in reasonably realistic environment. However that means testing is tied to your deployment platform. If you're willing to take the hit the system can very tight like Microsoft Visual Studio Team System. But then you have moved away from the 'lowest common denominator' approach that is hallmark of good software. Something that might hit a sweet spot (an idea I tried implementing for TRAC, but then the sun came out) is a unified logging system. Just like TRAC supports very handy wiki links to parts of your code. I part-build a system that allows links back from log files (presented inside TRAC's wiki system) back to the code that scribed them. ...everyone needs logging! Testing (beyond Unit Testing) really goes hand in hand with deployment. To test a system it needs to be running in reasonably realistic environment.

However that means testing is tied to your deployment platform. If you’re willing to take the hit the system can very tight like Microsoft Visual Studio Team System.

But then you have moved away from the ‘lowest common denominator’ approach that is hallmark of good software.

Something that might hit a sweet spot (an idea I tried implementing for TRAC, but then the sun came out) is a unified logging system. Just like TRAC supports very handy wiki links to parts of your code. I part-build a system that allows links back from log files (presented inside TRAC’s wiki system) back to the code that scribed them.

…everyone needs logging!

]]> By: Greg Wilson http://third-bit.com/blog/archives/1517.html#comment-1697 Greg Wilson Sat, 03 May 2008 00:29:36 +0000 http://pyre.third-bit.com/blog/archives/1517.html#comment-1697 @Pekka: I think there's a misunderstanding: I'm not trying to test DrProject itself, I'm trying to provide tools in DrProject that will help people with the testing of whatever application(s) they're using DrProject to help develop. @Pekka: I think there’s a misunderstanding: I’m not trying to test DrProject itself, I’m trying to provide tools in DrProject that will help people with the testing of whatever application(s) they’re using DrProject to help develop.

]]> By: Pekka Laukkanen http://third-bit.com/blog/archives/1517.html#comment-1696 Pekka Laukkanen Sat, 03 May 2008 00:25:48 +0000 http://pyre.third-bit.com/blog/archives/1517.html#comment-1696 Since you probably have generic interfaces (web, database, etc.) you should be able to use existing open source test tools. If your system is testable you shouldn't need much more. Since you probably have generic interfaces (web, database, etc.) you should be able to use existing open source test tools. If your system is testable you shouldn’t need much more.

]]> By: Greg Wilson http://third-bit.com/blog/archives/1517.html#comment-1695 Greg Wilson Fri, 02 May 2008 21:56:01 +0000 http://pyre.third-bit.com/blog/archives/1517.html#comment-1695 @Pekka: I agree systems should be designed for testability; I was wondering what tools like DrProject can provide to help with the actual testing. @Pekka: I agree systems should be designed for testability; I was wondering what tools like DrProject can provide to help with the actual testing.

]]> By: Pekka Laukkanen http://third-bit.com/blog/archives/1517.html#comment-1694 Pekka Laukkanen Fri, 02 May 2008 21:48:39 +0000 http://pyre.third-bit.com/blog/archives/1517.html#comment-1694 Adding support for testing mainly means making your system testable. It is surprisingly easy when you think about it before the implementation but hard to do after the fact. For web systems it is often enough to add clear and non-changing identifiers for all your widgets (including labels). I recommend reading Bret Pettichord's excellent paper Design for Testability for more information. You can get it from http://www.io.com/%7Ewazmo/papers/design_for_testability_PNSQC.pdf Adding support for testing mainly means making your system testable. It is surprisingly easy when you think about it before the implementation but hard to do after the fact. For web systems it is often enough to add clear and non-changing identifiers for all your widgets (including labels). I recommend reading Bret Pettichord’s excellent paper Design for Testability for more information. You can get it from http://www.io.com/%7Ewazmo/papers/design_for_testability_PNSQC.pdf

]]>