A brief summary of unit testing

On 11.15.10, In programming, software, By Derek

Unit test checkboxesIn my third of three related postings on some core programming principles, I’ll be talking about unit testing.  In the first part, we discussed code reuse, and in the second, I went over version control.

Unit testing is a methodology by which you run tests on individual bits of your programming code.  I have to admit that this is the topic of the three with which I am the least familiar.  The concept of “testing” in my past jobs has largely been comprised of this:

  • Write your program
  • Test it out as thoroughly as you can when done
  • Turn it over to a user for them to test thoroughly.

This is actually a very broad generalization, and I would, in fact, test out bits of code that I wrote as I wrote them, making sure that functions returned the desired results before I was anywhere near to having a final product.  While this is a step in the right direction towards unit testing, it is no means formal unit testing. (more…)

Tagged with: • • •
 
0 Comments
Leave A Response

Controlling your code through versioning

On 11.11.10, In programming, software, By Derek

Version ControlIn my last posting, I talked about the benefits of code reuse and how any good programmer should swear by that coding principle.  Today, I move on to another key programming methodology, that of version control.

Version control (revision control, source control, or any of a number of other similar names) is a method for archiving and documenting changes to programming code, web pages, XML files, and, frankly, any other type of file of which you might want to store multiple versions in one centralized location.  A benefit of this is that multiple programmers can work on the same code base without interfering with each other, and that you can easily track or back out changes to a file and go back to an earlier version, should a new change cause problems. (more…)

Tagged with: • • • •
 
0 Comments
Leave A Response

A matter of principles

On 11.10.10, In programming, By Derek

zeroes and onesIn the more than a decade that I’ve been programming, I’ve found that there are three programming principles that I really wish were included in the computer science program that I enrolled in during the late 1990s:

  • Code reuse (the DRY principle)
  • Implementing version control
  • Unit testing your code

There’s really no excuse for these topics not being covered, but it perhaps reflects upon how the academic world differs from the professional business world.  Academia considers you successful if you’ve studied all sorts of general aspects of computer science, while success in the business world requires following general coding principles, and not necessarily a grasping a thorough understanding of say, machine code or Artificial Intelligence (of course, my argument falls apart if you are designing computer processors, robotics, or video games!).

Covering all three topics in one article would be a bit much, so I’m going to split this up over the course of a few days. (more…)

Tagged with: • • •
 
1 Comments
Leave A Response

An apologetic old program

On 04.26.10, In programming, By Derek

This gave me a good chuckle — I ran into this recently on the old systems I still work on (yes, this comes from a terminal session!):

          Transaction Editing Database
              Charge Batch Proof

THIS ACTIVITY PROVIDES DETAIL VOUCHER INFORMATION BY
SELECTED BATCH NUMBER(S).

     HOW DO YOU WANT YOUR BATCH PROOF SORTED
               A. BY NUMBER
               B. BY PATIENT

          PLEASE SELECT A OR B : B

Sorry this portion of the program is being fixed !!!

Please selection A from the option menu.

Thank you for using the TE Batch Proof System

In short, I selected option B, only to be presented with the last three lines above.  This program first apologizes that B is not a working option and is currently being fixed (which is news to me – the last time I can tell that any programmer did any significant work to it was 10 years ago).  Then, it directs me to option A (why even bother listing an option B in the first place?).  And then perhaps my favorite part, it thanks me for using this system, apparently not realizing that it neglected to produce any useful output for me.

So, apparently, what we can learn from this is that if you don’t plan to eventually finish your program, at least make it sound like a pleasant convenience store worker.

Tagged with: •
 
0 Comments
Leave A Response

Making a splash… page.

On 03.08.10, In web design, By Derek

Splash of waterIf you were with us last time, we were discussing the numbering of a product called Studio Enterprise by Component One.  I raised some concerns about their versioning scheme, stating that it likely would raise lots of confusion among their userbase.  This time, I’d like to focus on a splash page on their site that is advertising this product.  Again, let me make the disclaimer that I am not reviewing the product itself or making any claims about it being good or bad.  I’m simply using the advertising on their site as a lesson in web design.

Since there’s a good chance the page will eventually come down or change (as it is, after all, advertising a product labeled “2009″, and the last time I checked, we were well into the year 2010), here is a small screenshot of the splash page in question (if this link does eventually kick the metaphorical bucket, just imagine this image blown up to 960 pixels wide and 1050 pixels tall):

Splage page ad

The splash page advertising Studio Enterprise 2009 v3.

(more…)

Tagged with: •
 
0 Comments
Leave A Response
« Previous Entries
Go To Top »