Comments on: MTEST update, plus Help Browser integration info http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/ Steve Eddins manages the Image & Geospatial development team at The MathWorks and coauthored Digital Image Processing Using MATLAB. He writes here about image processing concepts, algorithm implementations, and MATLAB. Fri, 10 Feb 2012 18:55:59 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Steve http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/#comment-21584 Steve Thu, 19 Mar 2009 12:57:56 +0000 http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/#comment-21584 James—That's a lot of changes to try all at once! Test-driven development and object-oriented programming both take some getting used to. Some programmers find that development pace actually speeds up with test-driven development, because the fraction of time spent debugging goes way down. But that's only after you have some experience with the technique, and only if you get in the habit of making code changes in small, rapid increments. James—That’s a lot of changes to try all at once! Test-driven development and object-oriented programming both take some getting used to. Some programmers find that development pace actually speeds up with test-driven development, because the fraction of time spent debugging goes way down. But that’s only after you have some experience with the technique, and only if you get in the habit of making code changes in small, rapid increments.

]]> By: James Ong http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/#comment-21583 James Ong Thu, 19 Mar 2009 12:51:16 +0000 http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/#comment-21583 Ah, then I'll change my test functions to not use assertAlmostEqual any more. By the way, your post on MTEST and refactoring made me read through the books "Test-driven development" (Beck) and "Refactoring" (Fowler) plus try programming MATLAB in an object oriented way. I'm still assessing the advantages and disadvantages for my work, but the most obvious at the moment are: - the code is more robust than I'm used to - the development time is somewhat slower than I'm used to Ah, then I’ll change my test functions to not use assertAlmostEqual any more.

By the way, your post on MTEST and refactoring made me read through the books “Test-driven development” (Beck) and “Refactoring” (Fowler) plus try programming MATLAB in an object oriented way. I’m still assessing the advantages and disadvantages for my work, but the most obvious at the moment are:
- the code is more robust than I’m used to
- the development time is somewhat slower than I’m used to

]]> By: Steve http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/#comment-21582 Steve Thu, 19 Mar 2009 12:45:05 +0000 http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/#comment-21582 James—Yes, assertAlmostEqual has disappeared from the main documentation. That was intentional. The explanation is in the first paragraph of this post. I have the new floating-point comparison functions assertElementsAlmostEqual and assertVectorsAlmostEqual. I left assertAlmostEqual there to avoid making an incompatible change, but I would prefer that people use the new functions. James—Yes, assertAlmostEqual has disappeared from the main documentation. That was intentional. The explanation is in the first paragraph of this post. I have the new floating-point comparison functions assertElementsAlmostEqual and assertVectorsAlmostEqual. I left assertAlmostEqual there to avoid making an incompatible change, but I would prefer that people use the new functions.

]]> By: James Ong http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/#comment-21581 James Ong Thu, 19 Mar 2009 12:26:41 +0000 http://blogs.mathworks.com/steve/2009/03/19/mtest-update-plus-help-browser-integration-info/#comment-21581 Is is just me, or has AssertAlmostEqual disappeared from the main documentation of mtest? Is is just me, or has AssertAlmostEqual disappeared from the main documentation of mtest?

]]>