-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: clearly deprecate Harness in the testing how-tos #1508
Conversation
@tmihoc if you have time, feel free to review this, but no problem if not :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks. Approving with some suggested tweaks.
I also noticed that there's a broken link on this page: https://ops.readthedocs.io/en/latest/explanation/testing.html
ops.testing.Harness and/or {ref}``ops-scenario
Can we fix that while we're here?
Co-authored-by: Ben Hoyt <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks Tony! I've added a couple of comments about the framework name
Co-authored-by: Dave Wilding <[email protected]>
Small adjustments to the how-to guides on testing to make it clear that Harness is deprecated:
ops[testing]
should be installed to write unit tests.ops.testing
rather than fromscenario
.Note that this does not substantially change the testing documentation: there's a roadmap item to do that later in 25.04.
Live preview