Skip to content

fix minor typos #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 29, 2017
Merged

fix minor typos #33

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -313,7 +313,7 @@ Running test_code_does_not_write_this_in_the_file... SUCCESS

Checks for a precise status code of the evaluation of *assertion*.

It may be usefull if you want to distinguish between several error conditions in your code.
It may be useful if you want to distinguish between several error conditions in your code.

In case of failure, the standard output and error of the evaluated *assertion* is displayed. The optional message is also displayed.

Expand Down Expand Up @@ -385,7 +385,7 @@ Running test_obvious_inequality_with_assert_not_equals... SUCCESS

fake <command> [replacement code]

Fakes *command* and replaces it with *replacement code* (if code is specified) for the rest of the execution of your test. If no replacement code is specified, then it replaces command by one that echoes stdin of fake. This may be usefull if you need to simulate an environment for you code under test.
Fakes *command* and replaces it with *replacement code* (if code is specified) for the rest of the execution of your test. If no replacement code is specified, then it replaces command by one that echoes stdin of fake. This may be useful if you need to simulate an environment for you code under test.

For instance:

Expand Down Expand Up @@ -520,7 +520,7 @@ overriden by a function. For instance if your code under test relies on *exec* t

*fake* stores parameters given to the fake in the global variable *FAKE_PARAMS* so that you can use them inside your fake.

It may be usefull if you need to adapt the behavior on the given parameters.
It may be useful if you need to adapt the behavior on the given parameters.

It can also help in asserting the values of these parameters... but this may be quite tricky.

Expand Down
2 changes: 1 addition & 1 deletion bash_unit
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ usage() {
echo "$0 [-f <output format>] [-p <pattern1>] [-p <pattern2>]... <test_file1> <test_file2>..." >&2
echo >&2
echo "Runs tests in test files that match <pattern>s" >&2
echo "<output format> is optionnal only supported value is tap" >&2
echo "<output format> is optional only supported value is tap" >&2
echo "-v to get current version information" >&2
echo "See https://github.com/pgrange/bash_unit" >&2
exit 1
Expand Down