nspcc-dev / nspcc-dev/neofs-node
`neofs-lens storage inspect` unit test
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when a storage engine instance is up against some sensitive information that must not be changed, e.g. in the neofs-lens storage inspect command. Even if in RO mode.
Describe the solution you'd like
Add a unit test that ensures that an example storage has not changed after the command execution.
Describe alternatives you've considered
Have such a test in as an integrational one.
Additional context
https://github.com/nspcc-dev/neofs-node/pull/2543#discussion_r1315132559.
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 at the neofs-lens storage inspect command and its existing unit tests, then identify an example storage suitable for the check. Run the command in read-only mode and verify that the example storage remains unchanged afterward; the unit test should fail if execution modifies it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100