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

mbland / go-script-bash
95%
master: 95%

Build:
Build:
LAST BUILD BRANCH: multiple-script-dirs
DEFAULT BRANCH: master
Repo Added 13 Sep 2016 05:47PM CUT
Files 69
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 bats-v1.0.1
branch: bats-v1.0.1
CHANGE BRANCH
x
Reset
  • bats-v1.0.1
  • appveyor
  • bats-helpers
  • cl-assertions-#181
  • cla-#214
  • cla-#217
  • close-bats-fd-3
  • copy-#184
  • create-fwd-script-#186
  • diff-lib
  • fileutil-module-#184
  • fix-coverage-kcov-v35
  • fix-fileutil-create-dirs-msys2
  • forwarding-script
  • go-template-download
  • issue-template
  • master
  • mirror-dir-#186
  • native-path-#186-#187
  • null
  • path-lib
  • platform-#184
  • platform-freebsd
  • run-script-helpers
  • skip-if-none-present-#186
  • skip-template-test
  • stub-hash-reset
  • tarball-#186
  • v1.6.0
  • v1.7.0
  • walk-#184

pending completion
825

push

travis-ci

mbland
Fix breakage from Bats v1.0.0, bump to Bats v1.0.1

https://github.com/bats-core/bats-core/releases/tag/v1.0.0, while
honoring the same interface as v0.4.0, introduced a few changes that
required some cleanup of our Bats utilities:

- bin/bats is no longer a symlink to libexec/bats, and the latter can no
  longer be invoked directly; hence _GO_BATS_PATH is now set to
  bin/bats.

- TAP output for skipped tests changed in bats-core/bats-core#19.

- run_bats_test_suite_in_isolation depended upon _GO_ROOTDIR and
  _GO_BATS_PATH, which led to bats not being able to find its libexec
  scripts. The bats path is now computed using `command -v bats`, which
  makes the library itself more portable.

- Some assertion-test-helpers output didn't end with a newline. This
  prevented the `while` loop used to replace `sed` in
  bats-core/bats-core#88 from reading the final line of output from the
  test. While this was fixed in bats-core/bats-core#99, updating the
  code to always emit newlines was still the right thing to do.

There was a bug in Bats v1.0.0 in setting `BATS_CWD` that broke the
"assertion-test-helpers: failing assertion must disable shell options"
test case. Specifically, stack trace paths that should've looked like:

  tests/assertion-test-helpers.bash

instead looked like:

  go-script-bash/tests/assertion-test-helpers.bash

This was fixed by bats-core/bats-core#98.

8 of 8 new or added lines in 3 files covered. (100.0%)

3228 of 3398 relevant lines covered (95.0%)

250.03 hits per line

Relevant lines Covered
Build:
Build:
3398 RELEVANT LINES 3228 COVERED LINES
250.03 HITS PER LINE
Source Files on bats-v1.0.1
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Loading...
Coverage∆FileLinesRelevantCoveredMissedHits/Line
No data available in table
Showing 0 to 0 of 0 entries
  • Previous
  • Next

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
825 bats-v1.0.1 Fix breakage from Bats v1.0.0, bump to Bats v1.0.1 https://github.com/bats-core/bats-core/releases/tag/v1.0.0, while honoring the same interface as v0.4.0, introduced a few changes that required some cleanup of our Bats utilities: - bin/bats is ... push 10 Jun 2018 03:52AM CUT mbland travis-ci pending completion  
See All Builds (758)
  • 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