[design-proposal] Add support for testing
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 35
- Forks
- 35
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 8
Description
The effortless pattern should support testing of the components and be included as a best practice.
Describe the problem
Currently when building out an effortless project testing is an exercise left up to the user. There should be a best practice decided on and included in this repository to improve this experience because it's pretty important to end users.
Software Version
N/a
Possible Solution
Currently when testing effortless packages we do the following:
- Build the habitat package
- Use kitchen-vagrant to create a VM(s) with the results directory synced
- Install the package on the VMs
- Run the inspec tests
Open to other suggestions!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the existing effortless package-testing workflow described in the issue: build the Habitat package, sync the results directory with kitchen-vagrant, install it on VMs, and run InSpec tests. Compare possible testing approaches and define a best practice for component testing that is documented and included in the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100