Details
- Reviewers
olasd - Group Reviewers
Reviewers - Commits
- rDICPff2b3e67853f: Add a check_vault command
The tests only check that the output conforms to Icinga's API to the best of my understanding of that API.
Diff Detail
- Repository
- rDICP Icinga plugins
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
I have the feeling that there's a way to factor out the state machine you're using for tests instead of duplicating it in all the tests.
I was about to point out that you should add a timeout, but you're adding that in a subsequent diff, so I guess that's fine.
swh/icinga_plugins/cli.py | ||
---|---|---|
28 | I think we've usually used dashes rather than underscores here. | |
swh/icinga_plugins/vault.py | ||
41 | Does anything actually raise that exception? |
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DICP/job/tox/1/
See console output for more information: https://jenkins.softwareheritage.org/job/DICP/job/tox/1/console
Build has FAILED
Link to build: https://jenkins.softwareheritage.org/job/DICP/job/tox/2/
See console output for more information: https://jenkins.softwareheritage.org/job/DICP/job/tox/2/console
Build is green
See https://jenkins.softwareheritage.org/job/DICP/job/tox/3/ for more details.