All examples in documentation need to have e2e testing
This includes examples in the book and in the reference docs.
I believe this is already done. @etefera can you comment? This was supposed to be a part of the Q1 OKRs.
Yes, https://raw.githubusercontent.com/GoogleContainerTools/kpt/next/site/guides/consumer/get/README.md is an example of where we're validating the shell commands we're presenting. Is there something missing in that functionality?
This includes testing all packages in package-examples directory. Currently we have multiple methods for testing:
- Tests embedded in documentation.
- Hydration-only: test harness using
.expecteddirectory - Live e2e
- Packaging e2e?
We need to decide how to get coverage here. 2) is an easy low-hanging fruit.
@etefera second part in the above list is a good first issue to ramp up on the codebase, so assigning it you. Let's have a chat about how this needs to be done.