1
92%
master: 89%

Ran 19 Nov 2014 10:34AM UTC

Files 52

Run time 23s

Badge

Embed ▾

Committed 19 Nov 2014 10:25AM UTC coverage: 91.633% (+0.004%) from 91.629%

Job # SKIP_VIRUS_SCAN=1 SKIP_SPLINTER_TESTS=1 MONGO_REPLICA_SET='' NO_AUTOPEP8=1

Build Type

push

travis-ci

Committed by

tombooth

Commit Message

Migrate mocked batch test to integration test

In order to fully test whether batching last update works it should
really test against mongo.

There is some pretty weird looking comparison due to there being a few
100 microsecond deviation between the time I wrote into mongo and the
time that was extracted out. I've copied and pasted a failed run with
direct comparison below:

```
FAIL:
tests.core.storage.test_mongo.TestMongoStorageEngine.test_batch_last_updated
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/var/apps/backdrop/venv/local/lib/python2.7/site-packages/nose/case.py",
line 197, in runTest
    self.test(*self.arg)
  File "/var/apps/backdrop/tests/core/storage/test_mongo.py", line 47,
in test_batch_last_updated
    assert_that(data_set.get_last_updated(), is_(timestamp))
AssertionError:
Expected: <2014-11-19 10:16:24.772844+00:00>
     but: was <2014-11-19 10:16:24.772000+00:00>
```

I would hypothesis that this is down to the difference between the
underlying representation used to store the datetimes, but I haven't had
the time to look deeply into it.

Run Details

1807 of 1972 relevant lines covered (91.63%)

0.92 hits per line

alphagov / backdrop / 2024 / 1
92%
master: 89%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 2024.1 (SKIP_VIRUS_SCAN=1 SKIP_SPLINTER_TESTS=1 MONGO_REPLICA_SET='' NO_AUTOPEP8=1)

alphagov / backdrop / 2024 / 1 92% master: 89%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 2024.1 (SKIP_VIRUS_SCAN=1 SKIP_SPLINTER_TESTS=1 MONGO_REPLICA_SET='' NO_AUTOPEP8=1)

alphagov / backdrop / 2024 / 1
92%
master: 89%

README BADGES
x