Slashdot Mirror

← Back to Stories (view on slashdot.org)

Unit Test Your Aspects

Posted by ScuttleMonkey on from the sounds-like-a-dirty-joke dept.

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."

8 of 130 comments (clear)

  1. hmph by Dominatus · · Score: 3, Funny

    My unit requires no futher testing, thank you very much!

    1. Re:hmph by slackmaster2000 · · Score: 2, Funny

      I try to test my unit at least twice a day. So far no problems have been found, knock on wood (pun!).

  2. I unit test all the programmers I hire... by Anonymous Coward · · Score: 2, Funny

    ...but discard most of them due to faulty design.

      I do inquire if they have any siblings that may be been properly engineered.

  3. Ironic by snevig · · Score: 5, Funny

    There's a javascript error in the article. Line 8, Char 76: Unterminated string constant

  4. How to always get your post on developers.slashdot by hexghost · · Score: 1, Funny

    1. Find an article on a development-oriented site. Possible sites include: www.ibm.com/developerworks, www.macdevcenter.com, devx.com, and persiankitty.com.
    2. Pick a recent article on your chosen site.
    3. Paraphrase the article in a few sentences, or if thats too difficult, just cut and paste the first few sentences of the article.
    4. Post your paraphrase/cut and paste, along with a link to the article, to slashdot.
    5. Bask in the glory as people attribute your ability to find an article with actually knowing what the article is talking about.

  5. Re:Aspect-oriented? by Bloater · · Score: 2, Funny

    > 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.

  6. Re:Thank God for the 2000 tech crash! by shmlco · · Score: 2, Funny

    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.
  7. Re:Unit Testing In The Schools... by dzfoo · · Score: 2, Funny

    >> 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
    ...Can you save Christmas?