If you want to make your unit tests look huge: just enable runtime theming in the DUnit GUI runner. It only runs 15 to 20 times slower then. lol

-
If you want to make your unit tests look huge: just enable runtime theming in the DUnit GUI runner. It only runs 15 to 20 times slower then. lol

Comments

  1. Roman YankovskyJune 11, 2014 at 10:50 AM

    Theming is a new sleep() ?

    ReplyDelete
  2. mezenJune 11, 2014 at 11:07 AM

    That reminds me on sleep(1000); after each item on a splash screen which is loaded, so the user can read what is loaded.

    ReplyDelete
  3. Stefan GlienkeJune 11, 2014 at 12:38 PM

    Ancient times when there were only 3 items to load and to make it look busy ;)

    ReplyDelete
  4. Nicholas RingJune 11, 2014 at 1:09 PM

    Have to remember this, as it is the length of time for the tests to run that indicates how well things are tested (or the amount of coverage done by unit tests), right? It has nothing to do with the actual tests at all, does it?  ;-)

    ReplyDelete
  5. Vincent ParrettJune 11, 2014 at 3:27 PM

    LOL! good one.

    ReplyDelete
  6. Bill MeyerJune 12, 2014 at 4:50 AM

    Speed is overrated anyway.

    ReplyDelete
  7. Giacomo Degli EspostiJune 13, 2014 at 2:24 AM

    A slower test must be way better then a faster one: if it's so slow, this means its' testing a lot of things! :)
    More seriously: fast tests are important if you are adopting continuous integration and tests are part of your commit/checkin operations.

    ReplyDelete
  8. Stefan MeisnerJune 25, 2014 at 10:40 AM

    I am always adding some sleeps to unit tests to work around threading issues like race conditions. All tests are green. Just kidding ;)

    ReplyDelete

Post a Comment