BitOps Integration Tests
- Dominant language
- Python
- Stars
- 37
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Outside of the Unit Tests https://github.com/bitovi/bitops/issues/286 where we test lower-level function details,
we'll need Integration Tests to verify different BitOps scenarios as a complete tool.
The main logic is in the 2 main files:
- [deploy_plugins.py](https://github.com/bitovi/bitops/blob/main/scripts/plugins/deploy_plugins.py)
- [install_plugins.py](https://github.com/bitovi/bitops/blob/main/scripts/plugins/install_plugins.py)
Test scenarios could be:
- BitOps finishes OK on some dummy opsrepo
- BitOps plugin installation is run OK on some dummy config
- Ensure the BitOps executes deployment per bitops config
- Verify if before/after hooks were really ran
- Verify the deployment order
- Exit with non-zero return code on different error(s)
Contributor guide
Research direction
Start by reading scripts/plugins/deploy_plugins.py and scripts/plugins/install_plugins.py, then review the unit-test scope in issue #286. Define integration cases around dummy opsrepos and configs, deployment order, before/after hooks, plugin installation, successful completion, and non-zero error exits; done means these BitOps scenarios are verified end to end.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100