Comments on: Build Pattern: Fish-eye Test Suite http://www.magpiebrain.com/blog/2007/01/29/build-pattern-fish-eye-test-suite/ Sam Newman's blog Wed, 08 Oct 2008 06:56:48 +0000 http://wordpress.org/?v=2.5.1 By: sam http://www.magpiebrain.com/blog/2007/01/29/build-pattern-fish-eye-test-suite/#comment-9529 sam Wed, 31 Jan 2007 07:35:52 +0000 http://www.magpiebrain.com/blog/2007/01/29/build-pattern-fish-eye-test-suite/#comment-9529 You guys might have a naming clash - there is already a Python testing tool called protest :-) I'm not taht clear as to how your solution will be able to build in the intellegence of a development team knowing what they'll be working on in the next iteration, but I can understand a system whereby you automatically flag slow tests with poor test coverage or something similar. Anyway, I'll view your progress with interest! You guys might have a naming clash – there is already a Python testing tool called protest :-) I’m not taht clear as to how your solution will be able to build in the intellegence of a development team knowing what they’ll be working on in the next iteration, but I can understand a system whereby you automatically flag slow tests with poor test coverage or something similar.

Anyway, I’ll view your progress with interest!

]]> By: Dennis Byrne http://www.magpiebrain.com/blog/2007/01/29/build-pattern-fish-eye-test-suite/#comment-9480 Dennis Byrne Tue, 30 Jan 2007 23:46:45 +0000 http://www.magpiebrain.com/blog/2007/01/29/build-pattern-fish-eye-test-suite/#comment-9480 Hi Sam, There's bunch of us working on this right now. http://sourceforge.net/projects/protest I've recently implemented an algorithm that builds dynamic JUnit suites based on bytecode dependency graphs. This allows you to determine relevant tests at test time - no more manually maintaining test suites. Kent Spillner has implemented a Condorcet voting implementation in Java ( http://en.wikipedia.org/wiki/Condorcet_method ) that will allow ProTest to combine the intelligence of multiple test suite algorithms to build suites that are designed to fail the fastest. By sorting tests, we want to give developers 90% of the feedback w/ 10% of the costs. Email me if you are interested. Naresh Jain is hacking ant right now so that we can run ProTest in our builds. Hi Sam,

There’s bunch of us working on this right now.

http://sourceforge.net/projects/protest

I’ve recently implemented an algorithm that builds dynamic JUnit suites based on bytecode dependency graphs. This allows you to determine relevant tests at test time – no more manually maintaining test suites. Kent Spillner has implemented a Condorcet voting implementation in Java ( http://en.wikipedia.org/wiki/Condorcet_method ) that will allow ProTest to combine the intelligence of multiple test suite algorithms to build suites that are designed to fail the fastest. By sorting tests, we want to give developers 90% of the feedback w/ 10% of the costs. Email me if you are interested. Naresh Jain is hacking ant right now so that we can run ProTest in our builds.

]]> By: James Mead http://www.magpiebrain.com/blog/2007/01/29/build-pattern-fish-eye-test-suite/#comment-9465 James Mead Tue, 30 Jan 2007 14:55:25 +0000 http://www.magpiebrain.com/blog/2007/01/29/build-pattern-fish-eye-test-suite/#comment-9465 Interesting post, Sam. I'm not sure about the name "Fish-eye Test Suite". Presumably this is drawn from the idea of a fish-eye lens which is an ultra wide-angle lens. Can you explain the metaphor? Interesting post, Sam. I’m not sure about the name “Fish-eye Test Suite”. Presumably this is drawn from the idea of a fish-eye lens which is an ultra wide-angle lens. Can you explain the metaphor?

]]>