octoleo/hosts
1
0
Fork 0
mirror of https://github.com/octoleo/hosts.git synced 2024-11-11 07:40:56 +00:00
Code Releases Activity
17b2615820
hosts/test/add.bats

183 lines
6.2 KiB
Plaintext
Raw Normal View History

Add add.bats.
2016-01-27 02:08:18 +00:00
#!/usr/bin/env bats
load test_helper
# `hosts add` #################################################################
@test "\`add\` with no arguments exits with status 1." {
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
[[ ${status} -eq 1 ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
@test "\`add\` with no argument does not change the hosts file." {
_original="$(cat "${HOSTS_PATH}")"
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add add.bats.
2016-01-27 02:08:18 +00:00
[[ "$(cat "${HOSTS_PATH}")" == "${_original}" ]]
}
@test "\`add\` with no arguments prints help information." {
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add add.bats.
2016-01-27 02:08:18 +00:00
[[ "${lines[0]}" == "Usage:" ]]
Update help/usage formatting.
2016-01-27 04:25:16 +00:00
[[ "${lines[1]}" == " hosts add <ip> <hostname> [<comment>]" ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
# `hosts add <ip>` ############################################################
@test "\`add <ip>\` exits with status 1." {
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add 0.0.0.0
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
[[ ${status} -eq 1 ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
@test "\`add <ip>\` does not change the hosts file." {
_original="$(cat "${HOSTS_PATH}")"
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add 0.0.0.0
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add add.bats.
2016-01-27 02:08:18 +00:00
[[ "$(cat "${HOSTS_PATH}")" == "${_original}" ]]
}
@test "\`add <ip>\` prints help information." {
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add 0.0.0.0
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add add.bats.
2016-01-27 02:08:18 +00:00
[[ "${lines[0]}" == "Please include a hostname" ]]
[[ "${lines[1]}" == "Usage:" ]]
Update help/usage formatting.
2016-01-27 04:25:16 +00:00
[[ "${lines[2]}" == " hosts add <ip> <hostname> [<comment>]" ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
# `hosts add <ip> <hostname>` #################################################
@test "\`add <ip> <hostname>\` exits with status 0." {
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add 0.0.0.0 example.com
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
[[ ${status} -eq 0 ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
@test "\`add <ip> <hostname>\` adds the entry to the hosts file." {
_original="$(cat "${HOSTS_PATH}")"
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add 0.0.0.0 example.com
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add add.bats.
2016-01-27 02:08:18 +00:00
_compare "${_original}" "$(cat "${HOSTS_PATH}")"
_compare '0.0.0.0 example.com' "$(sed -n '11p' "${HOSTS_PATH}")"
[[ "$(cat "${HOSTS_PATH}")" != "${_original}" ]]
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == "0.0.0.0 example.com" ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
@test "\`add <ip> <hostname>\` prints feedback." {
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" add 0.0.0.0 example.com
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add add.bats.
2016-01-27 02:08:18 +00:00
[[ "${lines[0]}" == "Added:" ]]
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
[[ "${lines[1]}" == "0.0.0.0 example.com" ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
Add tests for duplicate entry guard. Deplicate entries are avoided by a guard in the `add` subcommand. Add tests to ensure that duplicate entries are not created.
2019-05-29 01:18:29 +00:00
@test "\`add <ip> <hostname>\` doesn't add duplicate entry." {
_original="$(cat "${HOSTS_PATH}")"
{
run "${_HOSTS}" add 0.0.0.0 example.com
}
_modified="$(cat "${HOSTS_PATH}")"
run "${_HOSTS}" add 0.0.0.0 example.com
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
_compare "${_original}" "$(cat "${HOSTS_PATH}")"
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
_compare '0.0.0.0 example.com' "$(sed -n '11p' "${HOSTS_PATH}")"
Add tests for duplicate entry guard. Deplicate entries are avoided by a guard in the `add` subcommand. Add tests to ensure that duplicate entries are not created.
2019-05-29 01:18:29 +00:00
[[ "$(cat "${HOSTS_PATH}")" != "${_original}" ]]
[[ "$(cat "${HOSTS_PATH}")" == "${_modified}" ]]
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == "0.0.0.0 example.com" ]]
Add tests for duplicate entry guard. Deplicate entries are avoided by a guard in the `add` subcommand. Add tests to ensure that duplicate entries are not created.
2019-05-29 01:18:29 +00:00
}
Add add.bats.
2016-01-27 02:08:18 +00:00
# `hosts add <ip> <hostname> [comment]` #######################################
@test "\`add <ip> <hostname> [comment]\` exits with status 0." {
Test `add` with multi-word comment.
2018-05-15 01:53:06 +00:00
run "${_HOSTS}" add 0.0.0.0 example.com 'Example multi-word comment.'
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
[[ ${status} -eq 0 ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
@test "\`add <ip> <hostname> [comment]\` adds the entry to the hosts file." {
_original="$(cat "${HOSTS_PATH}")"
Test `add` with multi-word comment.
2018-05-15 01:53:06 +00:00
run "${_HOSTS}" add 0.0.0.0 example.com 'Example multi-word comment.'
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add add.bats.
2016-01-27 02:08:18 +00:00
[[ "$(cat "${HOSTS_PATH}")" != "${_original}" ]]
Test `add` with multi-word comment.
2018-05-15 01:53:06 +00:00
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == \
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
"0.0.0.0 example.com # Example multi-word comment." ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
Add tests for duplicate entry guard. Deplicate entries are avoided by a guard in the `add` subcommand. Add tests to ensure that duplicate entries are not created.
2019-05-29 01:18:29 +00:00
@test "\`add <ip> <hostname> [comment]\` doesn't add duplicate entry." {
_original="$(cat "${HOSTS_PATH}")"
{
run "${_HOSTS}" add 0.0.0.0 example.com
}
_modified="$(cat "${HOSTS_PATH}")"
run "${_HOSTS}" add 0.0.0.0 example.com 'Example multi-word comment.'
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
_compare "${_original}" "$(cat "${HOSTS_PATH}")"
_compare '0.0.0.0 example.com' "$(sed -n '11p' "${HOSTS_PATH}")"
[[ "$(cat "${HOSTS_PATH}")" != "${_original}" ]]
[[ "$(cat "${HOSTS_PATH}")" == "${_modified}" ]]
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == "0.0.0.0 example.com" ]]
Add tests for duplicate entry guard. Deplicate entries are avoided by a guard in the `add` subcommand. Add tests to ensure that duplicate entries are not created.
2019-05-29 01:18:29 +00:00
[[ "$(sed -n '11p' "${HOSTS_PATH}")" != \
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
"0.0.0.0 example.com # Example multi-word comment." ]]
Add tests for duplicate entry guard. Deplicate entries are avoided by a guard in the `add` subcommand. Add tests to ensure that duplicate entries are not created.
2019-05-29 01:18:29 +00:00
}
@test "\`add <ip> <hostname> [comment]\` doesn't add duplicate commented entry." {
_original="$(cat "${HOSTS_PATH}")"
{
run "${_HOSTS}" add 0.0.0.0 example.com 'Example multi-word comment.'
}
_modified="$(cat "${HOSTS_PATH}")"
run "${_HOSTS}" add 0.0.0.0 example.com 'Example multi-word comment.'
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
_compare "${_original}" "$(cat "${HOSTS_PATH}")"
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
_compare '0.0.0.0 example.com' "$(sed -n '11p' "${HOSTS_PATH}")"
Add tests for duplicate entry guard. Deplicate entries are avoided by a guard in the `add` subcommand. Add tests to ensure that duplicate entries are not created.
2019-05-29 01:18:29 +00:00
[[ "$(cat "${HOSTS_PATH}")" != "${_original}" ]]
[[ "$(cat "${HOSTS_PATH}")" == "${_modified}" ]]
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == \
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
"0.0.0.0 example.com # Example multi-word comment." ]]
Add tests for duplicate entry guard. Deplicate entries are avoided by a guard in the `add` subcommand. Add tests to ensure that duplicate entries are not created.
2019-05-29 01:18:29 +00:00
}
Add add.bats.
2016-01-27 02:08:18 +00:00
@test "\`add <ip> <hostname> [comment]\` prints feedback." {
Test `add` with multi-word comment.
2018-05-15 01:53:06 +00:00
run "${_HOSTS}" add 0.0.0.0 example.com 'Example multi-word comment.'
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add add.bats.
2016-01-27 02:08:18 +00:00
[[ "${lines[0]}" == "Added:" ]]
Improve `add` formatting.
2020-04-09 00:27:11 +00:00
[[ "${lines[1]}" == "0.0.0.0 example.com # Example multi-word comment." ]]
Add add.bats.
2016-01-27 02:08:18 +00:00
}
Add help tests to add.bats.
2016-01-27 03:01:02 +00:00
# help ########################################################################
@test "\`help add\` exits with status 0." {
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" help add
[[ ${status} -eq 0 ]]
Add help tests to add.bats.
2016-01-27 03:01:02 +00:00
}
@test "\`help add\` prints help information." {
Use braces in all variable references. Braces are only required in certain cases, but the cognitive overhead in keeping track of which cases require braces can be reduced by simply always using them. Example: `${NAME}` Retain more widely-used braces `$NAME` convention in documentation.
2016-02-24 02:14:21 +00:00
run "${_HOSTS}" help add
Use explicit escaping for "\\n" newlines. Backslash is literal, so explicitly escape it rather than rely on fallback behavior. ShellCheck SC1117 https://github.com/koalaman/shellcheck/wiki/SC1117
2018-04-15 21:55:26 +00:00
printf "\${status}: %s\\n" "${status}"
printf "\${output}: '%s'\\n" "${output}"
Add help tests to add.bats.
2016-01-27 03:01:02 +00:00
[[ "${lines[0]}" == "Usage:" ]]
Update help/usage formatting.
2016-01-27 04:25:16 +00:00
[[ "${lines[1]}" == " hosts add <ip> <hostname> [<comment>]" ]]
Add help tests to add.bats.
2016-01-27 03:01:02 +00:00
}
Copy Permalink