Tuesday, March 25, 2014

10 Most Controversial Programming Opinions

What's your most controversial programming opinion?

  1. Programmers who don't code in their spare time for fun will never become as good as those that do.
  2. The only "best practice" you should be using all the time is "Use Your Brain".
  3. Most comments in code are in fact a pernicious form of code duplication.
  4. XML is highly overrated.
  5. Not all programmers are created equal.
  6. If you only know one language, no matter how well you know it, you're not a great programmer.
  7. Performance does matter.
  8. Print statements are a valid way to debug code.
  9. Your job is to put yourself out of work.
  10. Getters and Setters are Highly Overused.

Tuesday, March 11, 2014

Getting the most out of Fitnesse Suites

Fitnesse offers the ability to use scripts inside tests and suites as well as use REST calls following their API. This is handy because it gives us the chance to write JavaScript hacks to improve the utility of Fitnesse.

One of the fundamental problems I have with Fitnesse is maintaining the state of tests. Often times, requirements change, and tests need updating. It's easy for Fitnesse tests to get left behind when you need to meet deliverables and updating your tests requires a great deal of effort. Luckily, the Fitnesse API has some features we can take advantage of to get a glimpse at the last execution of tests.

When writing a suite, I will create tables to put similar tests together. I start with the test name, then a description, and the current status. The script uses the test name to query the restful service, which returns the latest test result and populates the status cell based on the result.


  • Allows to skip running the suite, which can be time consuming on the machine it is running (as well as blocking for other test suites)
  • Get immediate results for each test instead of waiting for the suite
  • Easier to navigate than the suite test page


  • Slows loading of the suite page because ajax calls have to be made.
  • Script is very simple that this doesn't provide much useful info, just a broad overview.


To use this script in your suite, you need to make a few changes:

1. Update the ajax url parameter with your url, leading up to the suite with the following period. As long as the testnames in the first table column are valid, it will automatically populate the current status column with the last data.


<!--[if lt IE 7 ]> <span id="ie" class="ie6"></span> <![endif]-->
<!--[if IE 7 ]>    <span id="ie" class="ie7"></span> <![endif]-->
<!--[if IE 8 ]>    <span id="ie" class="ie8"></span> <![endif]-->
<!--[if IE 9 ]>    <span id="ie" class="ie9"></span> <![endif]-->
<!--[if (gt IE 9)|!(IE)]><!--> <span id="ie" class=""></span> <!--<![endif]-->
"use strict";
// These values count up each of the tests statuses. Display for a summary of the suite.
var passingTests = 0;
var failedTests = 0;
var exceptionTests = 0;
var ignoredTests = 0;

$( document ).ready(function() {
// For each tr that is not the first
$('table tr:not(:first-child) td:first-child').each(function() {
// get the name of the test out (from >Test Name)
var testname = $(this).text().substring(1);

// Make the rest call
$.ajax({ url: "http://yoururl.yourSuite."+testname+"?pageHistory&resultDate=latest&format=xml", cache: false, type: "GET", dataType: "xml", context: this, success: function(data) { var output = ""; //IE doesn't support innerHTML element if($("#ie").is('.ie6, .ie7, .ie8, .ie9')){ var correct = $(data).find("counts")[0].firstChild.text; var wrong = $(data).find("counts")[0].firstChild.nextSibling.text; var ignored = $(data).find("counts")[0].firstChild.nextSibling.nextSibling.text; var exception = $(data).find("counts")[0].firstChild.nextSibling.nextSibling.nextSibling.text; } else { // For everyone else - Note, you'll have to update the 
// childNodes unless you follow the same table setup I use.
var correct = $(data).find("counts")[0].childNodes[1].innerHTML; 
var wrong = $(data).find("counts")[0].childNodes[3].innerHTML;
var ignored = $(data).find("counts")[0].childNodes[5].innerHTML;
var exception = $(data).find("counts")[0].childNodes[7].innerHTML;

// Count all the values
output += "<span class=\"correct\">right: " + correct + "</span><br/>"; if(wrong != "0") { output += "<span class=\"wrong\">wrong: " + wrong + "</span><br/>"; $(this).closest("tr").addClass("testFailed"); } if(wrong != "0" && exception == "0"){ failedTests++; } if(ignored != "0"){ output += "<span class=\"ignored\">ignored: " + ignored + "</span><br/>"; ignoredTests++; } if(exception != "0"){ output += "<span class=\"exception\">exception: "+ exception +"</span>"; $(this).closest("tr").addClass("testException"); exceptionTests++; } if(wrong == "0" && exception == "0" && correct != "0") { passingTests++; $(this).closest("tr").addClass("testPassed"); } // Append to status td $(this).closest("td").next().next().append(output); } }); }); }); </script>


.testPassed {

.testFailed {

.testException {

.correct { 

.wrong { 

.exception { 

.ignored { 

2016 Update: I wrote this when I was a beginner in Javascript. The code is very hacky, because the table html is generated by Fitnesse, making it hard to grab them via jQuery. This script could be improved upon by:

  • Adding last date of test run to each test, so the user has an idea of how stale the test run is.
  • Not using this, and instead just using Jenkins to run Fitnesse suites and see results in Jenkins.
  • Adding expandables on each test row to see exception text or errors.

Monday, March 3, 2014

How to renew your blogger domain name

  1.  Go to admin.google.com, Sign in using your Google Apps credentials, username@yourdomain.com (not your gmail account!) -- I think the usernames default to "bloggeradmin@yourdomain.com"
  2. If you still can't get in, go to  https://admin.google.com/yourdomainname.com/ForgotAdminAccountInfo
  3. Once you submit a password reset, check your gmail linked to the account for the password reset.
  4. Log in using new credentials, go to Billing section
  5. Activate automatic renewal for domain registration.
I followed these steps and had this expired domain back up and running in about 15 minutes!