• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

redcross / arcdata / 694 / 1
65%
master: 65%

Build:
Build:
LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran 20 Jul 2020 11:58PM UTC
Files 282
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Jul 2020 11:54PM UTC coverage: 64.832%. Remained the same
2.4.6, SAUCE_USERNAME=[secure] SAUCE_ACCESS_KEY=[secure] GOOGLE_MAPS_API_KEY=[secure]

push

travis-ci

frankduncan
Fix #205: Add reason_marked_invalid to incident

Before, the reason an incident was marked invalid was stored in the
incident_type field, which resulted in losing the original incident type
(fire, or vacate, or whatever).  This caused issues when the incident
was reopened, or for reporting.

Instead, we want to have a separate field for the invalid reason that we
display and search on when the incident status is 'invalid'

Issue #205: Create a Response Status field separate from Incident Types

5195 of 8013 relevant lines covered (64.83%)

51.7 hits per line

Source Files on job 694.1 (2.4.6, SAUCE_USERNAME=[secure] SAUCE_ACCESS_KEY=[secure] GOOGLE_MAPS_API_KEY=[secure])
  • Tree
  • List 0
  • Changed 13
  • Source Changed 0
  • Coverage Changed 13
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 568
  • Travis Job 694.1
  • 15618e90 on github
  • Prev Job for 2.4.6, SAUCE_USERNAME=[secure] SAUCE_ACCESS_KEY=[secure] GOOGLE_MAPS_API_KEY=[secure] on 205-create-invalid-reason-field (#693.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc