Share your knowledge at the LQ Wiki.
Go Back > Forums > Non-*NIX Forums > Programming
User Name
Programming This forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.


  Search this Thread
Old 09-25-2014, 04:21 AM   #1
Registered: Oct 2011
Posts: 75

Rep: Reputation: Disabled
How do you write unittest code to test the code like getDateOfYesterday?

Like you write a function to return the date of yesterday,Nomatter what language we use, Let me take python language as the example,
the code as below:
def getDateOfYesterday():
    agodate      = + datetime.timedelta(-1)
    agodate      = "%04d%02d%02d" % (agodate.year, agodate.month,
    return agodate
If I want to write code to unittest this function, The way I could figure out is to hard coded the expected return value,
class Test_getDateOfYesterday(unittest.TestCase):
    def test_1(self):
        onedayago = getDateOfYesterday
        self.assertEqual("20140924", onedayago, "")
But then everytime I need to run this unittest, I have to modify the expected return date to pass this unittest.
It's tedious.
If I don't hard coded the expected return date, then I need to write another code to verify this function.
Then what if the another code has the same fault as this function has?
Could somebody explain some theory which unittest such situation?
This question has bothered me a long time.
Hope I explain the problem clearly, and Thanks in advance.
Old 09-25-2014, 07:52 AM   #2
Registered: Mar 2011
Location: MA, USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu, Debian
Posts: 7,214
Blog Entries: 12

Rep: Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656Reputation: 2656
The problem is that you've coded with an absolute string and are not considering variability of the input.

A proper unit test first examines all possible input values; including illegal values and all possible output values.

To properly unit test something you should be testing all possible input values which can be sent to that module, or the best representation of values you can conceive of and you should automate the testing better.

Two ways I might approach this, and I would use both ways for a full and complete test:
  1. Alter system date in iteration to cause the output of to be a broad range of values and test iteratively
  2. Replace the possible values that agodate could be with test table data and test iteratively
In all cases, you should have a table of expected results which you compare against when you write your test function.

I would use both methods, but lean more on method #2 for the following reasons. In method #1, your system is only going to accept legal dates, and providing the library function now() works, which it does, then you're always only ever going to test legal date strings and therefore fail to test illegal date strings. Using method #2 you can cause incorrect input and verify that your module rejects or does no continued harm.

Either case, in writing your test harness, you do not hard code the expected result, you instead contrive a variety of inputs as broadly defined as you can and you also code expected outputs or behaviors from the module under test and then you run the test program and generate a report.
Old 09-25-2014, 08:15 AM   #3
Registered: Aug 2008
Distribution: Slackware
Posts: 492

Rep: Reputation: 210Reputation: 210Reputation: 210
One solution is to add a _now argument to getDateOfYesterday, e.g.:
def getDateOfYesterday(_now=None):
    if _now is None:
        _now =
    _now += datetime.timedelta(-1)
    return "%04d%02d%02d" % (_now.year, _now.month,
and then use it in tests. You can also create a separate function:
def getDateOfPrevDay(now):
    now += datetime.timedelta(-1)
    return "%04d%02d%02d" % (now.year, now.month,

def getDateOfYesterday():
    return getDateOfPrevDay(
and test it instead of getDateOfYesterday.

A bit more complicated approach, but one that does not require the module you are testing to be changed, is to mock method. Unfortunately, datetime.datetime is a built-in type so you have to mock the whole thing:
import datetime
import unittest

def getDateOfYesterday():
    dt =
    dt += datetime.timedelta(-1)
    return "%04d%02d%02d" % (dt.year, dt.month,

class DateTimeMock(object):

    original_datetime = datetime.datetime
    _now =

    def now(self):
        return self._now

    def setNow(self, *args, **kw):
        self._now = self.original_datetime(*args, **kw)

class TestCase(unittest.TestCase):

    def _setNow(self, *args, **kw):
        self._dt_mock.setNow(*args, **kw)

    def setUp(self):
        self._dt_mock = DateTimeMock()
        datetime.datetime = self._dt_mock

    def tearDown(self):
        datetime.datetime = self._dt_mock.original_datetime

    def testGetDateOfYesterday(self):
        self._setNow(2014, 9, 20)
        self.assertEqual('20140919', getDateOfYesterday())

        self._setNow(2013, 9, 20)
        self.assertEqual('20130919', getDateOfYesterday())

if __name__ == '__main__':

Last edited by mina86; 10-01-2014 at 02:09 PM.
1 members found this post helpful.
Old 09-25-2014, 08:53 PM   #4
Registered: Oct 2011
Posts: 75

Original Poster
Rep: Reputation: Disabled
mina86, Thanks for your patient explanation and the example code, That's really helpful, Your view open my mind and expand my view too. I really appreciate your help. Thanks again.
Old 09-25-2014, 09:02 PM   #5
LQ Guru
Registered: Nov 2003
Location: Canada
Distribution: Slackware
Posts: 8,496

Rep: Reputation: 3523Reputation: 3523Reputation: 3523Reputation: 3523Reputation: 3523Reputation: 3523Reputation: 3523Reputation: 3523Reputation: 3523Reputation: 3523Reputation: 3523
Honestly, I'd just rewrite the function to return the day before the date that's passed in.

def getDateOfYesterday(today):
    agodate      = today + datetime.timedelta(-1)
    agodate      = "%04d%02d%02d" % (agodate.year, agodate.month,
    return agodate
And then you use it with:

Much more versatile, and much more testable.

Last edited by dugan; 09-25-2014 at 09:06 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
how do I test the return code value Glenn D. Linux - Software 2 01-28-2011 09:34 AM
What is the fastest way to compile, if none, to test android code/OS changes? archieval Linux - Mobile 0 09-17-2010 09:40 PM
LXer: Keeping score in test-driven development with Python, PyLint, unittest, doctest LXer Syndicated Linux News 0 11-12-2009 03:10 PM
Test php code on Apache backpacker Linux - Newbie 3 12-17-2005 05:14 AM
User Preferences: Use HTML code instead of vB code? (vB code is overrated) stefanlasiewski LQ Suggestions & Feedback 5 07-26-2005 02:37 AM > Forums > Non-*NIX Forums > Programming

All times are GMT -5. The time now is 11:49 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration