Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions README.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -158,9 +158,9 @@ Write your test functions in a file. The name of a test function has to start wi

Use the *bash_unit* assertion functions in your test functions, see below.

You may write a *setup* function that will be exectuted before each test is run.
You may write a *setup* function that will be executed before each test is run.

You may write a *teardown* function that will be exectuted after each test is run.
You may write a *teardown* function that will be executed after each test is run.

You may write a *setup_suite* function that will be executed only once before all the tests of your test file.

Expand Down
4 changes: 2 additions & 2 deletions docs/man/man1/bash_unit.1
Original file line number Diff line number Diff line change
Expand Up @@ -182,9 +182,9 @@ Write your test functions in a file. The name of a test function has to start wi
.sp
Use the \fBbash_unit\fP assertion functions in your test functions, see below.
.sp
You may write a \fBsetup\fP function that will be exectuted before each test is run.
You may write a \fBsetup\fP function that will be executed before each test is run.
.sp
You may write a \fBteardown\fP function that will be exectuted after each test is run.
You may write a \fBteardown\fP function that will be executed after each test is run.
.sp
You may write a \fBsetup_suite\fP function that will be executed only once before all the tests of your test file.
.sp
Expand Down