Unit tests: SPDK
- Dominant language
- Python
- Stars
- 132
- Forks
- 69
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 47
Description
This issue is to keep track of unit tests related to startup and monitoring of SPDK.
- [ ] Test if GW reports error and exits on startup for invalid path for SPDK
- [ ] Test if GW exits after SPDK hangs
- [ ] Test if GW is able to successfully start and shut down SPDK
- [ ] Test if GW reports error and exits for invalid tgt_cmd_extra_args for SPDK
- [ ] Test if GW reports error and exits for invalid SPDK initialization
Contributor guide
Research direction
Start by locating the unit-test entry points for GW startup and monitoring of SPDK. Use the five checklist cases as the test plan: invalid paths and arguments, SPDK hangs or initialization failure, and successful startup and shutdown. Done means each case has a passing unit test covering the expected GW behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100