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

supergiant / supergiant-dashboard / 219 / 1
94%
master: 94%

Build:
DEFAULT BRANCH: master
Ran 19 May 2016 03:48PM UTC
Files 188
Run time 24s
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

18 May 2016 09:22PM UTC coverage: 94.005% (-0.07%) from 94.073%
219.1

push

travis-ci

esmevane
Correctly partition components on app name.

The previous method of approaching component / app sorting was a naive
approach.  It presumed that apps would have more or less distinct names.
That hasn't really been the case, however - so in instances where the
app names were very similar, a given component would appear in multiple
places.

This commit makes a little more of an intelligent guess out of the whole
thing - but ultimately what we really need to do in the long term will
be to organize components in a much more distinct way.  Either we can
give them a better keying interface on the back end or we can invent one
custom to the front-end using the tags feature.

2603 of 2769 relevant lines covered (94.01%)

4.9 hits per line

Source Files on job 219.1
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 219
  • Travis Job 219.1
  • 445e3fab on github
  • Prev Job for on master (#215.1)
  • Next Job for on master (#228.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