jfh-bats-mock

Mocking/stubbing library for BATS (Bash Automated Testing System)

This is a fork of bats-mock.

bats-core

There are great things happening in the bats ecosystem! Anyone actively using it should be installing from [bats-core]: https://github.com/bats-core.

Installation

`` sh
npm install --save-dev jfh-bats-mock
`

then in test/test_helper.bash:

` bash
bats_load_library 'jfh-bats-mock'
`

Usage

After loading jfh-bats-mock you have two new functions defined:

- stub: for creating new stubs, along with a plan with expected args and the results to return when called.

- unstub: for cleaning up, and also verifying that the plan was fullfilled.

$3

The stub function takes a program name as its first argument, and any remaining arguments goes into the stub plan, one line per arg.

Each plan line represents an expected invocation, with a list of expected arguments followed by a command to execute in case the arguments matched, separated with a colon:

arg1 arg2 ... : only_run if args matched

The expected args (and the colon) is optional.

So, in order to stub date, we could use something like this in a test case (where format_date is the function under test, relying on data from the date command):

`bash
#!/usr/bin/env bats

load "test_helper"

this is the "code under test"

it would normally be in another file

format_date() {
date -r 222
}

setup() {
_DATE_ARGS='-r 222'
stub date \
"${_DATE_ARGS} : echo 'I am stubbed!'" \
"${_DATE_ARGS} : echo 'Wed Dec 31 18:03:42 CST 1969'"
}

teardown() {
unstub date
}

@test "date format util formats date with expected arguments" {
result="$(format_date)"
[ "$result" == 'I am stubbed!' ]

result="$(format_date)"
[ "$result" == 'Wed Dec 31 18:03:42 CST 1969' ]
}
`

This verifies that format_date indeed called date using the args defined in ${_DATE_ARGS} (which can not be declared in the test-case with local), and made proper use of the output of it.

The plan is verified, one by one, as the calls come in, but the final check that there are no remaining un-met plans at the end is left until the stub is removed with unstub.

$3

Once the test case is done, you should call unstub in order to clean up the temporary files, and make a final check that all the plans have been met for the stub.

How it works

(You may want to know this, if you get weird results there may be stray files lingering about messing with your state.)

Under the covers, bats-mock uses three scripts to manage the stubbed programs/functions.

First, it is the command (or program) itself, which when the stub is created is placed in (or rather, the binstub script is sym-linked to) ${BATS_MOCK_BINDIR}/${program} (which is added to your PATH when loading the stub library). Secondly, it creates a stub plan, based on the arguments passed when creating the stub, and finally, during execution, the command invocations are tracked in a stub run file which is checked once the command is unstub'ed. The ${program}-stub-[plan|run] files are both in ${BATS_MOCK_TMPDIR}.

$3

If you stub functions, make sure to unset them, or the stub script wan't be called, as the function will shadow the binstub script on the PATH`.

Credits

Contributor and maintainer for this fork: [Joerg Heinrich][jfheinrich]

Extracted from the [ruby-build][] test suite. Many thanks to its author and contributors: [Sam Stephenson][sstephenson] and [Mislav Marohnić][mislav].

[ruby-build]: https://github.com/sstephenson/ruby-build
[sstephenson]: https://github.com/sstephenson
[mislav]: https://github.com/mislav
[jfheinrich]: https://jfheinrich.eu