This repository was archived by the owner on Sep 11, 2025. It is now read-only.
Repository navigation
Replies: 1 comment
|
After the discussion with @queria I found a more elegant way (using Antora) than pollute this repository with wild hacks. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I am working on a V1 to V2 migration guide (which will be the long run due to the size of the V1 API, but for now it is sufficient to document only known use cases) and I am playing with a little technical challenge: To not keeping the content of the migration guide with the V2 API in sync manually, I am planning to use Antora extensionability together with the content of this repository to generate the related part of the documentation from the prespecified set of API tests. The opposite way - to generate tests from a documentation (something what pytest's doctest extension is doing) - is also an option but I prefer to keep tests at a one place. Moreover, I failed to find Antora extension alternative to the pytest's doctest one.
The solution that comes up to my mind is to implement a wrapper (or monkey-patch) around
testandexpectfrom@playwrightto do the desired job.Another solution that I like much more than the previous one is to use
*.featureand*.step.tsapproach like in UI tests but I don't know if such a solution for the API tests is supported and/or desirable.All reactions