octoleo/hosts
1
0
Fork 0
mirror of https://github.com/octoleo/hosts.git synced 2024-11-11 15:50:58 +00:00
Code Releases Activity
05ba7bdc03
hosts/test/enable.bats

206 lines
6.3 KiB
Plaintext
Raw Normal View History

Add enable.bats.
2016-01-27 02:50:43 +00:00
#!/usr/bin/env bats
load test_helper
# `hosts enable` ##############################################################
@test "\`enable\` 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}" enable
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
[[ ${status} -eq 1 ]]
Add enable.bats.
2016-01-27 02:50:43 +00:00
}
@test "\`enable\` 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}" enable
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add enable.bats.
2016-01-27 02:50:43 +00:00
[[ "$(cat "${HOSTS_PATH}")" == "${_original}" ]]
}
@test "\`enable\` 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}" enable
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add enable.bats.
2016-01-27 02:50:43 +00:00
[[ "${lines[0]}" == "Usage:" ]]
Update help/usage formatting.
2016-01-27 04:25:16 +00:00
[[ "${lines[1]}" == " hosts enable (<ip> | <hostname> | <search string>)" ]]
Add enable.bats.
2016-01-27 02:50:43 +00:00
}
# `hosts enable <ip>` #########################################################
@test "\`enable <ip>\` 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
run "${_HOSTS}" disable 127.0.0.2
Add enable.bats.
2016-01-27 02:50:43 +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}" enable 127.0.0.2
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
[[ ${status} -eq 0 ]]
Add enable.bats.
2016-01-27 02:50:43 +00:00
}
@test "\`enable <ip>\` 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
run "${_HOSTS}" disable 0.0.0.0
run "${_HOSTS}" disable 127.0.0.2
Add enable.bats.
2016-01-27 02:50:43 +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}" enable 127.0.0.2
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add enable.bats.
2016-01-27 02:50:43 +00:00
_compare "${_original}" "$(cat "${HOSTS_PATH}")"
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == "#disabled: 0.0.0.0 example.com" ]]
[[ "$(sed -n '12p' "${HOSTS_PATH}")" == "#disabled: 0.0.0.0 example.net" ]]
[[ "$(sed -n '13p' "${HOSTS_PATH}")" == "127.0.0.2 example.com" ]]
}
@test "\`enable <ip>\` enables 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 127.0.0.2 example.com
run "${_HOSTS}" disable 0.0.0.0
run "${_HOSTS}" disable 127.0.0.2
Add enable.bats.
2016-01-27 02:50:43 +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}" enable 0.0.0.0
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add enable.bats.
2016-01-27 02:50:43 +00:00
_compare \
"${_original}" \
"$(cat "${HOSTS_PATH}")"
_compare \
"'0.0.0.0 example.com'" \
"'$(sed -n '11p' "${HOSTS_PATH}")'"
_compare \
"'0.0.0.0 example.net'" \
"'$(sed -n '12p' "${HOSTS_PATH}")'"
_compare \
"'#disabled: 127.0.0.2 example.com'" \
"'$(sed -n '13p' "${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}")" == "#disabled: 127.0.0.2 example.com" ]]
}
@test "\`disable <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
run "${_HOSTS}" disable 127.0.0.2
Add enable.bats.
2016-01-27 02:50:43 +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}" enable 127.0.0.2
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add enable.bats.
2016-01-27 02:50:43 +00:00
[[ "${lines[0]}" == "Enabling:" ]]
[[ "${lines[1]}" == "127.0.0.2 example.com" ]]
}
# `hosts enable <hostname>` ###################################################
@test "\`enable <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
run "${_HOSTS}" add 0.0.0.0 example.net
run "${_HOSTS}" add 127.0.0.2 example.com
run "${_HOSTS}" disable 0.0.0.0
Add enable.bats.
2016-01-27 02:50:43 +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}" enable example.net
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
[[ ${status} -eq 0 ]]
Add enable.bats.
2016-01-27 02:50:43 +00:00
}
@test "\`enable <hostname>\` 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
run "${_HOSTS}" disable 0.0.0.0
Add enable.bats.
2016-01-27 02:50:43 +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}" enable example.net
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add enable.bats.
2016-01-27 02:50:43 +00:00
_compare "${_original}" "$(cat "${HOSTS_PATH}")"
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == "#disabled: 0.0.0.0 example.com" ]]
[[ "$(sed -n '12p' "${HOSTS_PATH}")" == "0.0.0.0 example.net" ]]
[[ "$(sed -n '13p' "${HOSTS_PATH}")" == "127.0.0.2 example.com" ]]
}
@test "\`enable <hostname>\` enables 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 127.0.0.2 example.com
run "${_HOSTS}" disable 0.0.0.0
run "${_HOSTS}" disable 127.0.0.2
Add enable.bats.
2016-01-27 02:50:43 +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}" enable example.com
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add enable.bats.
2016-01-27 02:50:43 +00:00
_compare \
"${_original}" \
"$(cat "${HOSTS_PATH}")"
_compare \
"'0.0.0.0 example.com'" \
"'$(sed -n '11p' "${HOSTS_PATH}")'"
_compare \
"'#disabled: 0.0.0.0 example.net'" \
"'$(sed -n '12p' "${HOSTS_PATH}")'"
_compare \
"'127.0.0.2 example.com'" \
"'$(sed -n '13p' "${HOSTS_PATH}")'"
[[ "$(sed -n '11p' "${HOSTS_PATH}")" == "0.0.0.0 example.com" ]]
[[ "$(sed -n '12p' "${HOSTS_PATH}")" == "#disabled: 0.0.0.0 example.net" ]]
[[ "$(sed -n '13p' "${HOSTS_PATH}")" == "127.0.0.2 example.com" ]]
}
@test "\`disable <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
run "${_HOSTS}" disable 0.0.0.0
Add enable.bats.
2016-01-27 02:50:43 +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}" enable example.net
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add enable.bats.
2016-01-27 02:50:43 +00:00
[[ "${lines[0]}" == "Enabling:" ]]
[[ "${lines[1]}" == "0.0.0.0 example.net" ]]
}
Add help tests to enable.bats.
2016-01-27 03:04:18 +00:00
# help ########################################################################
@test "\`help enable\` 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 enable
[[ ${status} -eq 0 ]]
Add help tests to enable.bats.
2016-01-27 03:04:18 +00:00
}
@test "\`help enable\` 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 enable
printf "\${status}: %s\n" "${status}"
printf "\${output}: '%s'\n" "${output}"
Add help tests to enable.bats.
2016-01-27 03:04:18 +00:00
[[ "${lines[0]}" == "Usage:" ]]
Update help/usage formatting.
2016-01-27 04:25:16 +00:00
[[ "${lines[1]}" == " hosts enable (<ip> | <hostname> | <search string>)" ]]
Add help tests to enable.bats.
2016-01-27 03:04:18 +00:00
}
Copy Permalink