Previous Next        Current Page: NeXtMidas Training / Primitives / Test Macros / Lamest Reasons for not Testing
back
+ Start Here   
+ Background   
+ Common Midas Concepts   
+ Getting Started - Part 1   
+ Getting Started - Part 2   
+ Working with Files   
+ Option Trees   
+ Macros - Part 1 (Basics)   
+ Macros - Part 2 (Graphics)   
+ NetBeans - Part 1 (Setup)   
+ NetBeans - Part 2 (GUIs)   
+ NetBeans - Part 3 (Profiler)   
+ Eclipse - Part 1 (Setup)   
+ Eclipse - Part 2 (GUIs)   
- Primitives   
   + Overview   
   + Open, Process, Close   
   + Building   
   + The NeXtMidas API   
   + Lab 1   
   + Special Variables   
   + Lab 2   
   + Lab 3*   
   + Files in a Primitive   
   + Lab 4   
   + Lab 5*   
   - Test Macros   
      - Introduction to Test Macros   
      - Lamest Reasons for not Testing   
      - Creating a Test Macro   
      - Test Strategy   
      - Layout of a Test Macro   
   + Lab 6   
   + Real Time Controls   
   + Lab 7   
   + Working with Messages   
   + Lab 8   
   + Primitive Restarts   
   + Introduction to DSP   
   + Lab 9   
   - Commands executing commands   
+ WebStart   
+ Maps & Imagery   
+ X-Midas Interoperability   
+ RMIF & Remoting   
+ Installing NeXtMidas   
+ Support & Maintenance   
+ File Handlers   
  • For your amusement...
    • The lamest excuses for not testing a primitive:
      My primitive tests itself.
      (Unless it is BLD or UNITTEST, this isn't the case)
      I tested it when I wrote it.
      (And someone modifies it 6 months from now and...)
      It works on my system.
      (The field system is missing some old bug fixes)
      My code is bug-free.
      (Yes, keep telling yourself that...)
      My dog ate it.
      (Didn't work then, doesn't work now)
    • A few valid exceptions where automated testing doesn't work well:
      Graphics and user interfaces.
      (Must be manually tested)
      Network interfaces.
      (Testable, but requires setup)
      Error handling.
      (Some errors are extremely hard to reproduce)
back