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

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

Build:
Build:
LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran 11 Jul 2020 03:50PM UTC
Files 282
Run time 16s
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

11 Jul 2020 03:44PM UTC coverage: 64.854%. First build
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

5200 of 8018 relevant lines covered (64.85%)

51.35 hits per line

Source Files on job 691.1 (2.4.6, SAUCE_USERNAME=[secure] SAUCE_ACCESS_KEY=[secure] GOOGLE_MAPS_API_KEY=[secure])
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 565
  • Travis Job 691.1
  • f943aa31 on github
  • Next 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