Overview
Add ShellSpec unit test coverage for the shellFunctionSetup.sh file.
Details
Add ShellSpec unit tests for the shellFunctionSetup.sh file. Unit tests should be written for all supported shells.
All unit tests must be run by the pipeline.
Ensure that the result of these unit tests are reflected in the GitHub status badge(s) in the top level README.md of this repository.
The new unit tests should be documented to the same level as the existing ones.
Supported Shells
- bash
- zsh
- dash
- BusyBox ash
- FreeBSD sh
- NetBSD sh
- mksh
- OpenBSD ksh
- yash
- posh
- OSH
Artifact(s)
- PR that adds unit test coverage of
shellFunctionSetup.sh and ensures that the tests are run by the pipeline, if it exists.
Scope
At point of writing, I don't know how many of the supported shells are already supported by the unit test suit. If a shell is not already supported by the unit test suit, then break out the creation of unit tests of shellFunctionSetup.sh for that shell into a separate issue.
If issue #3 hasn't already been worked, then there will be no pipeline. In that case, there is no need to add these unit tests to the pipeline.
If issue #4 hasn't already been worked, the there is no need to do this. If issue #4 has been worked, but #5 hasn't, then this only needs to be done for the zsh status badge.
Blockers
Before this issue may be worked, ShellSpec unit tests must have already been added by issue #2.
Should be worked after issue #3 and #4.
Overview
Add ShellSpec unit test coverage for the
shellFunctionSetup.shfile.Details
Add ShellSpec unit tests for the
shellFunctionSetup.shfile. Unit tests should be written for all supported shells.All unit tests must be run by the pipeline.
Ensure that the result of these unit tests are reflected in the GitHub status badge(s) in the top level
README.mdof this repository.The new unit tests should be documented to the same level as the existing ones.
Supported Shells
Artifact(s)
shellFunctionSetup.shand ensures that the tests are run by the pipeline, if it exists.Scope
At point of writing, I don't know how many of the supported shells are already supported by the unit test suit. If a shell is not already supported by the unit test suit, then break out the creation of unit tests of
shellFunctionSetup.shfor that shell into a separate issue.If issue #3 hasn't already been worked, then there will be no pipeline. In that case, there is no need to add these unit tests to the pipeline.
If issue #4 hasn't already been worked, the there is no need to do this. If issue #4 has been worked, but #5 hasn't, then this only needs to be done for the zsh status badge.
Open a PR for This Issue
Blockers
Before this issue may be worked, ShellSpec unit tests must have already been added by issue #2.
Should be worked after issue #3 and #4.