Functional tests for editor functionality
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Currently there aren't any tests for the editor mode of sops. A simple one would be setting sed with a simple replace as the editor, and checking that the values are actually replaced.
This would prevent issues like #215 from happening.
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
Start by locating the sops editor-mode entry point and existing functional test structure. Configure sed as the editor with a simple replacement, then verify through the test that the edited values are actually replaced and that the test catches the regression described in #215.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100