← Back to team overview

zeitgeist team mailing list archive

[Bug 486996] [NEW] testInsertGetWithoutTimestamp testcase fails

 

Public bug reported:

Running
   python test/resonance-engine-test.py
I get one failed testcase

======================================================================
FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp
    self.assertTrue(ev.timestamp)
AssertionError

----------------------------------------------------------------------

I would have fixed this if I were totally sure what the correct fix is.
Right now the default timestamp of an event is an empty string, which is
why this testcase fails. Is this the expected behaviour, and should we
fix the test. Or should the default timestamp be a string containing the
timestamp of object creation time?

** Affects: zeitgeist
     Importance: Undecided
         Status: New

** Changed in: zeitgeist
    Milestone: None => 0.3

-- 
testInsertGetWithoutTimestamp testcase fails
https://bugs.launchpad.net/bugs/486996
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Engine.

Status in Zeitgeist Engine: New

Bug description:
Running
   python test/resonance-engine-test.py
I get one failed testcase

======================================================================
FAIL: testInsertGetWithoutTimestamp (__main__.ZeitgeistEngineTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/resonance-engine-test.py", line 87, in testInsertGetWithoutTimestamp
    self.assertTrue(ev.timestamp)
AssertionError

----------------------------------------------------------------------

I would have fixed this if I were totally sure what the correct fix is. Right now the default timestamp of an event is an empty string, which is why this testcase fails. Is this the expected behaviour, and should we fix the test. Or should the default timestamp be a string containing the timestamp of object creation time?



Follow ups

References