octoleo/hosts
1
0
Fork 0
mirror of https://github.com/octoleo/hosts.git synced 2024-11-10 23:31:04 +00:00
Code Releases Activity
b44f3b8fe0
hosts/test/remove.bats

228 lines
6.7 KiB
Plaintext
Raw Normal View History

Add remove.bats.
2016-01-27 03:35:04 +00:00
#!/usr/bin/env bats
load test_helper
# `hosts remove` #################################################################
@test "\`remove\` 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}" remove
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 remove.bats.
2016-01-27 03:35:04 +00:00
}
@test "\`remove\` 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}" remove
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 remove.bats.
2016-01-27 03:35:04 +00:00
[[ "$(cat "${HOSTS_PATH}")" == "${_original}" ]]
}
@test "\`remove\` 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}" remove
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 remove.bats.
2016-01-27 03:35:04 +00:00
[[ "${lines[0]}" == "Usage:" ]]
Update help/usage formatting.
2016-01-27 04:25:16 +00:00
[[ "${lines[1]}" == " hosts remove (<ip> | <hostname> | <search string>) [--force]" ]]
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
Test argument with no match in remove.bats.
2016-01-27 04:17:55 +00:00
# `hosts remove <invalid> --force` ############################################
@test "\`remove <invalid> --force\` 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 example.com
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
Test argument with no match in remove.bats.
2016-01-27 04:17:55 +00:00
}
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}" remove 127.0.0.3 --force
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 ]]
Test argument with no match in remove.bats.
2016-01-27 04:17:55 +00:00
}
@test "\`remove <invalid> --force\` prints error message." {
{
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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
Test argument with no match in remove.bats.
2016-01-27 04:17:55 +00:00
}
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}" remove 127.0.0.3 --force
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
[[ ${output} == "No matching records found." ]]
Test argument with no match in remove.bats.
2016-01-27 04:17:55 +00:00
}
Add remove.bats.
2016-01-27 03:35:04 +00:00
# `hosts remove <ip> --force` #################################################
@test "\`remove <ip> --force\` 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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
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}" remove 127.0.0.2 --force
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 remove.bats.
2016-01-27 03:35:04 +00:00
}
@test "\`remove <ip> --force\` updates the hosts file." {
{
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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
_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}" remove 127.0.0.2 --force
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 remove.bats.
2016-01-27 03:35:04 +00:00
_compare "${_original}" "$(cat "${HOSTS_PATH}")"
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == "0.0.0.0 example.com" ]]
[[ "$(sed -n '12p' "${HOSTS_PATH}")" == "0.0.0.0 example.net" ]]
[[ "$(sed -n '13p' "${HOSTS_PATH}")" == "" ]]
}
@test "\`remove <ip>\` removes all matches." {
{
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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 0.0.0.0 example.dev
run "${_HOSTS}" add 127.0.0.2 example.com
run "${_HOSTS}" disable example.dev
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
_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}" remove 0.0.0.0 --force
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 remove.bats.
2016-01-27 03:35:04 +00:00
_expected="\
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
127.0.0.2 example.com"
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
_compare "'${_expected}'" "'$(cat "${HOSTS_PATH}")'"
[[ "$(cat "${HOSTS_PATH}")" != "${_original}" ]]
[[ "$(cat "${HOSTS_PATH}")" == "${_expected}" ]]
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
@test "\`remove <ip>\` 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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
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}" remove 127.0.0.2 --force
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 remove.bats.
2016-01-27 03:35:04 +00:00
[[ "${lines[0]}" == "Removed:" ]]
[[ "${lines[1]}" == "127.0.0.2 example.com" ]]
}
# `hosts remove <hostname> --force` ###########################################
@test "\`remove <hostname> --force\` 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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
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}" remove example.com --force
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 remove.bats.
2016-01-27 03:35:04 +00:00
}
@test "\`remove <hostname> --force\` updates the hosts file." {
{
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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
_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}" remove example.com --force
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 remove.bats.
2016-01-27 03:35:04 +00:00
_compare "${_original}" "$(cat "${HOSTS_PATH}")"
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == "0.0.0.0 example.net" ]]
[[ "$(sed -n '12p' "${HOSTS_PATH}")" == "" ]]
}
@test "\`remove <hostname>\` removes all matches." {
{
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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 0.0.0.0 example.dev
run "${_HOSTS}" add 127.0.0.2 example.com
run "${_HOSTS}" disable example.dev
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
_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}" remove example.com --force
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 remove.bats.
2016-01-27 03:35:04 +00:00
_expected="\
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
0.0.0.0 example.net
#disabled: 0.0.0.0 example.dev"
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
_compare "'${_expected}'" "'$(cat "${HOSTS_PATH}")'"
[[ "$(cat "${HOSTS_PATH}")" != "${_original}" ]]
[[ "$(cat "${HOSTS_PATH}")" == "${_expected}" ]]
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
@test "\`remove <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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
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}" remove example.com --force
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 remove.bats.
2016-01-27 03:35:04 +00:00
_expected="\
Removed:
0.0.0.0 example.com
127.0.0.2 example.com"
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
[[ "${output}" == "${_expected}" ]]
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
# help ########################################################################
@test "\`help remove\` 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 remove
[[ ${status} -eq 0 ]]
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
@test "\`help remove\` 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 remove
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 remove.bats.
2016-01-27 03:35:04 +00:00
[[ "${lines[0]}" == "Usage:" ]]
Update help/usage formatting.
2016-01-27 04:25:16 +00:00
[[ "${lines[1]}" == " hosts remove (<ip> | <hostname> | <search string>) [--force]" ]]
Add remove.bats.
2016-01-27 03:35:04 +00:00
}
Copy Permalink