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

strongloop / strong-globalize
81%
master: 8%

Build:
Build:
LAST BUILD BRANCH: strong-globalize-cli@7.1.0
DEFAULT BRANCH: master
Repo Added 11 Jul 2016 06:31PM UTC
Files 5
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

LAST BUILD ON BRANCH unprune
branch: unprune
CHANGE BRANCH
x
Reset
  • unprune
  • 2.5.4-update
  • 2.5.5-update
  • 2.5.6-update
  • 2.5.7-update
  • 2.5.8-update
  • 2.6.0-update
  • 2.6.1-update
  • 2.6.2-update
  • 2.6.3-update
  • 2.6.4-update
  • 2.6.5-update
  • 2.6.6-update
  • 3.x
  • 3.x-latest
  • 4.x
  • 5.x
  • D-E-modes
  • adv-479
  • alias
  • allow-setting-root-dir
  • aml-update
  • babel-parser
  • blacklist-itself
  • cli-runtime-separation
  • copyright
  • dep-update
  • dremond_espree_change
  • fake-deps
  • fallback-to-md5
  • feat/alias
  • feature/detect-exports
  • fix-issue-127
  • fix-linting
  • fix-logic
  • fix-mem-leak
  • fix-readme
  • fix-string-sub
  • fix-typo-001
  • fix/console-in-browser
  • fix/crash
  • fix/drop-zlib
  • fix/logs-in-browser
  • fix/perf-part1
  • fix/perf-part2
  • fix/phantomjs
  • formatter-perf
  • handle-null-case
  • improve-regex
  • indirect-require
  • inline-deps
  • lodash
  • master
  • new-maintainer
  • null-check
  • remove-bom
  • return-entry
  • revert-some-version-upgrade
  • secure-travis
  • secure-travis-test
  • silent-api
  • simplify-coverage
  • sort-msges
  • strong-globalize-cli@5.0.0
  • strong-globalize-cli@5.0.2
  • strong-globalize-cli@6.0.0
  • strong-globalize-cli@6.0.2
  • strong-globalize-cli@6.0.3
  • strong-globalize-cli@6.0.4
  • strong-globalize-cli@6.0.5
  • strong-globalize-cli@7.0.0
  • strong-globalize-cli@7.0.1
  • strong-globalize-cli@7.0.2
  • strong-globalize-cli@7.0.3
  • strong-globalize-cli@7.0.4
  • strong-globalize-cli@7.0.5
  • strong-globalize-cli@7.1.0
  • strong-globalize-util@4.2.0
  • strong-globalize-util@5.0.0
  • strong-globalize-util@5.0.2
  • strong-globalize-util@5.0.3
  • strong-globalize-util@5.0.4
  • strong-globalize-util@6.0.0
  • strong-globalize-util@6.0.1
  • strong-globalize-util@6.0.2
  • strong-globalize@4.1.2
  • strong-globalize@4.1.4
  • strong-globalize@5.0.0
  • strong-globalize@5.0.2
  • strong-globalize@5.0.3
  • strong-globalize@5.0.4
  • strong-globalize@5.0.5
  • strong-globalize@5.1.0
  • strong-globalize@6.0.0
  • strong-globalize@6.0.1
  • strong-globalize@6.0.2
  • strong-globalize@6.0.3
  • strong-globalize@6.0.4
  • strong-globalize@6.0.5
  • support-nodejs-6x
  • suppress-dots
  • test-help
  • txt-filename
  • update-dep-versions
  • update-deps
  • update-deps-4x
  • update-lockfiles
  • update-package-locks
  • update/dep
  • upgrade-deps
  • use-shelljs
  • v2.5.5
  • v2.5.6
  • v2.5.7
  • v2.5.8
  • v2.6.0
  • v2.6.1
  • v2.6.10
  • v2.6.2
  • v2.6.3
  • v2.6.4
  • v2.6.5
  • v2.6.6
  • v2.6.8
  • v2.6.9
  • v2.7.0
  • v2.8.0
  • v2.8.1
  • v2.8.2
  • v2.8.3
  • v2.8.4
  • v3.0.0
  • v3.1.0
  • v3.2.0
  • v3.3.0
  • v4.0.0
  • v4.0.1
  • v4.0.2
  • v4.1.0
  • v4.1.1
  • v5.1.0

pending completion
133

push

travis-ci

rmg
test: fix empty subtest in TAP output

When run in the master process scenario, the subtest had 0 assertions in
it. The resulting TAP output confuses tap4j causing all sorts of fun.

Only load tap in the child process so that the only TAP that is seen by
the runner is coming from the child process and not double-interpretted
by tap being loaded into the parent process.

This entire test is way more complicated than it should be. I'm not sure
what it is supposed to be testing, but it sure doesn't fit with how
node-tap was meant to work.

1267 of 1565 relevant lines covered (80.96%)

120.38 hits per line

Relevant lines Covered
Build:
Build:
1565 RELEVANT LINES 1267 COVERED LINES
120.38 HITS PER LINE
Source Files on unprune
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
133 unprune test: fix empty subtest in TAP output When run in the master process scenario, the subtest had 0 assertions in it. The resulting TAP output confuses tap4j causing all sorts of fun. Only load tap in the child process so that the only TAP that is ... push 26 Jul 2016 10:44PM UTC rmg travis-ci pending completion  
131 unprune squash! test: fix empty subtest in TAP output Only load tap in the child process so that the only TAP that is seen by the runner is coming from the child process and not double-interpretted by tap being loaded into the parent process. This entir... push 26 Jul 2016 10:21PM UTC rmg travis-ci pending completion  
129 unprune test: fix empty subtest in TAP output When run in the master process scenario, the subtest had 0 assertions in it. The resulting TAP output confuses tap4j causing all sorts of fun. push 26 Jul 2016 09:50PM UTC rmg travis-ci pending completion  
127 unprune fixup! test: don't polute TAP output with test debug push 26 Jul 2016 09:37PM UTC rmg travis-ci pending completion  
125 unprune test: don't polute TAP output with test debug push 26 Jul 2016 09:09PM UTC rmg travis-ci pending completion  
123 unprune remove references to gzip'd CLDR data push 26 Jul 2016 08:52PM UTC rmg travis-ci pending completion  
121 unprune squash! don't prune alternate CLDR formats during install Load json before gz, since it is supported by all platforms. If someone has modified their CLDR payload and not modified the loader for some reason, and are using node 0.12+, then they ca... push 26 Jul 2016 08:34PM UTC rmg travis-ci pending completion  
119 unprune don't prune alternate CLDR formats during install The gains are negligible considering the cost of bandwidth and disk writing has already been paid. Additionally, the postinstall prevents a vanilla 'npm install && npm test && npm publish' workfl... push 26 Jul 2016 08:14PM UTC rmg travis-ci pending completion  
See All Builds (727)
  • Repo on GitHub
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

© 2025 Coveralls, Inc