EWT33 – Let’s date

EWT33 – Let’s date

Date: 28th August 2010
Time: 15:30 – 17:30 UTC

Your boss has assigned you to a very important pre-sales activity. A customer in Nepal would be interested in your application. There is one requirement from the customer that gives your colleagues a headache. Your application shall support Nepali dates in combination to the standard Gregorian calendar. Research the implications for handling Nepali dates, and come up with test cases for the Nepali date support.

Testers: Dr. Meeta Prakash, Michael Larsen, Eusebiu Blindu, Markus Gärtner

Markus Gärtner facilitated the discussion afterwards.

Markus started the discussion to explain how he tackled the problem, and what he would suggest to do. First of changing something fundamental like a calendar implementation is a difficult thing to do. Therefore he proposes to convert entry dates to Gregorian and output dates back to Nepali. In addition, the conversion would be based upon three things: a look-up algorithm like the given example code; discussing the requirement heavily with the customer; and restrict the supported date ranges for the application.

Eusebiu Blindu found it strange that some people change their calendar system each year. He stated that a changing calendar system is not predictable.

Michael Larsen described that the leap year handling in the Gregorian system already provided him a challenge. But changing the month lengths each year overwhelmed him.

The chat transcript can be inspected here.

Image credits: http://farm2.static.flickr.com/1019/1108066858_e3cdb47dca.jpg

About the Author