1
91%
master: 90%

Ran 28 Dec 2017 05:12PM UTC

Files 197

Run time 16s

Badge

Embed ▾

Committed 28 Dec 2017 04:51PM UTC coverage: 90.579% (+0.07%) from 90.512%

Job # 2.3.4

Build Type

push

travis-ci

Committed by

val99erie

Commit Message

Make sure fields get marked as dirty if they change. Story #122

I overrode the getter and setter methods for the ordered fields to keep
track of their order in secondary fields, but that caused a problem.
Even though those fields appeared to be correct in the UI, I noticed
that the `description` and `ordered_descriptions` fields were out of
sync in the fedora console.

The overrides to the getters and setters messed up the logic that
determines whether or not a field is marked dirty.

I wrote a spec to make sure that both the original field and its
secondary ordering field will be marked dirty if the field is updated,
and then moved the `super` call to the top of the setter method, which
solves the problem with the logic for dirtiness.

Run Details

2740 of 3025 relevant lines covered (90.58%)

107.18 hits per line

curationexperts / epigaea / 2332 / 1
91%
master: 90%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 2332.1 (2.3.4)

curationexperts / epigaea / 2332 / 1 91% master: 90%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 2332.1 (2.3.4)

curationexperts / epigaea / 2332 / 1
91%
master: 90%

README BADGES
x