Slashdot Mirror
Unit Test Your Aspects
An anonymous reader writes "The widespread adoption of programmer testing over the past five years has been driven by the demonstrable productivity and quality of the resulting code. Find out why and how to do it, as this article introduces you to the benefits of testing aspect-oriented code and presents a catalog of patterns for testing crosscutting behavior in AspectJ."
My unit requires no futher testing, thank you very much!
...but discard most of them due to faulty design.
I do inquire if they have any siblings that may be been properly engineered.
There's a javascript error in the article. Line 8, Char 76: Unterminated string constant
> you could write the debug message in a separate function or file, and then via aspect-oriented programming not include code to call it in every single function. Instead you'd define an aspect, or something, and have your debug message print whenever the situation that defines that aspect occurs.
Is that like intercals "COME FROM" construct.
I actually had a degreed developer tell me, with a straight face, that he didn't do testing, as his professor told him it's the job of the QA department...
Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
>> http://frayspace.com/toomuchtv/isntthatgood/merryf unday.html
Simple reason:
C/C++ programmers: It works, dammit! We don't need no stinkin' testing.
C# programmers: The compiler would warn or fail if it didn't work; if anything goes wrong in production, we'll patch it in the next release.
Visual Basic programmers: Uh... testing? wuzzat?
-dZ.
Carol vs. Ghost